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.
7 天免费 · 无需信用卡 · EU 托管
问 Sage 任何事
通过 AnythingMCP 对 Sage 200 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 SageClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Sage 200。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 Sage 200
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
What this connects to: the Sage 200 API (Sage 200 Standard, and Sage 200 Professional connected to the API), https://api.columbus.sage.com/uk/<product>/accounts/v1. It reads customers, suppliers, sales and purchase orders, posted sales and purchase transactions (invoices, credit notes, receipts, payments), stock items and stock levels, and nominal codes. This first version only reads.
Start with sage_200_list_sites: it lists the sites and companies the signed-in user can reach. Every other tool takes site_id and company_id from it; they are sent as the X-Site and X-Company headers Sage 200 requires.
Setup
- Client credentials are issued by Sage, not created in Sage 200: request them from Sage Developer Services ([email protected], then Sage's application form). Choose a confidential (web server) client with the redirect URI
<your AnythingMCP URL>/api/mcp-oauth/callback(on AnythingMCP Cloud:https://cloud.anythingmcp.com/api/mcp-oauth/callback). Sage takes a few days. - In the Sage Developer Portal, get a developer subscription key (primary key) for the Sage 200 API.
- Set
SAGE200_PRODUCTtosage200for Sage 200 Standard orsage200extrafor Sage 200 Professional, and fill in client ID, client secret and subscription key. - On the connector page, click Authorize with Provider and sign in with the Sage ID that is an API user of your Sage 200 companies (for Sage 200 Professional, the company must be connected to the API in System Administration).
Querying: lists take OData options: filter (e.g. reference eq 'ABC001'), select, orderby, top, skip. Field names are snake_case, as in the answers. Ids are numbers and differ from references and codes.
Invoices: posted invoices and credit notes are ledger transactions; read them with sage_200_list_sales_transactions / sage_200_list_purchase_transactions and filter on the transaction type and outstanding value.
Pitfalls: 401 means the Sage ID token is not valid (authorize again) or the subscription key is wrong; 403 means the Sage ID is not an API user of that company. Amounts are in the account's currency; check currency_id.