Contact us
(Guide)

MCP integration:your ERP, store and CRM in ChatGPT and Claude

Updated · 6 min read

An MCP integration connects a business system to AI assistants so employees or customers can look up an order, a stock level or a CRM contact from ChatGPT or Claude. Some vendors already run their own MCP servers, others don't. Here's where things stand in November 2026 and how to pick the right approach for your company.

What an MCP integration is

MCP (Model Context Protocol) is an open standard that ChatGPT, Claude and other assistants use to reach external systems. An MCP server gives the assistant tools, such as "find order" or "check availability," and talks to your system's API itself. For the basics, see What is an MCP server?

The same server works in ChatGPT and in Claude. You don't build a separate integration for each assistant.

Three approaches

  • The vendor's official server: turn it on and connect it to ChatGPT or Claude. Fastest, but you get the tools and permissions the vendor designed.
  • Your own MCP server on the system's API: tools shaped around your processes, with your rules and permissions. Needed when the vendor has no server or theirs doesn't fit.
  • Your own server spanning several systems: one "order status" tool queries the store, the ERP and the carrier at once, so the assistant doesn't have to piece the answer together from three sources.

Who already has an official MCP server

As of early November 2026. The market changes every month, so check the vendor's docs before you decide.

  • Shopware 6: an MCP server in the platform core, with endpoints for the Admin API (/api/_mcp) and the Store API (/store-api/_mcp). Behind a feature flag since 6.7.11, on by default from 6.7.14, marked experimental until Shopware 6.8.
  • Microsoft Dynamics 365 Business Central: a hosted MCP server with Microsoft Entra ID sign-in. Microsoft lists Claude and ChatGPT as supported clients, but outside Microsoft's own tools you have to register your own app in Entra ID. The data query tools are in preview.
  • HubSpot: a remote server at mcp.hubspot.com with OAuth (PKCE) sign-in. In Claude it's also a Verified connector in the directory.
  • Salesforce: hosted MCP servers with OAuth sign-in.
  • Personio: an MCP server in beta, not yet available on every account.
  • SAP: the official MCP servers are mostly developer tools (Fiori, CAP, UI5, ABAP). Business data from S/4HANA goes through SAP's APIs.
  • JTL: has announced an MCP server with access to JTL-Wawi data as an open beta from November 2026, for ERP version 2.2 or later, with sign-in through a JTL account.
  • DATEV, lexware office, sevdesk, Xentral, weclapp: we found no official server, only community projects. Third parties offer MCP servers for some of these systems: before you connect one, check who processes your data.

When the vendor's server is enough

  • Your employees use it, not your customers.
  • You work with a single system, such as just the CRM.
  • The user's permissions in the system are a good enough limit on what the assistant can do.
  • The server supports the sign-in your assistant requires (see below).

When you need your own server

  • The system has no MCP server, or only an older API or a database on an on-premises server.
  • Customers will use the assistant, for example to check orders, stock and prices in your store. That calls for a separate public server with only safe tools. Example: Drukalo.
  • One answer needs data from several systems.
  • You want fewer, well-described tools instead of "the whole system over MCP." The assistant then picks the right tool more often. More in MCP server vs REST API.
  • You need your own rules: limits, approvals for changes, masking of personal data or an audit log.

Sign-in: what ChatGPT and Claude require

This is where integrations most often stall. ChatGPT accepts custom MCP servers only with OAuth 2.1 and PKCE, or with no sign-in at all. API keys, client credentials and service accounts aren't supported. Claude connectors also connect through OAuth or without sign-in.

  • Servers with OAuth (HubSpot, Salesforce, Business Central) connect directly, though Business Central needs an app registration in Entra ID first.
  • Shopware's Admin API server signs in with integration keys or a token from Shopware's own OAuth endpoint. For ChatGPT and Claude on the web, it needs an OAuth sign-in layer in front. Integration keys work in developer tools such as Claude Code, where you set the headers yourself.
  • Details and the differences between assistants are in OAuth for MCP servers.

Permissions and security

  • Start with read-only tools. Add tools that change things (orders, prices, invoices) after testing, with user confirmation.
  • Use a dedicated integration account with the least privileges needed, not an admin account.
  • The server checks permissions, not the assistant. The readOnlyHint and destructiveHint annotations help the assistant ask for confirmation, but they don't replace access control.
  • External content (emails, product descriptions, customer notes) can carry hidden instructions, known as prompt injection. The full list of risks is in MCP server security.
  • Log who changed what, when and with which tool.

Hosting and data

  • Your own MCP server can run in the EU, in the US or inside your network. For systems on your internal network, put a public HTTPS endpoint in front of the server or, in ChatGPT, use OpenAI's Secure MCP Tunnel.
  • Whatever a tool returns goes to OpenAI's or Anthropic's model under the terms of your plan. For company data, use business plans with a data processing agreement.
  • Return only the fields the answer needs. Instead of the full customer record, an order number and status are often enough.

How a project runs

  • Workshop: which questions and tasks employees or customers should handle in the assistant.
  • Tool list: a handful to a dozen or so tools, with descriptions, parameters and permissions.
  • A read-only prototype, tested in MCP Inspector, ChatGPT and Claude. How to test is covered in How to test an MCP server in ChatGPT and Claude.
  • OAuth sign-in, tools that change data, and an audit log.
  • Rollout in your company through the ChatGPT or Claude admin, and for customers a directory listing.
  • The amount of work depends mostly on the number of systems, the quality of their APIs, the sign-in method and whether the assistant only reads or also changes data.
FAQ
Do we need a new API for an MCP integration?
Usually not. The MCP server uses the API the system already has. If there's no API, as with an older on-premises ERP, the server can read data through an export, the database or a small adapter.
Will one integration work in both ChatGPT and Claude?
Yes. You add the same MCP server in ChatGPT as a plugin with a custom MCP server and in Claude as a connector. Sign-in and plan details differ.
Which ChatGPT and Claude plans do we need?
In ChatGPT, Business, Enterprise and Edu get full MCP, including tools that change data, while Pro is read-only. In Claude Team and Enterprise, the organization owner adds custom connectors. Details in [MCP servers in ChatGPT](/guides/chatgpt-mcp-server) and [Claude connectors](/guides/claude-connectors).
Our vendor has an MCP server. Why build our own?
Often you don't need to. Your own server makes sense when customers use the assistant, when one answer needs several systems, or when you need your own rules and narrower permissions than the vendor's server gives you.
Guides

Want to connect your system to ChatGPT and Claude?

MCP servers

LET'S MAKESOMETHINGPEOPLE→REMEMBER

Get in touch