MCP Pickaxe Server
The MCP Pickaxe Server connects AI assistants like Claude to the Pickaxe platform, enabling natural language management of AI agents, knowledge bases, users, and analytics.
Studio Management: List configured studios, view the current default, and switch between multiple environments (production, staging, dev).
Chat History & Analytics: Fetch and analyze conversation logs for up to 100 conversations at a time, identify knowledge gaps, review agent performance, and export data in human-readable or raw metadata formats.
Knowledge Base Management: Create documents from raw text or scraped URLs, list/retrieve/delete documents with pagination, and connect/disconnect documents from agents to manage their knowledge bases.
User Management: Perform CRUD operations on users, manage product access and usage limits, track usage statistics, send bulk invitations, and update user details.
Product Management: List available products and bundles in the studio.
Memory Management: List memory schemas, retrieve collected memories for specific users (filterable by schema ID), and support pagination for personalization auditing and privacy compliance.
Multi-Studio Operations: Seamlessly work across multiple studios in a single session, compare data between environments, and automate administrative tasks like security monitoring, knowledge base maintenance, and agent performance reviews.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Pickaxe Server analyze chat history from the last week for my customer support agent"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Pickaxe Server

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.
Why Use This?
If you're building AI agents on Pickaxe, this MCP server lets you:
Analyze agent conversations - Review chat history to identify knowledge gaps and improve agent performance
Manage knowledge bases - Create, update, and connect documents to your agents without leaving your AI workflow
Handle user management - Create users, manage access, send invitations, and track usage
Work across multiple studios - Seamlessly switch between different Pickaxe studios in a single session
Automate workflows - Let Claude handle repetitive Pickaxe admin tasks
Related MCP server: Forge MCP Server
Features
Category | Tools |
Studios | List configured studios, switch between them |
Chat History | Fetch and analyze agent conversation logs |
Documents | Create, list, get, delete, connect/disconnect to agents |
Users | Create, list, get, update, delete, invite |
Products | List available products and bundles |
Memory | List memory schemas, retrieve user memories |
Prerequisites
Node.js 18+
A Pickaxe account with API access
Your Pickaxe Studio API key(s)
Installation
Option 1: Install from npm (recommended)
npx mcp-pickaxeOr install globally:
npm install -g mcp-pickaxeOption 2: Clone and Build
git clone https://github.com/aplaceforallmystuff/mcp-pickaxe.git
cd mcp-pickaxe
npm install
npm run buildConfiguration
1. Get Your Pickaxe API Key
Log in to Pickaxe Studio
Navigate to Settings > API
Copy your Studio API key (starts with
studio-)
2. Configure Your MCP Client
For Claude Desktop
Add to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"pickaxe": {
"command": "node",
"args": ["/path/to/mcp-pickaxe/dist/index.js"],
"env": {
"PICKAXE_STUDIO_MAIN": "studio-your-api-key-here"
}
}
}
}For Claude Code
Add to ~/.claude.json:
{
"mcpServers": {
"pickaxe": {
"command": "node",
"args": ["/path/to/mcp-pickaxe/dist/index.js"],
"env": {
"PICKAXE_STUDIO_MAIN": "studio-your-api-key-here"
}
}
}
}Multi-Studio Configuration
To work with multiple Pickaxe studios, add multiple environment variables:
{
"env": {
"PICKAXE_STUDIO_PRODUCTION": "studio-xxx-xxx-xxx",
"PICKAXE_STUDIO_STAGING": "studio-yyy-yyy-yyy",
"PICKAXE_STUDIO_DEV": "studio-zzz-zzz-zzz",
"PICKAXE_DEFAULT_STUDIO": "PRODUCTION"
}
}Then specify which studio to use in your requests:
If you set
PICKAXE_DEFAULT_STUDIO, that studio is used when none is specifiedIf only one studio is configured, it's used automatically
Otherwise, pass
studio="STAGING"(or similar) to any tool
Use Cases
These are real workflows built with mcp-pickaxe in production environments.
1. Security Monitoring with n8n
Scenario: Detect prompt injection attempts across 29+ AI agents in real-time.
Implementation:
An n8n workflow polls chat_history hourly for all agents, runs messages against injection detection patterns (stored in Notion), and routes alerts by severity:
HIGH/CRITICAL → Telegram alert + Notion log
LOW/MEDIUM → Notion log only
n8n Schedule (hourly)
→ Fetch patterns from Notion
→ Loop through 29 pickaxe IDs
→ Fetch chat_history for each
→ Detect injections (regex patterns)
→ Route by severity → Alert/LogTools used: chat_history, studios_list
Result: Real-time security monitoring across an entire studio with dynamic pattern management and severity-based alerting.
2. Knowledge Base Auto-Research Pipeline
Scenario: Automatically fact-check and maintain 31+ knowledge base articles.
Implementation: An n8n workflow queries KB articles from Notion, extracts key claims, fact-checks via Perplexity API, classifies changes by risk level, and routes to auto-update or human review.
Daily Schedule (2am)
→ Query KB articles from Notion
→ Filter by day (hash-based, ~1/7th daily)
→ Extract key claims
→ Perplexity fact-check
→ Classify: none/low/major risk
→ Route: auto-update or create review taskTools used: doc_list, doc_get, doc_create, doc_connect
Result: KB content stays current with automated fact-checking and human-in-the-loop for major changes.
3. Agent Performance Review
Scenario: Quarterly review of a training studio to identify KB gaps and user pain points.
Workflow:
1. "Fetch chat history from my training agents"
2. "Analyze: which questions got unclear or uncertain responses?"
3. "List all KB documents - which topics are missing?"
4. "Check user stats - who's most active, who's churning?"
5. "Create KB documents addressing the top 3 gaps"
6. "Connect new documents to the relevant agents"Tools used: chat_history, doc_list, doc_create, doc_connect, user_list
Result: Data-driven KB improvements based on actual user conversations rather than guesswork.
4. Multi-Studio Operations
Scenario: Managing multiple Pickaxe studios from a single Claude session.
Configuration:
{
"env": {
"PICKAXE_STUDIO_PRODUCTION": "studio-xxx",
"PICKAXE_STUDIO_STAGING": "studio-yyy",
"PICKAXE_STUDIO_DEV": "studio-zzz",
"PICKAXE_DEFAULT_STUDIO": "PRODUCTION"
}
}Workflow:
1. "List users in PRODUCTION - how many signups this month?"
2. "Switch to STAGING - list products"
3. "Compare KB document counts across all studios"
4. "Find which studio has the most chat activity"Tools used: studios_list, user_list, doc_list, products_list
Result: Cross-studio visibility without switching contexts or API keys manually.
5. User Memory Auditing
Scenario: Review what your agents remember about users for personalization and privacy compliance.
Workflow:
1. "List all memory schemas defined in the studio"
2. "Get memories for user@example.com"
3. "What does the system know about this user's situation?"
4. "Which memory fields are most populated across users?"Example output:
User: maria.example@email.com
Nickname: "Cautious Educator from Madrid"
Summary: "Teaching [language] for [platform] at low hourly rate,
considering self-employment status due to
uncertain income"
Memories: 1 storedTools used: memory_list, memory_get_user, user_list
Result: Visibility into personalization data for both product improvement and GDPR compliance.
Quick Start Examples
Once configured, you can interact with Pickaxe through natural language:
Analyze Agent Performance
"Show me the last 20 conversations from my support agent"
"What questions are users asking that my agent can't answer?"
Manage Knowledge Base
"Create a new document called 'FAQ' with this content: [your content]"
"Connect the FAQ document to my customer support agent"
"List all documents in my knowledge base"
User Management
"Show me all users and their usage stats"
"Create a new user with email user@example.com and give them access to the Pro product"
"Send invitations to these emails: [list of emails]"
Multi-Studio Operations
"List all users in my staging studio"
"Compare the documents between production and staging"
Available Tools
Studio Management
studios_list- List all configured studios and the current default
Chat History
chat_history- Fetch conversation history for an agentParameters:
pickaxeId,skip,limit,format("messages" or "raw"),studio
Document Management
doc_create- Create document from content or URLdoc_list- List all documents (with pagination)doc_get- Get a specific documentdoc_delete- Delete a documentdoc_connect- Link document to an agentdoc_disconnect- Unlink document from an agent
User Management
user_list- List all users with access and usage infouser_get- Get a specific user by emailuser_create- Create a new useruser_update- Update user details, products, or usageuser_delete- Delete a useruser_invite- Send email invitations
Products
products_list- List available products/bundles
Memory
memory_list- List memory schemasmemory_get_user- Get collected memories for a user
Development
# Run in development mode (auto-reloads)
npm run dev
# Build for production
npm run build
# Run the built version
npm startTroubleshooting
"No Pickaxe studios configured"
Ensure you have at least one PICKAXE_STUDIO_* environment variable set in your MCP config.
"Studio not found"
Check that the studio name matches exactly (case-insensitive). Run studios_list to see available options.
"Pickaxe API error (401)"
Your API key is invalid or expired. Get a new one from Pickaxe Studio settings.
"Pickaxe API error (403)"
Your API key doesn't have permission for this operation. Check your Pickaxe account permissions.
Contributing
Contributions are welcome! Please see CONTRIBUTING.md for guidelines.
License
MIT License - see LICENSE for details.
Links
Available Tools
17 toolschat_historyB
Fetch conversation history for a Pickaxe agent. Use to analyze user questions, identify KB gaps, and review agent performance.
Inputs: pickaxeId (required), studio, skip, limit, +1 more.
doc_connectA
Connect/link a document to a Pickaxe agent, adding it to the agent's knowledge base.
Inputs: documentId (required), pickaxeId (required), studio.
doc_createB
Create a new document in Pickaxe knowledge base. Can create from raw content or scrape a website URL.
Inputs: name (required), studio, rawContent, website.
doc_deleteB
Delete a document from Pickaxe. This removes it from all connected agents.
Inputs: documentId (required), studio.
doc_disconnectB
Disconnect/unlink a document from a Pickaxe agent, removing it from the agent's knowledge base.
Inputs: documentId (required), pickaxeId (required), studio.
doc_getB
Retrieve a specific document by ID.
Inputs: documentId (required), studio.
doc_listB
List all documents in the Pickaxe studio with pagination.
Inputs: studio, skip, take.
memory_get_userC
Get all collected memories for a specific user.
Inputs: email (required), studio, memoryId, skip, +1 more.
memory_listB
List all memory schemas defined in the studio.
Inputs: studio, skip, take.
products_listB
List all available products/bundles in the Pickaxe studio.
Inputs: studio.
studios_listA
List all configured Pickaxe studios and the current default.
Inputs: no named parameters.
user_createC
Create a new user with optional product access.
Inputs: email (required), studio, name, password, +2 more.
user_deleteC
Delete a user by email.
Inputs: email (required), studio.
user_getC
Get details for a specific user by email.
Inputs: email (required), studio.
user_inviteC
Send email invitations to new users with optional product access.
Inputs: emails (required), studio, productIds.
user_listA
List all users in the Pickaxe studio with their product access and usage stats.
Inputs: studio, skip, take.
user_updateC
Update an existing user's details, products, or usage.
Inputs: email (required), studio, name, products, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource types (documents, users, memories, products, studios, chat history) and specific actions (create, get, list, update, delete, connect/disconnect), making it easy for an agent to select the correct tool without confusion.
Tool names follow a highly consistent verb_noun pattern throughout, such as doc_create, user_list, memory_get_user, and studios_list. All tools use snake_case with clear, descriptive names, providing a predictable and readable structure across the entire set.
With 17 tools, the count is well-scoped for managing a Pickaxe studio's resources. Each tool earns its place by covering essential operations like CRUD for documents and users, plus additional functions for linking, memory, and studio management, without being excessive or insufficient for the domain.
The tool surface provides complete CRUD/lifecycle coverage for the Pickaxe domain, including documents, users, memories, products, studios, and chat history. There are no obvious gaps; agents can perform all necessary operations from creation to deletion, with additional utilities like connecting documents and inviting users, ensuring no dead ends in workflows.
Maintenance
Related MCP Connectors
Connect your AI agent to 300+ methods and 100+ live tools
Access your Callin.io AI phone agents, call history and transcripts from any AI assistant.
Connect AI agents to 1000+ apps with managed authentication and tool-calling.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables seamless integration with AnythingLLM instances, providing complete workspace management, chat operations, document handling, user administration, and AI agent configuration through natural language.3859 npm16MIT

Forge MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceConnects AI assistants to the complete Salesforge product suite, enabling management of workspaces, contacts, sequences, mailboxes, domains, and more across multiple sales tools.59 npm2MIT- AlicenseAqualityDmaintenanceConnects AI assistants to live Purl Studio projects, enabling reading objects, modifying scripts, and setting properties.26MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to look up and update WorkForceAI platform data, including voice agents, campaigns, phone numbers, call logs, and dashboard stats, through natural language.-