ADITUS Developer Portal MCP

The ADITUS Developer Portal MCP gives AI assistants direct, read-only access to the official developer documentation of the ADITUS ticketing platform (developers.aditus.com) – the same source that powers the portal's API reference.

Five tools: • search_docs – full-text search across endpoints and guides • list_modules – overview of all API modules (e.g. Ticket purchase & registration, Business Intelligence) • list_endpoints – all endpoints of a module • get_endpoint – details of a single endpoint including parameters and request/response examples • get_guide – integration guides such as authentication, scopes, webhook signatures or the shop micro frontend Typical use cases: designing a shop or ticketing integration, finding the right endpoint for a given task, turning example payloads into code, verifying webhook signatures correctly, or answering questions about authentication and scopes.

MCP connector

Server URL: https://developers.aditus.com/api/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: Read-only documentation for the ADITUS event-technology APIs (ticketing, registration, access, accreditation, Business Intelligence) and the Shop Micro Frontend. Start with for a topic, for orientation, then for the full contract (parameters, body, example responses) or for integration guides. Shop Micro Frontend: 'micro-frontend' is the compact contract for coding agents, 'micro-frontend-docs' the complete human documentation, 'micro-frontend-overview' the non-technical overview (what it is, purchase flow, base setup, add-on levels) for questions from non-developers. API hosts are per customer: request examples use the {{API_BASE_URL}} placeholder; never invent a hostname. ADITUS also offers an MCP server over the ADITUS API itself (a customer's own event data). That server is NOT this one: it requires an API client for the customer system; customers arrange it with their ADITUS Customer Success Manager. This documentation server is public, read-only and needs no credentials.

Tools

Reads data5

Skills

None in the store listings or on the server

MCP connector

Server URL

https://developers.aditus.com/api/mcp

None

Protocol

MCP 2025-11-25

Instructions

Read-only documentation for the ADITUS event-technology APIs (ticketing, registration, access, accreditation, Business Intelligence) and the Shop Micro Frontend. Start with for a topic, for orientation, then for the full contract (parameters, body, example responses) or for integration guides. Shop Micro Frontend: 'micro-frontend' is the compact contract for coding agents, 'micro-frontend-docs' the complete human documentation, 'micro-frontend-overview' the non-technical overview (what it is, purchase flow, base setup, add-on levels) for questions from non-developers. API hosts are per customer: request examples use the {{API_BASE_URL}} placeholder; never invent a hostname. ADITUS also offers an MCP server over the ADITUS API itself (a customer's own event data). That server is NOT this one: it requires an API client for the customer system; customers arrange it with their ADITUS Customer Success Manager. This documentation server is public, read-only and needs no credentials.