ADITUS Developer Portal MCP

Read-only access to the official developer documentation of the ADITUS ticketing platform – the same content that powers developers.aditus.com.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Search Docs: Ranked full-text search across API modules, endpoints and integration guides.
  • List Modules: All API modules with direction, endpoint counts and documentation URLs, plus the guides.
  • List Endpoints: Every endpoint of one module.

What data it sees

Do you need an account

No: the server works without sign-in

Read-only access to the official developer documentation of the ADITUS ticketing platform – the same content that powers developers.aditus.com.

Tools

  • search_docs – full-text search across endpoints and integration guides
  • list_modules – all API modules (e.g. Ticket purchase & registration, Business Intelligence)
  • list_endpoints – endpoints of a module
  • get_endpoint – parameters plus request/response examples for one endpoint
  • get_guide – integration guides (authentication, scopes, webhook signatures, shop micro frontend)

Use it to design a shop or ticketing integration, find the right endpoint for a task, turn example payloads into code, or verify webhook signatures correctly.

No account, API key or configuration required. The server only reads documentation and never performs actions against ADITUS systems. No IP addresses or response content are logged; anonymised usage data is deleted after 90 days – see the privacy section.

Setup guide, example prompts and details: https://developers.aditus.com/mcp

Server tool list (5)

Raw names from tools/list. Only developers need these.

search_docsRanked full-text search across API modules, endpoints and integration guides.
list_modulesAll API modules with direction, endpoint counts and documentation URLs, plus the guides.
list_endpointsEvery endpoint of one module.
get_endpointFull contract of one endpoint (parameters, headers, body, example responses).
get_guideMarkdown of an integration guide (micro-frontend, guidelines, webhooks), whole or one section.