ADITUS Developer Portal MCP
com.aditus.developers/developer-portalVersion 1.0.0Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.
Status
Responds117 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:45 UTC
- Latency
- 117 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://developers.aditus.com/api/mcpResponds117 msNo sign-in
Claude Code
claude mcp add --transport http developer-portal https://developers.aditus.com/api/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: developer-portal
Remote MCP server URL: https://developers.aditus.com/api/mcpCursor
{
"mcpServers": {
"developer-portal": {
"url": "https://developers.aditus.com/api/mcp"
}
}
}VS Code
code --add-mcp '{"name":"developer-portal","type":"http","url":"https://developers.aditus.com/api/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
5 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
get_endpointFull contract of one endpoint: method, URL, auth, query and header parameters, request body example, example responses (large bodies truncated, full text on the docs page). Accepts the endpoint id from search/list, or 'METHOD /path'. Path parameters may use any name or spelling (':cart', '{cartId}', a concrete value); a leading '/api' or '/v1' is ignored. Some routes are recorded several times with different query parameters: a reference without query string resolves to the recording without query parameters, a reference with a query string (e.g. '?$expand=All') to the recording with exactly (or at least) those keys. If that still leaves several recordings, the result is { ambiguous: true, candidates: [{ id, name, method, path }] } instead of the contract — call again with one of the candidate ids. When nothing matches, the error lists the nearest endpoints of that method. | No | Yes | Yes | No |
get_guideMarkdown of an integration guide. 'micro-frontend' is the compact Shop Micro Frontend contract for coding agents (mounting, sessions, styling, Web Component, lifecycle, security); 'micro-frontend-docs' is the complete Micro Frontend documentation as on the website; 'micro-frontend-overview' is the non-technical overview (what it is, purchase flow, base setup, add-on levels); module guides such as 'guidelines' or 'webhooks' come from the API reference. Pass a section heading to fetch only that section. | No | Yes | Yes | No |
list_endpointsEvery endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules. | No | Yes | Yes | No |
list_modulesAll top-level ADITUS API modules with direction (inbound = your systems call ADITUS, outbound = ADITUS data into your systems), endpoint counts and documentation URLs. Also lists the integration guides. | No | Yes | Yes | No |
search_docsFull-text search across API modules, endpoints (name, path, description) and the guides (Shop Micro Frontend agent contract, full documentation and overview; Guidelines; Webhooks). The reference is English; German search terms are understood as well (a generated language layer maps them onto the English vocabulary, e.g. 'aussteller' → exhibitor, 'gutschein' → voucher). Returns ranked hits with ids usable in get_endpoint / get_guide. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Sep 12, 2026
- Updated
- Sep 12, 2026
- Repository
- Not given
- Categories (suggested)
- Developer toolsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared