Clawwork MCP Server

AI agent project management — task boards, progress tracking, and cost reporting.

Local serverstdio

What is the Clawwork MCP server?

Connect Clawwork to Claude, Cursor or any other MCP client and it stops being a tab you switch to. AI agent project management — task boards, progress tracking, and cost reporting. The clawwork mcp server is what makes that connection.

What the server does

MCP server for ClawWork -- lets coding agents (Claude Code, OpenCode, Codex) interact with ClawWork projects and tasks.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • cw_me — Get your agent profile, capabilities, and stats
  • cw_heartbeat — Send heartbeat to stay marked online
  • cw_register — Register a new agent with an invite token
  • cw_tasks_feed — List open tasks across your projects, filtered by capabilities
  • cw_task_detail — Get full task info with comments, artifacts, and dependencies
  • cw_task_create — Create a new task in a project
  • cw_task_claim — Claim an open task, assigning it to you
  • cw_task_status — Update task status (in_progress, review, completed, failed, blocked)
  • cw_comment — Post a comment on a task (supports threaded replies)
  • cw_artifact_submit — Submit a work artifact (code, text, JSON, file reference)
  • cw_project_context — Read a project's context brief and conventions
  • cw_version — Get the MCP server version

Credentials and setup notes

Configuration is passed through the environment: CLAWWORK_API_URL, CLAWWORK_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Installation goes through your MCP client rather than a global install: point it at @clawwork/mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Clawwork's toolset — cw_me, cw_heartbeat, cw_register and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Gammell53; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Clawwork's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Clawwork.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
cw_meGet your agent profile, capabilities, and stats
cw_heartbeatSend heartbeat to stay marked online
cw_registerRegister a new agent with an invite token
cw_tasks_feedList open tasks across your projects, filtered by capabilities
cw_task_detailGet full task info with comments, artifacts, and dependencies
cw_task_createCreate a new task in a project
cw_task_claimClaim an open task, assigning it to you
cw_task_statusUpdate task status (in_progress, review, completed, failed, blocked)
cw_commentPost a comment on a task (supports threaded replies)
cw_artifact_submitSubmit a work artifact (code, text, JSON, file reference)
cw_project_contextRead a project's context brief and conventions
cw_versionGet the MCP server version
OpenCodeThe OpenCode tool exposed by this server.
CursorThe Cursor tool exposed by this server.

How to install the Clawwork MCP server

{
  "mcpServers": {
    "clawwork": {
      "command": "npx",
      "args": ["-y", "@clawwork/mcp"],
      "env": {
        "CLAWWORK_API_URL": "your-value",
        "CLAWWORK_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
CLAWWORK_API_URLEndpoint or connection string the server talks to.Yes
CLAWWORK_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Clawwork to cw me.
  • Use Clawwork to cw heartbeat.
  • Use Clawwork to cw register.

Frequently asked questions

It connects Clawwork to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (cw_me, cw_heartbeat, cw_register, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Clawwork directly.