Craft MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRAFT_API_KEY | Yes | Your craft.io API key | |
| CRAFT_PORTAL_ID | No | The portal ID (optional) | |
| CRAFT_ACCOUNT_ID | Yes | The account ID (used for /workspaces/{id} endpoint to list workspaces) | |
| CRAFT_WORKSPACE_ID | Yes | The workspace ID (used for /workspace/{id}/items endpoint) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| craft_pingB | Test connectivity to craft.io API |
| craft_get_workspaceB | Get details about the configured craft.io workspace |
| craft_get_itemsC | Get items from the craft.io workspace (products, features, etc.) |
| craft_get_itemA | Get a specific item by ID from craft.io (e.g., UPS-1234) |
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 4 tools
Each tool has a clearly distinct purpose with no ambiguity: craft_get_item retrieves a single item by ID, craft_get_items fetches multiple items from the workspace, craft_get_workspace provides workspace details, and craft_ping tests API connectivity. The descriptions clearly differentiate their scopes and use cases.
All tool names follow a consistent verb_noun pattern with the 'craft_' prefix: craft_get_item, craft_get_items, craft_get_workspace, and craft_ping. This uniformity makes the tool set predictable and easy to understand for an agent.
With 4 tools, the server is well-scoped for its purpose of interacting with craft.io. Each tool serves a distinct and necessary function—retrieving items, workspace details, and connectivity testing—without being overly sparse or bloated.
The tool set covers core read operations and connectivity testing for the craft.io domain, but lacks write or update capabilities (e.g., create, update, delete items). While agents can perform basic queries, the absence of mutation tools limits full lifecycle management, though this may be intentional for a read-focused server.