Report · As of 2026-09-22

How agent-ready are 21 German B2B SaaS APIs?

AI agents (Claude, ChatGPT, Copilot & Co.) can only operate software on their own if the API is built for it: an MCP endpoint (Model Context Protocol), clean OAuth-standard authentication, machine-readable documentation. We put the APIs of 21 German B2B SaaS providers from the office and accounting software, ERP, HR, e-commerce, real estate, and communications sectors through a public surface assessment, using the same automated test our free MCP live test runs for every API.

Ranking

#CompanyScore
1awork53/100 (C)
2Clockodo37/100 (D)
3Personio33/100 (D)
4seven.io30/100 (D)
5JTL-Software18/100 (F)
6Xentral ERP18/100 (F)
7easybill15/100 (F)
8sevdesk12/100 (F)
9PlentyONE (plentymarkets)12/100 (F)
10propstack8/100 (F)
11Maileon8/100 (F)
12rexx systems8/100 (F)
13Zammad5/100 (F)
14Lexware Office5/100 (F)
15weclapp5/100 (F)
16softgarden5/100 (F)
17onOffice5/100 (F)
18Userlike (jetzt Lime Connect)5/100 (F)
19pretix2/100 (F)
20Collmex2/100 (F)
21d.vinci0/100 (F)

Key findings

4 of 21 companies offer an official MCP server: awork, seven.io, clockodo, and personio. All endpoints pass our live test with clean OAuth discovery (RFC 9728). The rest of the industry is absent from a technology the market already treats as a standard.
No company reaches half of the possible 100 points. Best in class: awork at 53/100, making it the German benchmark. The field's median sits at 8 of 100 points.
14 of 21 provide no machine-readable API description. Without an OpenAPI spec, every agent integration remains a hand-built GitHub repository, failure modes included. Exactly such unofficial wrappers already exist for at least 8 of the tested products.
The demand exists without the supply: Zammad customers ask for MCP in the official forum (561 views), the vendor's answer is “not really planned”, while a community server collects 41 stars. Propstack and Xentral now ship llms.txt for AI systems but offer no agent access to the product.
Authentication is the blind spot: 9 of the 21 APIs work with static keys and no OAuth flow. Delegated, restricted agent access (“this agent may only read invoices”) is technically impossible as a result.

Methodology

Tested per company: (1) MCP endpoint at the documented address; for vendors without a documented endpoint, derived hosts (mcp./api./docs./developers./developer. of the vendor domain) are additionally checked with a handshake scan: initialize/tools/list, Streamable HTTP, legacy SSE fallback, protocol version incl. server/discover per specification 2026-07-28; (2) authentication signals: 401/403 behavior, WWW-Authenticate with resource_metadata, OAuth Protected Resource Metadata (RFC 9728), Authorization Server Metadata (RFC 8414); (3) MCP Server Card (working group draft: /.well-known/mcp.json among others); (4) documentation surface: OpenAPI/Swagger at standard paths, at addresses verified during research and, if no spec is found there, on derived hosts (docs./api./developers./developer. of the vendor domain), robots.txt policies for 13 known AI crawlers (GPTBot, ClaudeBot, PerplexityBot among others), llms.txt (rated as cosmetic, since a Google study from 6/2026 found no effect), security.txt. Scoring: 40 points for a real MCP offering (handshake 15, listable tools 10, current specification level 5, server card 10), 25 points for authentication and safety signals, 20 points for machine-readable documentation, 15 points for tool description quality. The point distribution is deliberately designed so that a company without an MCP offering cannot mathematically reach the top grade. A dozen blog articles do not replace an endpoint. Limitations: The assessment is a snapshot of the public surface (September 19–20, 2026; corrected run on September 22, 2026, after the detection of specs at standard paths was repaired: sevdesk turns out to have a previously overlooked OpenAPI spec at api.sevdesk.de/openapi.yaml; a second full run with extended host detection confirmed all remaining values) and does not replace a security audit. What this test cannot see (live runs of real agents, tool permissions in detail, tenant separation, GDPR data flows) is the subject of our paid audit.

The full per-company breakdown

Every check result for all 21 companies — crawler policies, discovered specs, authentication signals — is published in the detailed German report.

Open the detailed report (German)
Your product is listed — or missing?

We test your API for free, or deliver the full diagnosis with live agent tests at a fixed price.

Start the free MCP live test