Craft MCP Server
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., "@Craft MCP Server list the features in my current workspace"
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.
Craft MCP Server
A lightweight MCP (Model Context Protocol) server providing read access to craft.io.
Installation
npm install
npm run buildRelated MCP server: OpsLevel MCP
Configuration
Set the following environment variables:
export CRAFT_API_KEY="your-api-key"
export CRAFT_WORKSPACE_ID="your-workspace-id"
export CRAFT_ACCOUNT_ID="your-account-id"
export CRAFT_PORTAL_ID="your-portal-id" # optionalCRAFT_API_KEY: Your craft.io API key
CRAFT_WORKSPACE_ID: The workspace ID (used for
/workspace/{id}/itemsendpoint)CRAFT_ACCOUNT_ID: The account ID (used for
/workspaces/{id}endpoint to list workspaces)
Usage
With Claude Code
Add to your Claude Code MCP settings (~/.claude/settings.json):
{
"mcpServers": {
"craft": {
"command": "node",
"args": ["/path/to/craft_mcp/dist/index.js"],
"env": {
"CRAFT_API_KEY": "your-api-key",
"CRAFT_WORKSPACE_ID": "your-workspace-id",
"CRAFT_ACCOUNT_ID": "your-account-id"
}
}
}
}Standalone
npm startAvailable Tools
Tool | Description |
| Test connectivity to craft.io API |
| Get workspace details |
| Get items (products, features, etc.) from workspace |
| Get a specific item by ID (e.g., |
Development
# Watch mode for development
npm run dev
# Build
npm run buildLicense
MIT
Available Tools
4 toolscraft_get_itemA
Get a specific item by ID from craft.io (e.g., UPS-1234)
Inputs: itemId (required).
craft_get_itemsC
Get items from the craft.io workspace (products, features, etc.)
Inputs: fields, limit.
craft_get_workspaceB
Get details about the configured craft.io workspace
Inputs: no named parameters.
craft_pingB
Test connectivity to craft.io API
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Official Fibery MCP server: query and update your workspace from any AI client via OAuth.
MCP server for Product Management
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Model Context Protocol server for Studex tools, notifications, and profile integrations
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceThis MCP server implementation allows users to manage and expose actions as tools from their Integration App workspace through the Model Context Protocol.10 npm36ISC

OpsLevel MCPofficial
AlicenseNot gradedqualityFmaintenanceModel Context Protocol (MCP) server for OpsLevel12MIT
argocd-mcpofficial
AlicenseCqualityCmaintenanceAn implementation of Model Context Protocol (MCP) server for Argo CD.1420,533 npm606Apache 2.0- AlicenseAqualityBmaintenanceA Model Context Protocol (MCP) server for accessing Productive.io API endpoints (projects, tasks, comments, todos), tailored for read-only operations, providing streamlined access to essential data while minimizing token consumption18MIT