Pickaxe MCP server

by aplaceforallmystuff·io.github.aplaceforallmystuff/mcp-pickaxe·v1.0.1·2 stars

MCP server for Pickaxe API - manage AI agents, knowledge bases, users, and analytics

C60/100grade C

What users say

No reviews yet

Safety scan

C60/100

Adoption

New

2 stars

Reviews

Nobody has reviewed Pickaxe yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

chat_history
Fetch conversation history for a Pickaxe agent. Use to analyze user questions, identify KB gaps, and review agent performance.
doc_connect
Connect/link a document to a Pickaxe agent, adding it to the agent's knowledge base.
doc_createwrite action
Create a new document in Pickaxe knowledge base. Can create from raw content or scrape a website URL.
doc_deletewrite action
Delete a document from Pickaxe. This removes it from all connected agents.
doc_disconnect
Disconnect/unlink a document from a Pickaxe agent, removing it from the agent's knowledge base.
doc_get
Retrieve a specific document by ID.
doc_list
List all documents in the Pickaxe studio with pagination.
memory_get_user
Get all collected memories for a specific user.
memory_list
List all memory schemas defined in the studio.
products_list
List all available products/bundles in the Pickaxe studio.
studios_list
List all configured Pickaxe studios and the current default.
user_createwrite action
Create a new user with optional product access.
user_deletewrite action
Delete a user by email.
user_get
Get details for a specific user by email.
user_invitewrite action
Send email invitations to new users with optional product access.
user_list
List all users in the Pickaxe studio with their product access and usage stats.
user_updatewrite action
Update an existing user's details, products, or usage.

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

1 high

Code scan3 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitystatic API keys via environment variables6/15
Maintenancerepository archived0/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 60/100; higher than 15% of 48,255 servers
Tools: 17; the typical server has 7
Tools that change things: 35%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 2; more than 75% of 28,688 servers

What its tools let an agent do: 11 read · 6 change

Runs npx -y mcp-pickaxe on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-pickaxe -- npx -y mcp-pickaxe

Is Pickaxe MCP server safe?: With care: it is graded C, so read the findings first (60/100). Read the Pickaxe safety report
How do I install Pickaxe?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Pickaxe need an API key?: Yes. The registry entry asks for PICKAXE_API_KEY.
Is Pickaxe maintained?: The last commit was 165 days ago (2026-05-23). The latest release is v1.0.1.
How does Pickaxe compare with other MCP servers?: safety score 60/100 (higher than 15% of 48,255 servers); tools 17 (the typical server has 7); tools that change things 35% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.