ADITUS Developer Portal MCP is an MCP server published by com.aditus.developers, hosted at developers.aditus.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 5 tools, including search_docs, list_modules, list_endpoints, get_endpoint, get_guide.
Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.
71 connections through 4 shared values. Tap any node.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | Maximum hits (default 10) |
| query * | string | Search terms in English or German, e.g. 'create cart', 'webhook signature', 'timeslot', 'session token', 'aussteller import' |
{
"name": "search_docs",
"title": "Search ADITUS documentation",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1,
"description": "Maximum hits (default 10)"
},
"query": {
"type": "string",
"maxLength": 200,
"minLength": 2,
"description": "Search terms in English or German, e.g. 'create cart', 'webhook signature', 'timeslot', 'session token', 'aussteller import'"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
No parameters.
{
"name": "list_modules",
"title": "List API modules",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Every endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules.
| Parameter | Type | Description |
|---|---|---|
| module * | string | Module id, e.g. 'ticket-purchase-registration' |
{
"name": "list_endpoints",
"title": "List endpoints of a module",
"description": "Every endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"module"
],
"properties": {
"module": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Module id, e.g. 'ticket-purchase-registration'"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| endpoint * | string | Endpoint id (e.g. 'ticket-purchase-registration/cart/create-cart') or 'POST /api/shop/cart' |
{
"name": "get_endpoint",
"title": "Get endpoint details",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"endpoint"
],
"properties": {
"endpoint": {
"type": "string",
"maxLength": 300,
"minLength": 1,
"description": "Endpoint id (e.g. 'ticket-purchase-registration/cart/create-cart') or 'POST /api/shop/cart'"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| guide * | 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 |
{
"name": "get_guide",
"title": "Get an integration guide",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"guide"
],
"properties": {
"guide": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Guide id, e.g. 'micro-frontend', 'micro-frontend-docs', 'micro-frontend-overview', 'guidelines', 'webhooks'"
},
"section": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "Optional section heading (or slug) to return only that part"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Read-only documentation for the ADITUS event-technology APIs (ticketing, registration, access, accreditation, Business Intelligence) and the Shop Micro Frontend. Start with search_docs for a topic, list_modules for orientation, then get_endpoint for the full contract (parameters, body, example responses) or get_guide 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.
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.