MCP App Store
by KeenEthics
Commerce-Shopping
ADITUS Developer Portal MCP icon

ADITUS Developer Portal MCP

by ADITUS GmbH

Overview

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. The server is public, requires no account or API key, and never performs actions against ADITUS systems – it only reads documentation. No IP addresses and no response content are logged; anonymised usage data is deleted after 90 days (details at developers.aditus.com/mcp#privacy). ADITUS provides ticketing, registration and access-control solutions for trade fairs, events and leisure venues.

Tools

get_endpoint

Claude
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'.

get_guide

Claude
Markdown of an integration guide. 'micro-frontend' is the Shop Micro Frontend contract (mounting, sessions, styling, Web Component, lifecycle, security); module guides such as 'guidelines' or 'webhooks' come from the API reference. Pass a section heading to fetch only that section.

list_endpoints

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

list_modules

Claude
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.

search_docs

Claude
Full-text search across API modules, endpoints (name, path, description) and the integration guides (Shop Micro Frontend, Guidelines, Webhooks). Returns ranked hits with ids usable in get_endpoint / get_guide.

App Stats

5

Tools

Claude

Platforms

Works with

Claude

Data refreshed daily