chat_history
Fetch conversation history for a Pickaxe agent. Use to analyze user questions, identify KB gaps, and review agent performance.
LABSCO SUMMARY
It is built around one loop — read chat_history, find what the agent could not answer, then doc_create and doc_connect to close it.
chat_history's own description names that job: analyse user questions, identify knowledge-base gaps, review agent performance. The document calls are shaped to answer it, with doc_create accepting either raw content or a website URL to scrape. The user side is full write access rather than reporting — user_update sets products, currentUses and extraUses — and one consequence is worth knowing before a cleanup pass: doc_delete removes the document from every agent connected to it, not only from the one you were looking at.
What it is
A management surface for a Pickaxe studio: an agent's conversation history, the documents in its knowledge base, the studio's users and their product access, and the memories collected against them.
What you get
- Conversation history you can act on: chat_history fetches an agent's conversations by pickaxeId with limit, skip and a format choice, for reviewing questions asked and performance given.
- Knowledge-base documents created either way: doc_create takes rawContent or a website URL to scrape, doc_list pages the studio's documents, doc_get returns one by documentId, and doc_delete removes it from every agent it was connected to.
- Per-agent knowledge wiring: doc_connect links a document into a Pickaxe agent's knowledge base and doc_disconnect unlinks it, so one document can serve one agent and not another.
- User administration inside the studio: user_list returns users with their product access and usage stats, user_create and user_update set name, password, isEmailVerified and products, user_invite emails invitations with optional productIds, and user_get and user_delete work by email address.
- Usage counters as editable fields: user_update takes currentUses and extraUses alongside the user's product list.
- What the agent has remembered: memory_list returns the studio's memory schemas and memory_get_user returns one user's collected memories for a memoryId.
- More than one studio behind one server: studios_list reports the configured Pickaxe studios and which is the default, and a studio argument on a call sends it somewhere else.
- The product catalogue behind access grants: products_list returns the studio's available products and bundles, which are what user_create, user_update and user_invite assign.
Requirements
Your Pickaxe Studio API key (it starts with studio-) in PICKAXE_STUDIO_MAIN — one PICKAXE_STUDIO_<NAME> variable per studio if you work with several — and Node.js 18 or later. Calls about an agent's history and knowledge base also take that agent's pickaxeId.
Setup effort
One command plus a key — npx -y mcp-pickaxe, then supply credentials
USE CASES
01
Closing the gap between what users ask and what the agent knows
Read the conversations for questions the agent handled badly, turn the missing material into a document, and attach it to that agent.
02
Onboarding a group of users with the right product access
Check which products exist, invite the group with those products attached, and confirm what they ended up with.
03
Sorting out a user who says they have run out of uses
Look up the account, see the usage the studio has recorded against it, and adjust the allowance without rebuilding the user.
04
Retiring a document that has gone out of date
Find it in the studio, check what it says, unlink it from the agent that was using it, and then remove it for good.
05
Seeing what an agent has collected about a particular user
Look at which memory schemas the studio defines, then read one user's stored values against the schema you care about.
17 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
doc_connect
Connect/link a document to a Pickaxe agent, adding it to the agent's knowledge base.
doc_create
Create a new document in Pickaxe knowledge base. Can create from raw content or scrape a website URL.
doc_delete
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_create
Create a new user with optional product access.
user_delete
Delete a user by email.
user_get
Get details for a specific user by email.
user_invite
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_update
Update an existing user's details, products, or usage.
BEFORE YOU INSTALL
What to know first
Tools you get
17 tools when we connected.
Requires
- npx on PATH
- Node.js 18 or later
- PICKAXE_STUDIO_MAIN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 17 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-pickaxe": {
"command": "npx",
"args": [
"-y",
"mcp-pickaxe"
],
"env": {
"PICKAXE_STUDIO_MAIN": "<YOUR_PICKAXE_STUDIO_MAIN>"
}
}
}
}npx
TERMINAL
npx -y mcp-pickaxe
