M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
C

Craft Agents

Community
Not a standard server
An open-source, document-centric multi-agent workspace with Claude and MCP integration.

This is not a typical connect-and-use MCP server; read the source repository before using it.

How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #315 of 438
Stars
★ 7.2k Very popular
Transport
stdio (local process)
Runtime
Bun · Node.js · Docker
Credentials
Optional API key
License
Apache-2.0
Last commit
44FMRS · D

Craft Agents is a feature-rich open-source agent workspace emphasizing document-centric and source integration. It offers a robust feature set including multi-session management, source connectivity, permission controls, automations, and remote server support. However, it is not an official Anthropic product and is primarily targeted at users needing a desktop interface. Credential security and local MCP isolation are considered, but users should handle permissions and sensitive data with care.

Strongest · Documentation 12/20 Weakest · Reliability 3/20

Reliability
3/20
Security and permissions
10/20
Maintenance
10/20
Documentation
12/20
Setup experience
9/20
Why each score
Reliability 3/20
Based only on the README and repository metadata, this cannot be confirmed as a standard MCP server: the server manifest is not cached and there is no verifiable MCP init or tool-list handshake. The README describes the Craft Agents desktop client, a custom WebSocket RPC server, and a CLI, not standard MCP endpoints. Claims such as --validate-server are not backed by real CI workflows or committed tests in the supplied evidence. Per static calibration, missing evidence lowers the score, so reliability is very low.
Security and permissions 10/20
No red-line issues are apparent: no malware, credential theft, real token leakage, or covert exfiltration. The README states credentials are stored with AES-256-GCM encryption, sensitive environment variables are filtered for local MCP subprocesses, and permission modes Explore/Ask/Auto exist with Ask as default. However, the implementation is not verifiable from source, the CLI run command defaults to allow-all, and the remote server relies on a token with TLS optional. Permission and confirmation coverage is therefore incomplete, supporting a score of 10.
Maintenance 10/20
The repository is not archived and the README shows Apache-2.0, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, and trademark statements, indicating a maintenance regime. However, there is no verifiable release history, commit frequency, issue response, or dependency-update evidence in the supplied material. Versioning and update-path governance are unclear, so the score is 10: active but with governance/versioning gaps.
Documentation 12/20
The README is layered and detailed: installation, CLI, remote server, environment variables, TLS, Docker, configuration, automations, troubleshooting, and security are all covered with examples. However, as an MCP server review, it lacks the server manifest, tool parameters, limitations, and cost documentation expected for MCP, and it provides no mainstream MCP client integration example. This warrants a deduction.
Setup experience 9/20
The project itself has a one-line installer, source build instructions, Docker, and CLI examples, so its own setup path is fairly clear. But this repository is not a standard MCP server and there is no example of adding it to a mainstream MCP client. Connecting it as an MCP server would require understanding a custom protocol manually; the process is manual and fragile, so the score is 9.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesRuns commands or codeUses the networkConnects to a database

Best for

  • Claude users who prefer a more document- or session-centric workflow
  • Developers who want to connect various sources and MCP servers within a desktop GUI
  • Users who want to run agents on a headless server and access via CLI

Not for

  • Users who prefer a pure CLI workflow without a desktop interface
  • Users who do not need document-centric or multi-session management
  • Users who require official Anthropic support (this is a third-party build)

Required permissions

  • User can choose permission modes: Explore (read-only), Ask to Edit, Auto (allow all)
  • User can connect third-party sources requiring authorization or API keys
  • Credentials are stored encrypted with AES-256-GCM

Risks and side effects

  • Third-party sources may require sensitive credentials, posing leakage risk
  • Local MCP servers run as subprocesses protected by environment variable filtering, but misconfiguration could lead to credential exposure
  • As a non-official tool, may lack timely stability or security updates

Setup

Before you start

Runtime：Bun · Node.js · Docker

CRAFT_SERVER_TOKEN requiredsecret Bearer token for client authentication on the headless server; generate with `openssl rand -hex 32`.
CRAFT_RPC_TLS_KEY optionalsecret Path to the PEM private key file, required alongside the cert.
SLACK_OAUTH_CLIENT_SECRET optionalsecret Slack OAuth client secret for the Slack integration.
LLM_API_KEY optionalsecret Generic API key fallback for the CLI run command; provider-specific env vars also work.
ANTHROPIC_API_KEY optionalsecret Anthropic API key used for Claude connections.
OPENAI_API_KEY optionalsecret OpenAI API key used for OpenAI provider connections.
GOOGLE_API_KEY optionalsecret API key for the Google provider (Gemini models).
Other optional settings (8)
CRAFT_RPC_HOST optional Headless server bind address; defaults to 127.0.0.1, set 0.0.0.0 for remote access.
CRAFT_RPC_PORT optional Headless server bind port; defaults to 9100.
CRAFT_RPC_TLS_CERT optional Path to a PEM certificate file; enables wss:// encrypted connections.
CRAFT_RPC_TLS_CA optional Optional PEM CA chain file for client certificate verification.
CRAFT_DEBUG optional Set to true to enable debug logging.
CRAFT_SERVER_URL optional WebSocket URL (ws:// or wss://) the desktop app or CLI uses to connect to the server.
MICROSOFT_OAUTH_CLIENT_ID optional Microsoft OAuth client ID for the Microsoft integration, baked in via .env at build time.
SLACK_OAUTH_CLIENT_ID optional Slack OAuth client ID for the Slack integration.

One-line install macOS/Linux: curl -fsSL https://agents.craft.do/install-app.sh | bash. Windows PowerShell: irm https://agents.craft.do/install-app.ps1 | iex. Build from source: git clone https://github.com/lukilabs/craft-agents-oss.git && cd craft-agents-oss && bun install && bun run electron:start.

Check that it works

Launch the Craft Agents desktop app, create a workspace, connect a source (e.g. paste your existing MCP config JSON), then mention it with @ in a session and confirm the agent's tool calls return results.

Troubleshooting

  1. Use --debug flag to enable verbose logging
  2. Check log locations: ~/Library/Logs/@craft-agent/electron/ on macOS, %APPDATA%\@craft-agent\electron\logs\main.log on Windows, ~/.config/@craft-agent/electron/logs/main.log on Linux
  3. Ensure OAuth client ID and secret are correctly configured for Google integrations
  4. Verify CRAFT_SERVER_TOKEN is set properly in remote server mode

Things to try

Once connected, you can ask your AI assistant things like:

  • Add Linear as a source and read my current issues
  • What files are in the current directory?
  • Import my existing skills and MCP config from Claude Code
  • Set up an automation that summarizes this week's completed tasks every Friday at 5pm

Use cases

Manage multiple AI agent sessions in a unified interface
Connect MCP servers and REST APIs (e.g., Gmail, Slack) as sources
Create and import skills to customize agent behavior
Set up automations to trigger agent sessions based on events

Supported clients

Claude Desktop

Listed from the project's documentation, not tested by this site.

Overview

Craft Agents is an open-source desktop application developed by craft.do for working effectively with AI agents. It provides a multi-session inbox, sources (MCP servers, REST APIs, local files), skills, automations, and permission controls. Built on the Claude Agent SDK and Pi SDK, it aims to offer a more intuitive, non-CLI way to interact with powerful agents. The app supports remote headless server mode and a command-line client.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 20e98eed968b Data synced 2026-10-12 Read the FMRS scoring method