ADITUS Developer Portal MCP

Read-only access to the official developer documentation of the ADITUS ticketing platform – the same content that powers developers.aditus.com.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Search Docs: Ranked full-text search across API modules, endpoints and integration guides.
  • List Modules: All API modules with direction, endpoint counts and documentation URLs, plus the guides.
  • List Endpoints: Every endpoint of one module.

What data it sees

Do you need an account

No: the server works without sign-in

Read-only access to the official developer documentation of the ADITUS ticketing platform – the same content that powers developers.aditus.com.

Tools

  • search_docs – full-text search across endpoints and integration guides
  • list_modules – all API modules (e.g. Ticket purchase & registration, Business Intelligence)
  • list_endpoints – endpoints of a module
  • get_endpoint – parameters plus request/response examples for one endpoint
  • get_guide – integration guides (authentication, scopes, webhook signatures, shop micro frontend)

Use it to design a shop or ticketing integration, find the right endpoint for a task, turn example payloads into code, or verify webhook signatures correctly.

No account, API key or configuration required. The server only reads documentation and never performs actions against ADITUS systems. No IP addresses or response content are logged; anonymised usage data is deleted after 90 days – see the privacy section.

Setup guide, example prompts and details: https://developers.aditus.com/mcp

How to connect

How to connect ADITUS Developer Portal MCP to Claude

The server address to paste into Claude settings:

https://aditus-developer-portal--m-ehbrecht.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect ADITUS Developer Portal MCP to ChatGPT

The server address to paste into ChatGPT settings:

https://aditus-developer-portal--m-ehbrecht.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect ADITUS Developer Portal MCP to Cursor

The server address to paste into Cursor settings:

https://aditus-developer-portal--m-ehbrecht.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (5)

Raw names from tools/list. Only developers need these.

search_docsRanked full-text search across API modules, endpoints and integration guides.
list_modulesAll API modules with direction, endpoint counts and documentation URLs, plus the guides.
list_endpointsEvery endpoint of one module.
get_endpointFull contract of one endpoint (parameters, headers, body, example responses).
get_guideMarkdown of an integration guide (micro-frontend, guidelines, webhooks), whole or one section.