TokPortal is now on the official MCP Registry, Docker MCP Catalog, Cline and more — how to install it in 15 agents

We spent the last two weeks on distribution rather than features. The TokPortal MCP server — 91 tokportal_* tools generated from the public OpenAPI schema, covering bundles, videos, uploads, warming, analytics, bans, webhooks and comments — is now discoverable from the places agent hosts actually look, and installing it is a one-liner or a URL almost everywhere. This post lists what is live, what is still in review, and the snippet for each host.

What is listed where (as of 2026-08-18)

Official MCP Registry — published as com.tokportal/mcp at registry.modelcontextprotocol.io. Hosts that sync from the registry (the VS Code / GitHub MCP registry does) pick it up automatically.
Docker MCP Catalog — submission open in Docker's mcp-registry; once merged the server appears in Docker Desktop's MCP Toolkit.
Cline Marketplace — submitted and in review; the JSON config below works today regardless.
awesome-mcp-servers — entry proposed.
Gemini CLI extension — tokportal/gemini-cli-extension, installable with gemini extensions install https://github.com/tokportal/gemini-cli-extension.
Claude Code plugin marketplace — tokportal/claude-plugin: the MCP server, five skills and a /tokportal-status command.
Cursor plugin and agent skills — tokportal/cursor-plugin and tokportal/skills (Claude Code, Codex, Cursor, OpenClaw).
Packages — tokportal-mcp and @tokportal/node, @tokportal/cli on npm; tokportal on PyPI; github.com/tokportal/tokportal-go on Go modules; everything under the tokportal GitHub organization.

We keep this list current on the MCP page and in developer-ecosystem.json.

What changed in tokportal-mcp 1.12.1

Two things worth knowing if you already run the server.

Tool annotations. Every tool now ships MCP annotations: title, readOnlyHint on all GET-backed tools, destructiveHint on unpublish / cancel / delete / reset / unschedule / revoke, idempotentHint on GET / PUT / DELETE, and openWorldHint: false. Hosts that honor annotations can auto-approve reads and prompt before destructive calls without any per-tool configuration on your side. The remote server serves the same annotations.

Ban lifecycle tools. tokportal_list_account_bans (added in 1.12.0) is the source of truth for ban state — appeal_pending, appeal_accepted, appeal_refused, no_appeal_banned — and for the staff resolution (refund, remake, no_remake with reason_code and refund_credits). Pair it with the account.ban_appeal.submitted and account.ban_resolution.decided webhook events described in the changelog.

Two transports, same tools

Remote (Streamable HTTP): https://app.tokportal.com/api/ext/mcp, OAuth 2.1 sign-in in the browser or Authorization: Bearer sk_... / X-API-Key: sk_....
Local (stdio): npx -y tokportal-mcp with TOKPORTAL_API_KEY=sk_....

Keys come from the Developer Portal, start with sk_, and are shown once. OAuth mints a dedicated key named Claude (MCP connector) you can revoke at any time.

The 15 hosts

Claude (claude.ai, Desktop, mobile) — Settings → Connectors → Add custom connector → https://app.tokportal.com/api/ext/mcp → Authorize.
Claude Code — claude mcp add --transport http tokportal https://app.tokportal.com/api/ext/mcp, then /mcp. Or the plugin: claude plugin marketplace add tokportal/claude-plugin and claude plugin install tokportal@tokportal.
ChatGPT — Settings → Connectors → Create (developer mode) → URL above → OAuth.
OpenAI Codex CLI — ~/.codex/config.toml: [mcp_servers.tokportal] with url = "https://app.tokportal.com/api/ext/mcp", then codex mcp login tokportal.
Cursor — one-click or .cursor/mcp.json → {"mcpServers":{"tokportal":{"url":"https://app.tokportal.com/api/ext/mcp"}}}.
VS Code (Copilot agent mode) — code --add-mcp '{"name":"tokportal","type":"http","url":"https://app.tokportal.com/api/ext/mcp"}'.
Windsurf — ~/.codeium/windsurf/mcp_config.json → "tokportal": {"serverUrl": "https://app.tokportal.com/api/ext/mcp"}.
Cline — cline_mcp_settings.json → {"type":"streamableHttp","url":"https://app.tokportal.com/api/ext/mcp","headers":{"X-API-Key":"sk_..."}}.
Goose — goose configure → Remote Extension (Streaming HTTP), or the goose://extension?type=streamable_http&url=... deeplink on the MCP page.
Gemini CLI — gemini mcp add --transport http tokportal https://app.tokportal.com/api/ext/mcp, or the extension above.
Zed — context_servers.tokportal with command: npx, args: ["-y","tokportal-mcp"], env: {TOKPORTAL_API_KEY}.
JetBrains AI Assistant — Settings → Tools → AI Assistant → MCP → Add, command npx -y tokportal-mcp, env TOKPORTAL_API_KEY.
OpenClaw — clawhub install tokportal, then set TOKPORTAL_API_KEY.
n8n — MCP Client node → HTTP Streamable → endpoint above → Bearer sk_...; or the community node n8n-nodes-tokportal (see our n8n post).
Perplexity — Settings → Connectors → Add connector → Custom → URL above → OAuth (Read-only is a good default there).

Every snippet, plus Copilot Studio, Factory Droid, Hermes Agent, Dify, Flowise, Langflow, CrewAI, LangChain, Vercel AI SDK and Mastra, lives on the new Agents × jobs pages — 25 hosts × 12 jobs, each page with the exact connect block, the tool sequence and a prompt to paste.

Verify in ten seconds

Ask your assistant: "What is my TokPortal credit balance? Use the TokPortal MCP tools." A working setup calls tokportal_get_credit_balance and answers with a number. If the tool list is empty, remove and re-add the server (hosts cache sessions); if you loop on 401, finish the OAuth tab or check the key starts with sk_.

What we did not do

We did not publish a "TokPortal for X" fork per host. All hosts talk to the same server and see the same 91 tools; the only differences are the config file and the auth flow. That is also why the tool catalog is generated: when the REST API gains an endpoint, every host gets the tool on the next release, with the same annotations.

If a listing is missing for the host you use, tell us at team@tokportal.com — registry submissions are cheap and we would rather be where you already are.