Sage 100 (DE)
Sage 100 German Mittelstand ERP over the Sage 100 Web API (OData): addresses, items, sales documents and stock on your own installation. Basic auth. Partner credentials and an activated Web API required.
7 天免费 · 无需信用卡 · EU 托管
问 Sage 任何事
通过 AnythingMCP 对 Sage 100 (DE) 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 SageClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Sage 100 (DE)。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 Sage 100 (DE)
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
Partner credentials required, and the Web API is a separate component. Sage 100 (the German product, not Sage 100cloud US) does not expose HTTP out of the box. The Sage 100 Web API / OData service has to be installed and licensed on your application server, and Sage distributes the developer documentation through its partner portal rather than publicly. Talk to your Sage partner before wiring this up.
Setup
- Have your partner install and start the Sage 100 Web API service and confirm which OData route it publishes — the path segment differs between Sage 100 versions and between the OData v3 and v4 services.
- Create a Sage 100 user for the integration with read rights on the areas you want. Sage enforces its own rights model on top of the API.
- Set
SAGE100_URLto the Web API root (no trailing slash),SAGE100_COMPANYto the mandant/company identifier, andSAGE100_USERNAME/SAGE100_PASSWORD.
OData vocabulary: $filter, $select, $top, $skip, $orderby, $expand. German entity names are used verbatim — Adressen, Artikel, Belege — which is why the tools below take the entity set name as a parameter rather than hard-coding a guess.
Start with sage_100_get_metadata. It returns the $metadata document with every entity set this particular installation publishes, which is the only reliable way to know what to ask for: a Sage 100 install is heavily customised and two customers rarely expose the same set.
Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.
Self-hosted, which is the thing to plan for.
- On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
- On an internal host (
sage.intern,10.0.0.x), self-host AnythingMCP on the same network and add that host toSSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.