Read-only access to ADITUS event-technology API documentation, letting an assistant search modules, endpoints and integration guides.
What you can do
Search documentation by keyword across API modules, endpoints and guides, including German search terms mapped onto the English reference. List top-level API modules with direction, endpoint counts and documentation links, plus the integration guides. List every endpoint of a module with method, path, sub-group and summary. Fetch one endpoint's full contract: method, URL, auth, parameters, request body and example responses. Retrieve an integration guide as Markdown, including the Shop Micro Frontend contract for coding agents.
When to use it
Useful when integrating with ADITUS ticketing, access or BI APIs, or building against the Shop Micro Frontend, and you want the assistant to look up endpoint contracts and guides instead of guessing.
Requirements
A remote streamable HTTP endpoint at developers.aditus.com; no package, environment variables or headers are declared, and no authentication is declared.
Before you install
Documentation is read-only, but endpoint contracts include authentication details and example request bodies; treat anything retrieved as reference rather than verified production credentials. Large example bodies are truncated, so check the full docs page for complete payloads.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.aditus.developers%2Fdeveloper-portal/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Full-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.
Parameterslimitqueryrequired
list_modules
List API modules
All 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.
Takes no parameters.
list_endpoints
List endpoints of a module
Every endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules.
Parametersmodulerequired
get_endpoint
Get endpoint details
Full 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.
Parametersendpointrequired
get_guide
Get an integration guide
Markdown 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.
Parametersguiderequiredsection
Version history
1
v1.0.0LatestSep 16, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.