Skip to main content
RedPill runs two MCP servers: This is for managing your RedPill account from an agent, not for running inference through one; for that, see Use in agents. The account server lets an agent check models, balance, billing history, API keys, workspaces, and usage, and make confirmed changes to keys and workspaces. It never returns a key secret through MCP, and it cannot spend money or change who is in your organization.

​
Connect

Add the account URL as a remote HTTP server. On first use the client opens your browser: sign in, choose the organization to authorize, and approve. No API key, client secret, or app registration is needed.
Then run /mcp in Claude Code to sign in.
Any client that supports remote HTTP MCP servers with OAuth works the same way. The agent documents at llms.txt, agents.md, and the RedPill skill tell an agent how to use both servers.

​
Tools

Every call checks your current organization membership and the same permission the dashboard uses, so an agent can do exactly what you can do there, and no more. Key listings show metadata and limits only. Archiving a workspace revokes its keys.

​
Changes need your confirmation

A write returns a preview first. Clients that support MCP forms show a confirmation; other clients repeat the call with confirm=true. Creating an API key finishes in the browser. The agent receives a short-lived link; you open it signed in as the same user, click Create, and see the secret once. The secret never passes through MCP or the model. Clients without URL elicitation support create keys in the dashboard instead.

​
Not available to agents

  • Payments, top-ups, auto-recharge, and subscriptions.
  • Organization membership, identity, and administrator operations.
  • Receipt verification. Verification has to run in the client that sent the request; see Verify a response.