Remote MCP Connector – Add TokPortal to claude.ai
Add TokPortal to claude.ai (web & mobile) or Claude Desktop as a custom connector with one-click OAuth login — no API key to paste.
Remote MCP Connector (claude.ai)
The remote connector lets you add TokPortal directly inside claude.ai (web & mobile) or Claude Desktop as a "custom connector" — with a single URL and a one-click login. There is no JSON config file and no API key to copy: Claude sends you through a TokPortal sign-in and you approve access.
Prefer a local setup for Cursor, Claude Code, or your own agents? Use the npm package (
tokportal-mcp) instead — it stays the right choice for stdio clients.
Connector URL
https://app.tokportal.com/api/ext/mcp
Add it in claude.ai
- Open claude.ai → Settings → Connectors → Add custom connector.
- Paste the connector URL above and confirm.
- Claude redirects you to TokPortal. Sign in (or you're already logged in).
- On the consent screen, choose Full access or Read-only, then click Authorize.
- Done — TokPortal tools now appear in Claude. Try: "What's my TokPortal credit balance?"
The same steps work in the Claude mobile app and in Claude Desktop (Settings → Connectors → Add custom connector).
How authentication works
The remote connector uses standard OAuth 2.1 with PKCE — the same mechanism Claude uses for any remote MCP server:
- Claude discovers the authorization server from the connector URL automatically.
- You log in to TokPortal and approve in your browser. Your password and API keys are never entered into Claude.
- On approval, TokPortal mints a dedicated API key named
Claude (MCP connector)and hands it to Claude as the access token. - Every tool call Claude makes runs under your TokPortal account, through the same public API and the same rate limits as a normal API key.
Access levels
At sign-in you choose how much the connector can do:
| Level | What Claude can do |
|---|---|
| Full | Read and write — create/configure/publish bundles, upload media, manage webhooks. Actions consume your credits. |
| Read-only | Read analytics, bundles, accounts and balances. No changes, no credit spend. |
You can authorize twice (once Full, once Read-only) if you want both, and pick the connector per conversation.
Managing & revoking access
The connector is just a named API key. To see or revoke it:
- Go to the Developer Portal → API Keys.
- Find the key named
Claude (MCP connector). - Revoke it — Claude immediately loses access and will prompt you to re-authorize next time.
Security notes
- Authorization codes are single-use, short-lived (10 minutes) and PKCE-bound (S256 only).
- The consent screen shows you exactly which destination the authorization is sent to (e.g.
claude.ai). Only approve destinations you recognize. - All traffic is HTTPS. The connector reuses the public API's authentication, rate-limiting and audit logging.
- Revoke anytime; nothing is stored on Claude's side beyond the issued token.
Tools & errors
The remote connector exposes the same tool catalogue as the npm package — generated from the public OpenAPI schema — and returns the same structured error diagnostics (request_id, retry_after_seconds, rate-limit headers). See the MCP Server page for the full tool list.