MCP Server
Talk to your Pitchfork dashboard from Claude, Cursor, Windsurf, or any MCP-compatible AI assistant.
MCP Server
Pitchfork ships a hosted Model Context Protocol server so you can drive your accounts, proxies, scripts, agents, groups, and triggers directly from any MCP-compatible AI assistant — Claude Desktop, Cursor, Windsurf, Continue, or your own client.
Anything you can do in the dashboard, you can ask the assistant to do for you.
The MCP server uses the same API key as the Public API. One key, two surfaces.
One-click setup
The fastest way to wire up your AI assistant:
- Log in to your Pitchfork dashboard
- Open MCP in the sidebar
- Pick the API key you want to use
- Click Copy setup prompt for AI
- Paste it into Claude, Cursor, or any other AI assistant — it knows the rest
The assistant will fetch the live MCP documentation, generate the right config for your client, and tell you exactly where to paste it.
Endpoints
| Transport | URL |
|---|---|
| Streamable HTTP (recommended) | https://api.getpitchfork.com/mcp |
| Server-Sent Events (legacy) | https://api.getpitchfork.com/mcp/sse |
| Live machine-readable docs | https://api.getpitchfork.com/docs/mcp |
| Agent-friendly setup guide | https://api.getpitchfork.com/docs/mcp/agent-instructions |
Use Streamable HTTP unless your client only supports SSE.
Authentication
Pass your Pitchfork API key on every request. Both headers are accepted equally — use whichever your MCP client makes easiest:
# Option 1: X-API-Key header (simplest for MCP client config)
X-API-Key: pfk_live_your_api_key_here
# Option 2: Authorization header (standard OAuth-style)
Authorization: Bearer pfk_live_your_api_key_hereEvery MCP request is a POST, so the auth middleware requires a Read-Write API key for every
tool call — including tools/list and read actions like action: list. Read-only keys can
connect but every call will be rejected with 403 insufficient_permissions.
Generate or rotate your key from Account Settings → API Keys in the dashboard. See the Public API guide for the full walkthrough.
Manual client setup
If you'd rather configure your client by hand, here are the snippets.
Available tools
Each tool is a single entry-point that handles list / get / create / update / delete via an action argument,
so you don't need to memorize dozens of endpoints — just ask the assistant.
| Tool | What it manages |
|---|---|
manage_accounts | OSRS accounts: CRUD, search, import/export, stop, auth-capture, bulk rename, proxy pairing |
manage_proxies | Proxy pool and proxy assignments |
manage_scripts | Script activities and their schedules |
manage_agents | Agent machines and their status |
manage_groups | Account groups and proxy groups |
manage_triggers | Automated triggers and their actions |
manage_client_instances | Templated client launch configurations (list, get, CRUD, launch) |
manage_account_tools | Automated account tools — ban appeal, Jagex upgrade, account creation, 2FA enable, status check (paid plan) |
Ask the assistant things like:
- "List my top five accounts by total level."
- "Create a new account with login
foo@bar.comand assign it to the Mains group." - "Disable every trigger that targets the Pures group."
- "Which proxies haven't been used in the last week?"
The full schema for every tool is published live at
https://api.getpitchfork.com/docs/mcp — your assistant will fetch
it automatically, so it always sees the same version of the API your account is using.
Rate limits
Same as the Public API: 1,000 requests per hour per API key. When you hit the limit, you'll get a 429
with a Retry-After header. Each MCP tool call counts as one request.
Troubleshooting
Need Help?
- Use the Copy setup prompt for AI button on the in-app MCP page — the prompt itself is a self-debugging guide.
- Join our Discord for community support.
- Check the FAQ for common questions.
Was this page helpful?