Mcp Pickaxe
Wire your coding agent to Pickaxe so you can manage studio AI agents, knowledge bases, users, and analytics from the editor without leaving the terminal.
Overview
mcp-pickaxe is an MCP server for the Build phase that lets your agent manage Pickaxe studio AI agents, knowledge bases, users, and analytics via the official API.
What is this MCP server?
- stdio MCP package mcp-pickaxe on npm (v1.0.1)
- Requires PICKAXE_API_KEY and PICKAXE_STUDIO_ID
- Manage AI agents and knowledge bases in your Pickaxe studio
- User and analytics operations exposed as agent-callable tools
- GitHub: aplaceforallmystuff/mcp-pickaxe
- Server version 1.0.1
- 2 required secrets/env: PICKAXE_API_KEY, PICKAXE_STUDIO_ID
- Transport: stdio via npm identifier mcp-pickaxe
What problem does it solve?
Toggling between the Pickaxe dashboard and your IDE breaks flow when you need quick agent or KB changes during a build session.
Who is it for?
Indie builders already on Pickaxe who want hands-free studio ops from Claude Code or Cursor.
Skip if: Teams not using Pickaxe or anyone who only needs a one-off REST script without MCP.
What do I get? / Deliverables
After registering the server with your API key and studio ID, your agent can perform Pickaxe management actions as tools from chat.
- Registered stdio MCP server for Pickaxe
- Agent-callable tools for agents, KBs, users, and analytics
- Repeatable Pickaxe ops without leaving the IDE
Recommended MCP Servers
Journey fit
Pickaxe is a product you integrate while assembling your agent stack and backend workflows, not a one-off launch or ops-only utility. The server speaks the Pickaxe HTTP API via stdio MCP, which is classic third-party platform wiring during build.
How it compares
Pickaxe API MCP bridge, not a standalone agent skill or hosted Pickaxe replacement.
Common Questions / FAQ
Who is mcp-pickaxe for?
Solo and small-team builders who run Pickaxe studios and want their coding agent to manage agents, knowledge bases, users, and analytics through MCP.
When should I use mcp-pickaxe?
Use it during Build when you are iterating on Pickaxe agents and need the agent in your editor to call Pickaxe instead of manual dashboard work.
How do I add mcp-pickaxe to my agent?
Install the npm package mcp-pickaxe, set PICKAXE_API_KEY and PICKAXE_STUDIO_ID, and add a stdio MCP server entry pointing at that binary in Claude Code, Cursor, or Windsurf.