For teams running Sage CRM next to Sage ERP
A Sage CRM MCP server reads opportunities, communications and quotes from the 2024 R2 REST API. Sage does not ship an MCP server as of 6 October 2026. Each call carries that user's credentials, and territory rights still apply. Pexon does not create a quote or an order from the agent.
What we build
Built on what Sage Group plc documents: Company, Person, Opportunity, Communication, Leads, Quotes, Orders. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# sage-crm-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
list_my_opportunities: # user -> opportunities that user's territory allows
backend: GET Opportunity, orderBy as documented in 2024 R2
mode: read
get_opportunity: # id -> status and linked company
backend: GET Opportunity('{id}')
mode: read
list_communications: # company -> communications
backend: GET Communication filtered to that company, confirmed in blueprint
mode: read
get_quote: # id -> quote status
backend: GET Quote, read
mode: read
draft_communication: # company, text -> a communication a person saves
backend: not posted by the agent
mode: propose
audit: every call logged with user, tool, arguments and the Sage CRM responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
Checked 6 October 2026
| What we found | |
|---|---|
| Interfaces | Sage CRM RESTful API (REST/JSON, docs public) |
| Authentication | The 2024 R2 SData page requires the user name and password on each request, Base64-encoded, in X-Sage-Authorization, over HTTPS. A release-note example uses the Authorization header instead. Territory, profile and field rights still apply. The blueprint records which header that server accepts. |
| Vendor MCP server | No vendor server. No Sage CRM MCP server is described on the 2024 R2 developer pages read on 6 October 2026. |
| Vendor AI assistant | None found. |
| Other connectors | None found. |
Sage Group plc (UK). DACH companies that already run a Sage ERP and add Sage CRM beside it. The DACH overview of 14 May 2026 lists Sage CRM that way and does not give a customer count.
Why Sage CRM is hard for agents
01 · Password
Sage documents the user name and password on the request, not a long-lived bearer token, on the page we read. The secret has to move with the call. It is still that user's secret, never a shared administrator password in the agent.
02 · Header
The authentication page says X-Sage-Authorization. A 2024 R2 release note sends Authorization. The first call in the blueprint finds which one this server enforces.
03 · Territory
A user who cannot see an opportunity in the client cannot see it on the API. An administrator token would erase that, so we do not use one.
04 · Quote
They are in the entity list. Reading a quote is a sales question. Creating an order is not.
Sage CRM holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
When this is the wrong page
If Sage CRM is only the address book beside Sage ERP, and the question is the invoice, this is the wrong page. The invoice is the ERP. This page is the opportunity and the quote.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Sage CRM owners and checks every backend against your release and licence. Week two tests whether a person's own Sage CRM permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named Sage CRM administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
No Sage CRM MCP server is described on the 2024 R2 developer pages read on 6 October 2026. This page describes what we add around that fact: a signed tool list and a test that the asking user only sees their own records.
Not on the list we sign. The blueprint starts read-only. A draft the person saves in the CRM is the only write, and only after that is agreed.
Only where the CRM would already show both of them the same records. Calls run as the person who asked. The blueprint tests that with two users before anything is called production.
The two-week Readiness Blueprint is fixed at €4,900: the tool list, a check against your tenant, and a test that permissions survive the round trip. A production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Thirty minutes with the engineer who would build the connector, with your Sage CRM administrator in the room if you like.