ADITUS Developer Portal MCP

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "ADITUS Developer Portal MCP": {
      "url": "https://developers.aditus.com/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

• search_docs read-only

  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.

  Parameters:

  • query (required) — string — Search terms in English or German, e.g. 'create cart', 'webhook signature', 'timeslot', 'session token', 'aussteller import'
  • limit — integer — Maximum hits (default 10)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_modules read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_endpoints read-only

  Every endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules.

  Parameters:

  • module (required) — string — Module id, e.g. 'ticket-purchase-registration'

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_endpoint read-only

  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.

  Parameters:

  • endpoint (required) — string — Endpoint id (e.g. 'ticket-purchase-registration/cart/create-cart') or 'POST /api/shop/cart'

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_guide read-only

  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.

  Parameters:

  • guide (required) — string — Guide id, e.g. 'micro-frontend', 'micro-frontend-docs', 'micro-frontend-overview', 'guidelines', 'webhooks'
  • section — string — Optional section heading (or slug) to return only that part

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.