ADITUS Developer Portal MCP
Server Details
Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- ADITUS Developer Portal MCP
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: list_modules browses modules, list_endpoints enumerates a module's endpoints, get_endpoint fetches one contract, get_guide fetches guide markdown, and search_docs performs full-text lookup. The only conceptual overlap is that search_docs can surface endpoints and guides, but the search-vs-browse-vs-fetch split is explicit and the descriptions make selection unambiguous.
All five tools follow a strict verb_noun snake_case pattern (get_endpoint, get_guide, list_endpoints, list_modules, search_docs). The verbs map consistently to intent: list for enumeration, get for single-resource retrieval, search for querying.
Five tools is a tight, well-scoped surface for a read-only developer portal: two listing tools, two getters, and one search. No tool feels redundant and none is obviously missing from the browse/search/retrieve triad.
The surface covers discovery (modules, endpoints, search) and retrieval (endpoint contracts, guides), which is the full lifecycle for a documentation server with no write operations needed. Minor gaps remain, such as no direct way to browse sub-groups independently or fetch non-guide documentation pages beyond what endpoint/guide tools expose.
Available Tools
5 toolsget_endpointGet endpoint detailsARead-onlyIdempotentInspect
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.
Inputs: endpoint (required).
get_guideGet an integration guideARead-onlyIdempotentInspect
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.
Inputs: guide (required), section.
list_endpointsList endpoints of a moduleARead-onlyIdempotentInspect
Every endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules.
Inputs: module (required).
list_modulesList API modulesARead-onlyIdempotentInspect
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.
Inputs: no named parameters.
search_docsSearch ADITUS documentationARead-onlyIdempotentInspect
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.
Inputs: query (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
List events, open dates, orders, payments, vouchers and coupons in bookingkit.
Read Ticketsauce events, orders and ticket check-in IDs (read-only).
Read pretix events, tickets and orders; check attendees in or out with your own account.
Event ticketing: create and publish events, read orders, attendees and sales analytics.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceReadonly MCP server for the Guedder API v3, enabling operational tasks like listing events, searching tickets, and managing purchases via Streamable HTTP or stdio.-
- AlicenseAqualityBmaintenanceEnables read-only access to B2match event and matchmaking data through tools for events, participants, organisations, opportunities, agenda, sessions, speakers, and authenticated meeting, schedule, conversation, and notification workflows. Supports anonymous public queries and secure local token-based access.22283 npmMIT
- AlicenseAqualityCmaintenanceEnables MCP clients to search and inspect Evand's public events, organizers, cities, and categories, including ticket prices, availability, descriptions, and recommendations. It is read-only, with purchases directed to evand.com.7250 npmMIT
- FlicenseNot gradedqualityDmaintenanceAI commerce platform — WooCommerce store products, flights, tours, activities and local transport via MCP. Search, availability and booking tools. No auth for public endpoint.-
Glama MCP Gateway
Add one secure layer between your agents and this server.