MCP Pickaxe Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PICKAXE_STUDIO_DEV | No | Your Pickaxe Studio API key for development environment | |
| PICKAXE_STUDIO_MAIN | No | Your Pickaxe Studio API key (starts with 'studio-') | |
| PICKAXE_DEFAULT_STUDIO | No | The default studio to use when none is specified (e.g., 'PRODUCTION', 'STAGING', 'DEV') | |
| PICKAXE_STUDIO_STAGING | No | Your Pickaxe Studio API key for staging environment | |
| PICKAXE_STUDIO_PRODUCTION | No | Your Pickaxe Studio API key for production environment |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| studios_listA | List all configured Pickaxe studios and the current default. |
| chat_historyB | Fetch conversation history for a Pickaxe agent. Use to analyze user questions, identify KB gaps, and review agent performance. |
| doc_createB | Create a new document in Pickaxe knowledge base. Can create from raw content or scrape a website URL. |
| doc_connectA | Connect/link a document to a Pickaxe agent, adding it to the agent's knowledge base. |
| doc_disconnectB | Disconnect/unlink a document from a Pickaxe agent, removing it from the agent's knowledge base. |
| doc_listB | List all documents in the Pickaxe studio with pagination. |
| doc_getB | Retrieve a specific document by ID. |
| doc_deleteB | Delete a document from Pickaxe. This removes it from all connected agents. |
| user_listA | List all users in the Pickaxe studio with their product access and usage stats. |
| user_getC | Get details for a specific user by email. |
| user_createC | Create a new user with optional product access. |
| user_updateC | Update an existing user's details, products, or usage. |
| user_deleteC | Delete a user by email. |
| user_inviteC | Send email invitations to new users with optional product access. |
| products_listB | List all available products/bundles in the Pickaxe studio. |
| memory_listB | List all memory schemas defined in the studio. |
| memory_get_userC | Get all collected memories for a specific user. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.