MCP
Connect AI tools to Tillor via https://mcp.tillor.dev
Last updated on
With MCP (Model Context Protocol), tools such as Cursor, Claude, ChatGPT and Gemini can call the Tillor API for you. You log in once via OAuth; no API key needs to be in your config.
URL: https://mcp.tillor.dev
What you can do with it
Once connected, you can do the following in the AI tool:
- Browse API categories and endpoints (from the OpenAPI specification)
- Call endpoints with your own permissions in the chosen organisation
This runs over the same REST API as the HTTP API. What you are allowed to do depends on your Tillor account and your permissions in that organisation. Connecting via OAuth requires the permission Authorize OAuth apps (oauth:consent) in at least one organisation. Without that permission, consent fails and existing OAuth tokens stop working.
Authentication
- The tool connects to
https://mcp.tillor.devwithout a token - OAuth discovery and registration run on the MCP host; login and consent happen on Tillor
- You approve access in the browser
- The tool then sends a Bearer token with MCP calls
Send your organisation as a header when the tool supports it (Cursor, Gemini CLI):
X-Tillor-Org-Id: org_abc123Without that header (ChatGPT, Gemini app, Claude) you pass organizationId to call_api_endpoint. Organisation routes live under /orgs/{organizationId}; the API then fills in the header itself.
No API key needed
For the hosted MCP server you use OAuth (Connect / Authorize in the tool). For scripts and your own integrations you keep using API keys.
Connecting
Choose your tool:
Snelste weg: voeg Tillor toe in Cursor. Of zet dit in ~/.cursor/mcp.json (globaal) of .cursor/mcp.json (project):
{
"mcpServers": {
"Tillor": {
"url": "https://mcp.tillor.dev",
"headers": {
"X-Tillor-Org-Id": "org_abc123"
}
}
}
}Vervang org_abc123 door je organisatie-ID. Herlaad de MCP-servers en kies bij Tillor Connect of Authorize.
Or open the install picker for Cline, Zed, Warp, Codex and the rest.
Tools
| Tool | Purpose |
|---|---|
list_api_categories | Lists API categories |
list_api_endpoints | Endpoints in a category, with input schema |
get_api_endpoint_schema | Schema of a single endpoint by name |
call_api_endpoint | Calls an endpoint |
Endpoint names are not separate tools: use call_api_endpoint.
The full REST reference remains OpenAPI. MCP is a layer on top of it, not a separate product API.
Related
- HTTP API - API keys, headers and base URL
- OpenAPI - Full API specification
- API reference - Every endpoint, to try out in the browser