Connect an MCP client
Connect Toolporten and get access to 500+ tools through custom toolboxes (MCP servers). Add a remote connector in Cursor, Claude, ChatGPT, or Grok.
Toolporten MCP. URL https://data.toolporten.com/mcp/manage. OAuth with an empty Client ID, DCR + PKCE, scope mcp:tools. Pause for Approve. An account API key is under Advanced.
Toolboxes
Toolporten MCP creates toolboxes, then clients connect to /mcp/{toolboxId}. That catalog endpoint cannot call product tools.
A toolbox is the kit you picked. Its URL runs those tools. Public job pages (QR, cutout, reel, and the rest) are separate surfaces on the same host.
Keys
Most people use Connect Toolporten MCP (OAuth). No key needed.
An account API key (tpa_…) is for an agent that runs without a browser login (Grok Build, CI) and cannot click OAuth Approve. It calls Toolporten MCP as your account to create toolboxes and mint product tp_… secrets. Account keys are more powerful than toolbox keys.
Product toolbox keys (tp_…) cannot access Toolporten MCP. Use OAuth (empty Client ID, DCR + PKCE, scope mcp:tools) at https://data.toolporten.com/mcp/manage, and pause for Approve, or an account key (tpa_…).
llms.txt
llms.txt is the short note for the public Background Remover MCP. llms-full.txt is the longer one: connect steps, upload session, and limits. Both stay plain text.