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.

7 días gratis · sin tarjeta · hosting UE

Pregunta cualquier cosa a Sage

Prueba un prompt real contra Sage 200 vía AnythingMCP — Claude llama a los tools y responde. Pulsa Enter en tu mensaje para instalar en Cloud.

Instalar Sage en Cloud
Sage 200 · live vía MCP
Compartir
Opus 4.7

Claude es IA y puede equivocarse. Verifica siempre las respuestas.

Setup en 2 minutos

  1. 1Inicia trial gratuita en cloud.anythingmcp.com.
  2. 2Click en Sage 200 en el connector store. Pega las credenciales.
  3. 3Genera MCP API key y apunta el cliente AI a la URL MCP.
Instalar Sage 200 ahora

Guías para Sage

Setup paso a paso para los principales clientes AI.

Configurar Sage 200

Directamente de la definición del conector: dónde encontrar las credenciales, qué permisos necesitan y con qué API habla este adaptador. Proporcionadas en inglés por el autor del conector.

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

  1. 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.
  2. In the Sage Developer Portal, get a developer subscription key (primary key) for the Sage 200 API.
  3. Set SAGE200_PRODUCT to sage200 for Sage 200 Standard or sage200extra for Sage 200 Professional, and fill in client ID, client secret and subscription key.
  4. 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.

Tu IA está a dos clicks de Sage 200.

Instala el conector, pega credenciales, pregunta a la IA. 7 días gratis, sin tarjeta.