---
title: "Lessons learned: MCP integration of ERP, CRM, and email"
description: "What SIMO GmbH learned in the Lab about the Model Context Protocol: control before reach, permissions per tool, and data provenance."
canonical: "https://simosphereai.com/en/learnings/mcp-integration"
lang: en
---

# Lessons learned: MCP integration of ERP, CRM, and email

What SIMO GmbH learned in the Lab about the Model Context Protocol: control before reach, permissions per tool, and data provenance.

**MCP integration: control beats reach.**

The Model Context Protocol (MCP) connects language models to business systems. The technology is quick to build. Whether it holds up in a company depends on something else.

## What it is about

A language model knows nothing about your orders, customers, and contracts. Through MCP, it gets tools to look things up in ERP, CRM, email, or registers. That is the step from general world knowledge to answers from your own data.

In the Lab, we built several such integrations: for Microsoft 365, for public registers, and for annual accounts. The pattern repeated itself every time.

## What we learned

- **Control before reach**: What matters is not how many tools a server offers but how precisely it defines who may use which tool for which data.
- **Detect before the model reads**: Personal and sensitive content has to be detected before it reaches a model. Afterward, nothing can be taken back.
- **Deliver the provenance**: An answer from connected data must say where it comes from and which data is missing. Otherwise it cannot be checked.

## What it means for the architecture

MCP servers belong in the business architecture, not just in development. Every integration needs a business owner, a permission model, and a log.

Open protocols keep the choice of model open. Whoever integrates today should be able to switch models tomorrow without rebuilding the integration.

## Field reports and articles

- [Microsoft 365 and AI](https://simosphereai.com/en/field-reports/microsoft-365-and-ai-control): The value lies in control, not in access.
- [Trademarks in an agent workflow](https://simosphereai.com/en/field-reports/trademark-registers-in-agent-workflows): Anonymous and consented access, cleanly separated.
- [Building your own MCP server](https://simosphereai.com/en/blog/mcp-server-selbst-bauen): Blog: tailoring it so it holds up in operation.

## From the Lab to consulting.

SIMO does not judge options on vendor claims alone. Assumptions that can be tested technically are examined in the SIMOSphere AI Lab. SIMO GmbH works with your executive team to assess whether an approach that proves viable in the Lab makes sense for your company, and supports the implementation: independent of vendors, with a fixed scope and a decision after every phase.

- [Start the check](https://simo-online.com/en/self-check)
- [Book an initial call](https://request.simo-online.com/en?intent=erstgespraech)
- [All services on simo-online.com](https://simo-online.com/en/services)

Decision Readiness Check: 12 questions, about 3 minutes, instant result. Initial call: 45 minutes, free of charge, by video. Engagements begin with the BISA baseline assessment or the BEIA enterprise assessment. All on simo-online.com.

Rendered version: https://simosphereai.com/en/learnings/mcp-integration
