ADITUS Developer Portal MCP
v1.0.0Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.
Endpoint health
online- Last checked
- 11/20/2026, 6:16:23 AM
- Latency
- 1214 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.aditus.developers%2Fdeveloper-portal
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.aditus.developers/developer-portal": {
"url": "https://developers.aditus.com/api/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
5 shown · authentication unknown
Get endpoint details
get_endpoint
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.
Schema valid · SHA-256 be818c2c7832…
View input schema
{ "type": "object", "properties": { "endpoint": { "type": "string", "minLength": 1, "maxLength": 300, "description": "Endpoint id (e.g. 'ticket-purchase-registration/cart/create-cart') or 'POST /api/shop/cart'" } }, "required": [ "endpoint" ], "$schema": "http://json-schema.org/draft-07/schema#" }Get an integration guide
get_guide
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.
Connections
streamable-http
https://developers.aditus.com/api/mcp