Request API access
MCP

The ADITUS documentation, inside your coding assistant.

A public, read-only MCP server over the API reference and the Shop Micro Frontend guide. No account, no key: enable it from a directory without any configuration, or add one URL, and Claude, Cursor, Copilot or ChatGPT look up the real contract instead of guessing.

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

Available in …

The server is published in these directories. Enable it there with a click; no configuration file needed.

  • Claude

    Enable it directly as a connector in Claude: one click, no snippet needed.

    Open in Claude

  • Official MCP Registry

    The official server entry (com.aditus.developers/developer-portal) that registry-aware clients import.

    Open listing

  • Glama

    Connector page with tool overview and an in-browser inspector.

    Open listing

  • Smithery

    Listing with install commands for many clients and a hosted playground.

    Open listing

Manual setup

Only needed if your client does not support a directory. Streamable HTTP, no authentication, no session state. Pick your client:

Claude Code: run this command once in your terminal; the server is then available in every session.

Claude Code
claude mcp add --transport http aditus-docs https://developers.aditus.com/api/mcp

Cursor: put this in .cursor/mcp.json in your project folder (or ~/.cursor/mcp.json for all projects).

Cursor · .cursor/mcp.json
{
  "mcpServers": {
    "aditus-docs": {
      "url": "https://developers.aditus.com/api/mcp"
    }
  }
}

VS Code with Copilot: put this in .vscode/mcp.json in your project folder, or add it to your user settings via “MCP: Add Server”.

VS Code / Copilot · .vscode/mcp.json
{
  "servers": {
    "aditus-docs": {
      "type": "http",
      "url": "https://developers.aditus.com/api/mcp"
    }
  }
}

Claude Desktop: open Settings → Developer → Edit Config, paste this into claude_desktop_config.json and restart the app.

Claude Desktop · claude_desktop_config.json
{
  "mcpServers": {
    "aditus-docs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://developers.aditus.com/api/mcp"]
    }
  }
}

ChatGPT: in Settings → Connectors, add a custom connector with the endpoint URL above; no snippet needed. To try the server without any client, run this in a terminal:

curl
curl -s https://developers.aditus.com/api/mcp \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"search_docs","arguments":{"query":"create cart"}}}'

Clients that read server cards discover the same server at /.well-known/mcp/server-card.json.

Tools

Five read-only tools. Content comes from the same redacted collection snapshot as the API reference and the Markdown mirrors under /ai, so all three always agree.

ToolArgumentsReturns
search_docsquery, limit?Ranked full-text search across modules, endpoints and guides.
list_modules–All API modules with direction, endpoint counts and links, plus the guides.
list_endpointsmoduleEvery endpoint of one module with method, path and a one-line summary.
get_endpointendpointFull contract: parameters, headers, request body and example responses.
get_guideguide, section?Markdown of the Shop Micro Frontend guides (agent guide, full documentation, overview), Guidelines or Webhooks, whole or one section.

Example prompts

Three typical questions and what happens after you ask them.

  1. “How do I create a cart and add a ticket via the ADITUS Shop API?”

    The assistant calls search_docs("create cart add item"), then get_endpoint for the two matching endpoints, and answers with the request order, required headers and body fields plus an example response.

  2. “How do I verify the signature of an ADITUS webhook?”

    The assistant calls get_guide("webhooks", "signature") and returns the exact header name, the signing algorithm and a verification snippet in your language, citing the guide section.

  3. “Which ADITUS APIs exist for access control, and which endpoint reads a ticket's scan history?”

    The assistant calls list_modules, picks the access module, calls list_endpoints for it and then get_endpoint for the scan-history endpoint, and answers with the module overview and the endpoint's parameters and response fields.

Data and privacy

No account, no key, and your conversation never reaches the server: your assistant sends only the tool name and its arguments (search term, module, endpoint or guide id). For operations, each request is logged with the JSON-RPC method, tool name, those arguments (each cut to 200 characters), the HTTP status, error or rejection reason, result count, duration, the client name, version and protocol version from initialize, the client's user-agent and a short keyed hash (HMAC) of the IP address; the address itself is never stored. Log rows are deleted after 90 days (pruned at startup and every six hours), stay within ADITUS and are not shared with third parties. Responses come exclusively from the public documentation. Questions: Contact · Privacy policy