API Tools

aditus.com

An MCP server that searches ADITUS API documentation, listing modules and endpoints and retrieving full endpoint contracts and integration guides.

1 endpoint5 known toolsFirst detected September 13, 2026Last detected September 13, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: aditus-developer-docs
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

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. API hosts are per customer: request examples use the {{API_BASE_URL}} placeholder; never invent a hostname. The Business Intelligence module additionally offers an assistant MCP server that answers data questions directly (aggregates, KPIs) over a customer's own event data. That server is NOT this one: it runs per customer, requires the customer's Business Intelligence credentials and applies the same data scoping as the BI API. Access is arranged with ADITUS; see https://developers.aditus.com/business-intelligence (section "Assistant access (MCP)"). This documentation server is public, read-only and needs no credentials.

Known tools 5

search_docs

Full-text search across API modules, endpoints (name, path, description) and the integration guides (Shop Micro Frontend, Guidelines, Webhooks).

Inferred read-only

list_modules

All top-level ADITUS API modules with direction (inbound = your systems call ADITUS, outbound = ADITUS data into your systems), endpoint counts and documentation URLs.

Inferred read-only

list_endpoints

Every endpoint of one module (id, method, path, sub-group, one-line summary).

Inferred read-only

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

Inferred read-only

get_guide

Markdown of an integration guide.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.aditus-developer-docs]
url = "https://developers.aditus.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "aditus-developer-docs": {
      "type": "http",
      "url": "https://developers.aditus.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: aditus-developer-docs
Remote MCP URL: https://developers.aditus.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "aditus-developer-docs": {
      "url": "https://developers.aditus.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "aditus-developer-docs": {
      "type": "http",
      "url": "https://developers.aditus.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "aditus-developer-docs",
  "transport": "streamable-http",
  "url": "https://developers.aditus.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.