Connect MCP and the API
You will learn where to create personal API keys in Tixio and how they unlock MCP clients (Cursor, Claude Desktop) and REST calls.
This page is the integrations entry point. For full steps, scopes, rotation, service accounts, and client config snippets, use the guides linked below.
1. Open API keys
- Open your workspace.
- Choose Settings > API keys (under Tools & automation).
You can also jump here from the command palette or the g then s shortcut
labeled Go to API keys.
The page subtitle describes these tokens as personal tokens for MCP clients and external integrations.
2. Create a key
- Choose New key.
- Enter a Name (for example
CursororClaude Desktop). - Choose Create key.
- Copy the
tix_…token from Save this key now and store it safely. - Choose I have saved it.
Tixio shows the full token only once. Revoke and recreate (or rotate via REST) if you lose it.
3. Connect an agent or script
- MCP (Cursor, Claude Desktop) — put the key in your MCP server config and point at Tixio's MCP HTTP endpoint. Follow Manage API keys and service accounts.
- REST — send
X-API-Key: tix_…on API requests. Same workflow page covers examples and service accounts. - Scopes — the UI creates full-permission personal keys; use REST to create scoped keys. See API key scopes.
Concepts worth reading first
- API keys and programmatic access — personal keys vs service accounts, rotation grace, audit, and security practices.
- AI assistant capabilities — what the in-product assistant can do (separate from your own MCP client).
Related automation
If you need Tixio to push events outbound instead of polling with an API key, use Manage webhooks. For in-product reactions without a client, use Use automation rules.
Next
- Manage API keys and service accounts — Cursor, Claude Desktop, REST, rotation, and service accounts.
- API key scopes — scope names and common combinations.
- Connect Slack if teammates prefer Slack over a local MCP client for quick create/find.