Business Central MCP Setup for Claude or ChatGPT

You can connect Claude or ChatGPT to Microsoft Dynamics 365 Business Central through an MCP server, provided you use a server compatible with the client and configure authentication and permissions. The practical setup is to run or access the MCP server, register it as a tool in the AI client, sign in to Business Central, and test a read-only request before allowing any changes.

What Business Central MCP Does

Model Context Protocol (MCP) is a way for an AI application to discover and call tools exposed by another service. A Business Central MCP server acts as the bridge: it receives a tool request from Claude or ChatGPT, accesses Business Central through an approved connection, and returns data or performs an available action.

MCP is a protocol, not a Microsoft Business Central feature that automatically enables every AI client. The available tools and setup depend on the specific server implementation. One server might expose customers, items, and sales orders; another may support only a subset, or may be intended for demonstrations rather than production. Confirm the server’s documentation, maintenance status, supported Business Central environment, and permissions before connecting company data.

For example, an enabled read tool might let you ask for the status of a sales order or retrieve information about an item. A write-enabled tool could potentially create or update records. The AI’s response is only as reliable as the tools and data it can access, so treat its suggestions as a user interface—not as a substitute for checking important transactions.

Choose a Server and Confirm Compatibility

Start with the MCP server, not the chat prompt. Locate a server whose documentation specifically describes Business Central support and explains how it connects, what tools it exposes, and whether it runs locally or as a hosted service. Do not assume that a project with “Business Central” in its name is maintained by Microsoft or suitable for production.

• Check the supported Business Central deployment and authentication method. Business Central online and on-premises environments can have different connection requirements.
• Review the tool list and distinguish read operations from create, update, post, or delete operations.
• Identify where the server runs and what network access it needs. A local process, container, and hosted endpoint have different operational and security implications.
• Check whether the server uses Microsoft’s supported APIs or another integration route, and whether its documentation explains required permissions and configuration.
• Verify client compatibility. Claude and ChatGPT have different interfaces and availability for connecting external tools; the client must support the server’s transport and connection method.

Use a test environment when available. If you cannot verify the server’s source, maintenance, or handling of credentials, do not connect it to a live company tenant.

Prepare Business Central Access

Before configuring the AI client, arrange the Business Central identity and permissions required by the chosen server. Follow that server’s current documentation: some integrations use Microsoft Entra ID app registration and OAuth, while others may have different supported authentication arrangements. Do not copy credentials, tenant identifiers, callback URLs, or permission names from an unrelated MCP guide; they are specific to the implementation and deployment.

1. Identify the Business Central environment and company the integration should access.
2. Have an administrator configure the documented application or sign-in flow, including any redirect or callback settings the server requires.
3. Grant only the permissions needed for the intended tools. Begin with read access if the goal is to look up records.
4. Store secrets using the server’s documented secret-management method. Do not put client secrets, access tokens, or passwords in prompts, source control, or shared configuration files.
5. Record who owns the integration and how access will be reviewed and revoked.

Permission design matters because MCP tools may act with the authority of the identity used to connect. A natural-language request such as “update this order” does not itself provide a safety boundary. The underlying account and server determine what can actually happen.

Connect Claude or ChatGPT

The exact screens change, and the two clients do not necessarily offer identical MCP connection options. Use the current instructions for the client account and server you have. In general, you need to start or make the MCP server reachable, then add its connection details in the client’s supported connector or developer configuration. A local server may require a command or configuration entry; a hosted server may require an endpoint and an authorization flow.

1. Install or launch the MCP server according to its documentation. Confirm that it starts successfully and can reach the intended Business Central environment.
2. In the AI client, open the area for connecting tools, connectors, or MCP servers. If the feature is unavailable on your account or client, do not try to work around that limitation; use a supported client configuration or another integration approach.
3. Enter the server details exactly as documented, including its transport, command or endpoint, and authentication settings. Avoid substituting guessed values.
4. Complete the sign-in or authorization flow, if required, and review the tools the client reports as available.
5. Ask a narrowly scoped, read-only question, such as “List the fields available for a sales order” or “Look up item [known item number].” Check the result against Business Central.

ChatGPT and Claude may expose MCP connections through different product features, account plans, or workspace controls. Availability can change; consult the current product documentation rather than relying on instructions written for an older interface. If a client supports only a hosted connection while your server is local, or vice versa, you will need a compatible deployment or a different connector.

Test Safely Before Using It for Work

Begin with a small test plan. Verify both that the AI can find the expected record and that it cannot access unrelated companies or perform actions outside its role. Test with non-sensitive records in a sandbox wherever possible.

• Check a known record by a unique identifier, such as an item number, rather than a vague description.
• Ask for the source fields used in the answer. Confirm dates, currencies, quantities, and company context directly in Business Central.
• For write tools, inspect the exact operation and approval process before enabling them. Test only in a sandbox and require a human to verify consequential changes.
• Review logs and audit information available from the server and Business Central. Know how to disable the connection and revoke its authorization.

Do not paste confidential business data into a chat unless the organization’s policies and the relevant service settings allow it. Consider data retention, access controls, and where prompts and tool results may be processed. A server’s ability to fetch a record does not mean every user is authorized to see it.

Common Setup Problems

If the server does not appear in the client, first check whether the client supports that connection type and whether the server process or endpoint is reachable. For a local process, confirm the command, runtime, and configuration path from the server’s documentation; for a hosted endpoint, check network access and the documented authentication flow.

An authorization error commonly points to a missing or incorrect sign-in configuration, insufficient permissions, or a mismatch between the selected environment and the identity. A successful connection that returns no records may instead reflect the wrong company, filters, or a tool that does not expose the requested data. Ask the server administrator to inspect its logs, but never share secret values in a troubleshooting message.

If results are incomplete or the AI misreads them, check what fields the tool actually returns. MCP does not make a server’s data model more complete, nor does it guarantee that the model will interpret every result correctly. Use specific identifiers and verify important figures in the source application.

Frequently Asked Questions

Can I connect Business Central to both Claude and ChatGPT?
Yes, if each client supports a connection method compatible with the MCP server and your organization permits both. Configure and authorize each client separately; do not assume one client’s settings or credentials can simply be copied to the other.

Is Business Central MCP an official Microsoft connector?
MCP is a protocol, and the existence of a Business Central MCP server does not establish that Microsoft publishes or endorses it. Check the specific server’s publisher, documentation, and support status.

Do I need an administrator?
Often, yes. Business Central access, application registration, consent, and permission assignment may require an administrator. The exact requirements depend on the server and your organization’s configuration.

Can the AI create or post sales orders?
Only if the server exposes the relevant write tools and the connected identity has sufficient permissions. Start with read-only access; test any write capability in a sandbox and keep human review for consequential transactions.

Why does the setup guide for Claude not match ChatGPT?
The clients can differ in MCP support, account availability, connection screens, and supported transports. Follow the current instructions for the particular client and server rather than treating their setup steps as interchangeable.

What is the safest first test?
Use a sandbox and a read-only tool to retrieve a known record by its unique identifier. Verify the returned company and fields in Business Central before expanding access.

Related

• View Saved Passwords in Safari on a Mac
• Facebook Group Post vs Page Post: Key Differences
• DayZ Types.xml: How to Change Loot Quantity