mcpbeat Sign in

MCP Pickaxe MCP Server

local only

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.

Installs per day peak 17 · avg 7 · +34% w/w
a month agotoday
57
Installs / week
npm · mcp-pickaxe
2
Stars
0 open issues
25 Feb 2026
Last commit
no releases in 90 days
MIT
License
JavaScript

What the code does

We read the source, 6 d ago · rules 995398eba69f

Capabilities

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.

Dumps the whole environment src/index.ts:18
  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.

This code can reach further than it looks

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.

Three servers free · no card

Connect this server

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.

run in your terminal
claude mcp add mcp-pickaxe -e 'PICKAXE_API_KEY=<PICKAXE_API_KEY>' -e 'PICKAXE_STUDIO_ID=<PICKAXE_STUDIO_ID>' -- npx -y mcp-pickaxe
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-pickaxe": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-pickaxe"
      ],
      "env": {
        "PICKAXE_API_KEY": "<PICKAXE_API_KEY>",
        "PICKAXE_STUDIO_ID": "<PICKAXE_STUDIO_ID>"
      }
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-pickaxe]
command = "npx"
args = ["-y", "mcp-pickaxe"]
env = { PICKAXE_API_KEY = "<PICKAXE_API_KEY>", PICKAXE_STUDIO_ID = "<PICKAXE_STUDIO_ID>" }
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-pickaxe": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-pickaxe"
      ],
      "env": {
        "PICKAXE_API_KEY": "<PICKAXE_API_KEY>",
        "PICKAXE_STUDIO_ID": "<PICKAXE_STUDIO_ID>"
      }
    }
  }
}
.vscode/mcp.json
{
  "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.

Alternatives to MCP Pickaxe

same job, measured the same way
GLPI MCP
by mhajder

MCP server for GLPI IT service management (tickets, assets, users, knowledge base)

242 installs/wk local only
Freshdesk
by wyre-technology

MCP server for Freshdesk — tickets, contacts, companies, agents, groups, and knowledge base.

local only
Freshdesk
by wyre-ai

MCP server for Freshdesk — tickets, contacts, companies, agents, groups, and knowledge base.

local only
Tencent Lexiang MCP Server
by tencent-lexiang

Tencent Lexiang AI knowledge base MCP server for searching, managing entries, and editing docs.

answering
Factsets MCP Server
by joshua-auchincloss

An MCP server that provides a local, persistent, self-maintaining knowledge base for AI agents

102 installs/wk local only
ElevenLabs Agents
by mindstone

ElevenLabs Conversational AI: agents, calls, conversations, and knowledge base for MCP hosts

57 installs/wk local only
Yuque MCP
by yuque

MCP server for Yuque — expose your knowledge base to AI assistants.

492 installs/wk local only
iknow
by iknow

Knowledge base MCP for AI agents on iknow.dev. Search, read, and maintain via OAuth.

answering

MCP Pickaxe — questions

Answers built from our own checks of this server.

Why is there no uptime for MCP Pickaxe?
MCP Pickaxe runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package mcp-pickaxe was installed 57 times last week.
Is MCP Pickaxe still maintained?
The author archived this repository on GitHub, meaning it is no longer maintained. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect MCP Pickaxe?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls mcp-pickaxe straight from npm; nothing to host, nothing to sign up for.
How many people use MCP Pickaxe?
The npm package mcp-pickaxe was installed 57 times in the last week. Week over week that is +34%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is MCP Pickaxe open source?
Yes — it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.