# RedPill for agents

RedPill exposes separate MCP servers for account operations and public documentation:

- Account: `https://service.redpill.ai/mcp`
- Documentation: `https://docs.redpill.ai/mcp`

## Connect

Add the account URL as a remote HTTP MCP server in your client. The client opens RedPill's Clerk OAuth consent flow; sign in, choose the organization to authorize, and approve access. No RedPill API key, MCP key, client secret, or pre-registered OAuth application is required for compatible CIMD clients.

The OAuth token is limited to the account MCP resource. Each tool also rechecks the user's current Clerk organization membership and the same product permission used by the RedPill Web app.

## Use

The account server covers ordinary account workflows: account and workspace details, model discovery and uptime, balances and billing history, API key metadata, usage summaries and logs, and confirmed API key or workspace changes.

Mutations require explicit confirmation. API key creation finishes on a RedPill browser page that requires the same Clerk user who started the MCP request. The secret is displayed once in that browser and is never returned through MCP or placed in model context. Clients without URL elicitation support must create keys in the RedPill Web app.

Payment, checkout, subscription, auto-recharge, identity, membership, organization URL, deployment, provider-cloud, and administrator operations are intentionally not exposed as account tools.

## Trust boundary

Use the documentation MCP for documentation rather than duplicating public content through the account server.

ACI verification must run in the native client that observed the exact request, response or stream, and pinned transport. The account MCP cannot prove those observations and does not expose a receipt-verification tool.

## Skill

The portable Agent Skill is available at `https://service.redpill.ai/skills/redpill/SKILL.md`.