MCP Pickaxe runs on your own machine — the client starts it, so there is no endpoint to ping. 57 installs a week from npm. Last commit 25 Feb 2026.
MCP server for Pickaxe API - manage AI agents, knowledge bases, users, and analytics
The author archived this repository on GitHub, meaning it is no longer maintained.
We read the source, 6 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
for (const key of Object.keys(process.env)) {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-pickaxe -e 'PICKAXE_API_KEY=<PICKAXE_API_KEY>' -e 'PICKAXE_STUDIO_ID=<PICKAXE_STUDIO_ID>' -- npx -y mcp-pickaxe
{
"mcpServers": {
"mcp-pickaxe": {
"command": "npx",
"args": [
"-y",
"mcp-pickaxe"
],
"env": {
"PICKAXE_API_KEY": "<PICKAXE_API_KEY>",
"PICKAXE_STUDIO_ID": "<PICKAXE_STUDIO_ID>"
}
}
}
}
[mcp_servers.mcp-pickaxe]
command = "npx"
args = ["-y", "mcp-pickaxe"]
env = { PICKAXE_API_KEY = "<PICKAXE_API_KEY>", PICKAXE_STUDIO_ID = "<PICKAXE_STUDIO_ID>" }
{
"mcpServers": {
"mcp-pickaxe": {
"command": "npx",
"args": [
"-y",
"mcp-pickaxe"
],
"env": {
"PICKAXE_API_KEY": "<PICKAXE_API_KEY>",
"PICKAXE_STUDIO_ID": "<PICKAXE_STUDIO_ID>"
}
}
}
}
{
"servers": {
"mcp-pickaxe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-pickaxe"
],
"env": {
"PICKAXE_API_KEY": "<PICKAXE_API_KEY>",
"PICKAXE_STUDIO_ID": "<PICKAXE_STUDIO_ID>"
}
}
}
}
Put your own values in place of
<PICKAXE_API_KEY> (Your Pickaxe studio API key), <PICKAXE_STUDIO_ID> (Your Pickaxe studio ID).
The author’s registry entry marks them as required.
MCP server for GLPI IT service management (tickets, assets, users, knowledge base)
MCP server for Freshdesk — tickets, contacts, companies, agents, groups, and knowledge base.
MCP server for Freshdesk — tickets, contacts, companies, agents, groups, and knowledge base.
Tencent Lexiang AI knowledge base MCP server for searching, managing entries, and editing docs.
An MCP server that provides a local, persistent, self-maintaining knowledge base for AI agents
ElevenLabs Conversational AI: agents, calls, conversations, and knowledge base for MCP hosts
MCP server for Yuque — expose your knowledge base to AI assistants.
Knowledge base MCP for AI agents on iknow.dev. Search, read, and maintain via OAuth.
Answers built from our own checks of this server.