Cowork MCP server
io.github.slashman413/cowork·v1.0.1·1 starsSelf-hosted MCP task inbox shared by Claude Code, Codex, Gemini CLI and local LLMs.
1 stars
Reviews
Write oneNobody has reviewed Cowork yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Cowork tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Cowork compares
Against every graded Email MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 73/100
- higher than 43% of 916 Email servers
- GitHub stars
- 1
- more than 65% of 493 Email servers
Install Cowork in Claude Code, Cursor or VS Code
claude mcp add cowork -- docker run -i --rm ghcr.io/slashman413/cowork:1.0.1
What the publisher says
From the Cowork repository's README, as published. We do not edit it. Read it on GitHub
🤝 Cowork — one task inbox for Claude Code, Codex, Gemini CLI & Hermes agents
A self-hosted MCP server + web dashboard that lets different AI coding agents share one task queue. Dispatch a task from any of them (or from the UI); a dispatcher routes it to a named brain (model × CLI × machine), runs it, verifies the result, and falls back to the next brain on rate limits. Workflows, artifacts, remote machines and cost/usage meters are built in.
(JOIN-AS-A-BRAIN.md): COWORK_URL=http://:6868 HOST= node cowork/deploy/remote-brain-client.mjs
- Mixed-vendor agents, one inbox: Claude Code, Codex, Gemini CLI / Antigravity, Hermes, Ollama.
- Brain routing with fallback chains: route by role, pin by task, fail over on quota errors.
- Plain files on disk: the task store is files. No database to run.
- Remote brains: another machine joins with one command and offers its models
Jump to: Quick Start · Connecting agents · Dispatcher · Brains · Workflows · MCP tools
Screenshots
One dark-themed single pane of glass for the whole operation: live host metrics (CPU / GPU / memory / temp), open-task and Agencies counters, the dispatcher's current role → model chains, and a real-time activity feed.
The Workflows, Task Inbox, Brains, Connections, and Chat views are shown in context throughout this README.
Supported Platforms
Quick Start
Prerequisites
cowork/agency-agents (the Agencies — 285 agents). Clone with submodules:
- Node.js ≥ 20 (tested with v22)
- npm ≥ 10
- The agency-agents repo — bundled as a git submodule at
git clone --recurse-submodules https://github.com/slashman413/cowork
# already cloned without it? initialise the submodule:
git submodule update --initFast path — two scripts (recommended)
From the repo root, after cloning with submodules (above):
# 1. Build + launch the server (installs deps, builds, starts a systemd user service)
deploy/install-server.sh
# 2. Drop the coordination skill + MCP connection into your agent clients on this box
deploy/install-skill.sh # auto-detects Claude Code / Hermes / Antigravityinstall-server.sh generates a systemd unit with this machine's real node path and working dir (nothing to hand-edit), or pass --foreground to launch in the terminal and --build-only to stop after building. install-skill.sh copies the right per-client skill into place and, for Claude Code, merges mcpServers.cowork into ~/.claude.json non-destructively (add --url http://:6868 for a remote server; --client claude|hermes|agy|all to target one). The numbered steps below are the same thing, broken out for when you want to do it by hand.
Container (hub only)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Cowork: common questions
- Is Cowork MCP server safe?
- Mostly: it is graded B (73/100). Read the Cowork safety report
- How do I install Cowork?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Cowork need an API key?
- Yes. The registry entry asks for
COWORK_API_KEY. - Is Cowork maintained?
- The last commit was 7 days ago (2026-10-28). The latest release is v1.0.1.
- What can I use instead of Cowork?
- Servers from other publishers that do the same job: smbCloud Mail & Auth MCP server, Inbox Zero MCP server and Atomic Mail MCP server.
- How does Cowork compare with other Email MCP servers?
- safety score 73/100 (higher than 43% of 916 Email servers); github stars 1 (more than 65% of 493 Email servers). Full comparison.
Alternatives to Cowork
Same job from other publishers: the closest match first, then the best rated.
smbCloud Mail & AuthEmail infrastructure and authentication for developers: domains, inbox routes, auth apps, deploys.not reviewedEstablishedA
Inbox ZeroSearch Gmail and Outlook, save drafts, manage email rules, and view email stats.not reviewedEstablishedA- Atomic MailProgrammable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.not reviewedEstablishedA
- Email Inbox API + Sending by SendmuxAI email inbox and sending tools with attachments, search, live events, and webhooks.not reviewedEstablishedA
- three.ws NotificationsRead the inbox, mark items read, manage delivery preferences, and register Web Push devices.not reviewedEstablishedB