How to Connect Sage 200 to Gemini — via MCP

💡 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 + Gemini

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 Gemini

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.

Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:

{
  "mcpServers": {
    "anythingmcp": {
      "httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart gemini.
3. Run /mcp inside Gemini CLI (or gemini mcp list in your shell) — anythingmcp should show as connected.
4. Start prompting — Gemini CLI can now call the Sage 200 tools.

Available tools

FAQ

Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Meta Muse