AnythingMCP Cloud is live — 7-day free trial−30% for 3 months with START30
AnythingMCP
Connector guide6-minute read15 MCP tools7 languages

Connect Sage 200 to Microsoft Copilot via MCP

Read Sage 200 Standard and Professional through the Sage 200 API: customers, suppliers, sales and purchase orders, posted invoices, credit notes and payments, stock items and stock levels, nominal codes. Sage ID OAuth 2.0, read-only.

HCBy HelpCode teamUpdated 6 min read Open-source on GitHub
Install Sage 200 on Cloud — free trialRead the step-by-step guide

No credit card · 7-day trial · Self-host alternative available

Sage 200

Sage 200

Read Sage 200 Standard and Professional through the Sage 200 API: customers, suppliers, sales and purchase orders, posted invoices, credit notes and payments, stock items and stock levels, nominal codes. Sage ID OAuth 2.0, read-only.

tools

15

Region

GB

Category

Accounting

Authentication

OAuth 2.0

Required env vars

SAGE200_PRODUCTSAGE200_CLIENT_IDSAGE200_CLIENT_SECRETSAGE200_SUBSCRIPTION_KEY
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Summary

Read Sage 200 Standard and Professional through the Sage 200 API: customers, suppliers, sales and purchase orders, posted invoices, credit notes and payments, stock items and stock levels, nominal codes. Sage ID OAuth 2.0, read-only.

Guided setup

Connect Sage 200 to Microsoft Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Sage 200 in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.

Set up Sage 200 freeI already have an account

No credit card · 7-day trial · Self-host alternative available

Try asking

Example prompts for Sage 200

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

Sage 200 · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Sage 200, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Sage 200 + Microsoft Copilot

Read Sage 200 Standard and Professional through the Sage 200 API: customers, suppliers, sales and purchase orders, posted invoices, credit notes and payments, stock items and stock levels, nominal codes. Sage ID OAuth 2.0, read-only.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

SAGE200_PRODUCT, SAGE200_CLIENT_ID, SAGE200_CLIENT_SECRET, SAGE200_SUBSCRIPTION_KEY

Step 1 — Get credentials

Sage issues the OAuth credentials; they cannot be created inside Sage 200, so allow a few days.

  1. Request a client ID and secret from Sage Developer Services ([email protected], then Sage's application form). Ask for a confidential (web server) client with the redirect URI https://cloud.anythingmcp.com/api/mcp-oauth/callback, or <your AnythingMCP URL>/api/mcp-oauth/callback when self-hosted.
  2. In the Sage Developer Portal, copy the primary key of your Sage 200 API subscription into SAGE200_SUBSCRIPTION_KEY (sent as Ocp-Apim-Subscription-Key).
  3. Set SAGE200_PRODUCT to sage200 for Sage 200 Standard or sage200extra for Sage 200 Professional, and fill in SAGE200_CLIENT_ID and SAGE200_CLIENT_SECRET.
  4. On the connector page, click Authorize with Provider and sign in with a Sage ID that is an API user of your companies. For Sage 200 Professional, the company must be connected to the API in System Administration.
  5. Call sage_200_list_sites first: every other tool needs the site_id and company_id it returns.

The connector only reads. Lists take OData options (filter, select, orderby, top, skip) with snake_case field names. Posted invoices and credit notes are ledger transactions: read them with sage_200_list_sales_transactions and sage_200_list_purchase_transactions. A 401 means authorize again or check the subscription key and edition; a 403 means the Sage ID is not an API user of that company.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

  1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
  2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
  3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
  4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
  5. Try it in the agent's Test pane: ask for something that needs the Sage 200 tools.
  6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

ToolWhat it does
sage_200_list_sitesThe Sage 200 sites and companies the signed-in Sage ID user can reach through the API, with site_id, site name, company_id and company name
sage_200_list_customersCustomer accounts with id, reference, name, balance, credit limit, on-hold flag, account status, currency and contact details
sage_200_get_customerOne customer account by id with addresses, contacts, credit terms, balance, analysis codes and default tax code
sage_200_list_suppliersSupplier accounts with id, reference, name, balance, credit limit, on-hold flag, currency and contact details
sage_200_get_supplierOne supplier account by id with addresses, contacts, payment terms, balance, bank details and default tax code
sage_200_list_sales_ordersSales orders (SOP) with id, document number, customer, document date, requested delivery date, status, totals and currency
sage_200_get_sales_orderOne sales order by id with header, delivery address and, with expand lines, every order line (product, quantity, price, discount…
sage_200_list_purchase_ordersPurchase orders (POP) with id, document number, supplier, document date, status, totals and currency
sage_200_get_purchase_orderOne purchase order by id with header and, with expand lines, every line (product, quantity, cost, received and invoiced quantities)
sage_200_list_sales_transactionsPosted sales ledger transactions: invoices, credit notes, receipts and adjustments with customer, reference, date, due date, goods, tax and…
sage_200_list_purchase_transactionsPosted purchase ledger transactions: supplier invoices, credit notes, payments and adjustments with supplier, reference, date, due date…
sage_200_list_productsStock items (products) with id, code, name, product group, unit of sale, prices, cost and stock settings
sage_200_get_productOne stock item by id with descriptions, units, prices, cost, analysis codes, suppliers and warehouses
sage_200_list_stock_levelsStock holdings per product and warehouse: quantity in stock, allocated, free, on order and reorder levels
sage_200_list_nominal_codesNominal (general ledger) accounts with id, reference, cost centre, department, name, account type and balances

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

Was this guide helpful?

Connect Sage 200 to Microsoft Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Sage 200 in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.

Set up Sage 200 freeSelf-host with DockerContact Sales

Related guides

Connectors

Connect Sage 200 to ChatGPT via MCP

Read Sage 200 Standard and Professional through the Sage 200 API: customers, suppliers, sales and purchase orders, posted invoices, credit notes and payments, stock items and stock levels, nominal codes. Sage ID OAuth 2.0, read-only.

Connectors

Connect Sage 200 to Claude via MCP

Read Sage 200 Standard and Professional through the Sage 200 API: customers, suppliers, sales and purchase orders, posted invoices, credit notes and payments, stock items and stock levels, nominal codes. Sage ID OAuth 2.0, read-only.

Connectors

Connect Sage 200 to Cursor via MCP

Read Sage 200 Standard and Professional through the Sage 200 API: customers, suppliers, sales and purchase orders, posted invoices, credit notes and payments, stock items and stock levels, nominal codes. Sage ID OAuth 2.0, read-only.

Connectors

Connect Sage 200 to Gemini CLI via MCP

Read Sage 200 Standard and Professional through the Sage 200 API: customers, suppliers, sales and purchase orders, posted invoices, credit notes and payments, stock items and stock levels, nominal codes. Sage ID OAuth 2.0, read-only.

Connectors

Connect Sage 200 to Meta Muse via MCP

Read Sage 200 Standard and Professional through the Sage 200 API: customers, suppliers, sales and purchase orders, posted invoices, credit notes and payments, stock items and stock levels, nominal codes. Sage ID OAuth 2.0, read-only.

Connectors

Sage 200 MCP Server: Invoices, Orders and Stock

Read Sage 200 Standard and Professional through the Sage 200 API: customers, suppliers, sales and purchase orders, posted invoices, credit notes and payments, stock items and stock levels, nominal codes. Sage ID OAuth 2.0, read-only.