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
C
Craft Agents
Community
An open-source, document-centric multi-agent workspace with Claude and MCP integration.
GitHub source repository ↗
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.
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.
Tools
The tool list has not been reviewed yet.
Setup
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.
Fit and risk
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
Troubleshooting
- Use --debug flag to enable verbose logging
- 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
- Ensure OAuth client ID and secret are correctly configured for Google integrations
- Verify CRAFT_SERVER_TOKEN is set properly in remote server mode
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 DesktopFull support