Sage 100 (DE)

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

1. 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.
2. 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.
3. Set SAGE100_URL to the Web API root (no trailing slash), SAGE100_COMPANY to the mandant/company identifier, and SAGE100_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 to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.