MCP server for Pickaxe API - manage AI agents, knowledge bases, users, and analytics
MCP Pickaxe MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Pickaxe directly instead of describing what you should do. MCP server for Pickaxe API - manage AI agents, knowledge bases, users, and analytics.
An MCP (Model Context Protocol) server that connects AI assistants like Claude to the Pickaxe platform. Manage your AI agents, knowledge bases, users, and analytics directly through natural language.
The server ships on npm as mcp-pickaxe, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once MCP Pickaxe is connected, these are the calls the assistant has available:
Products — The Products tool exposed by this serverMemory — The Memory tool exposed by this serverYou will need 5 environment variables: PICKAXE_STUDIO_MAIN, PICKAXE_STUDIO_PRODUCTION, PICKAXE_STUDIO_STAGING, PICKAXE_STUDIO_DEV, PICKAXE_DEFAULT_STUDIO. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Pickaxe's toolset — Products, Memory — is a fair guide to whether it matches your workflow. It is maintained by aplaceforallmystuff; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Pickaxe's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Products | The Products tool exposed by this server. |
| Memory | The Memory tool exposed by this server. |
{
"mcpServers": {
"pickaxe": {
"command": "npx",
"args": ["-y", "mcp-pickaxe"],
"env": {
"PICKAXE_STUDIO_MAIN": "your-value",
"PICKAXE_STUDIO_PRODUCTION": "your-value",
"PICKAXE_STUDIO_STAGING": "your-value",
"PICKAXE_STUDIO_DEV": "your-value",
"PICKAXE_DEFAULT_STUDIO": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PICKAXE_STUDIO_MAIN | Configuration value read at startup. | Optional |
| PICKAXE_STUDIO_PRODUCTION | Configuration value read at startup. | Optional |
| PICKAXE_STUDIO_STAGING | Configuration value read at startup. | Optional |
| PICKAXE_STUDIO_DEV | Configuration value read at startup. | Optional |
| PICKAXE_DEFAULT_STUDIO | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.