@createworker/mcp
Official# @createworker/mcp
MCP (Model Context Protocol) server for [CreateWorker](https://www.createworker.com). Drive AI workers — create and run tasks, read deliverables, approve actions, manage knowledge, and connect your own apps — directly from **Claude Code**, **Claude Desktop**, **Cursor**, and any other MCP client.
> Requires Node 18+ and a CreateWorker API key (create one in your dashboard under **Developer**).
## Use it in Claude Code
**Local (npx):**
```bash
claude mcp add createworker --env CREATEWORKER_API_KEY=cw_live_… -- npx -y @createworker/mcp
```
**Remote (hosted, zero-install):**
```bash
claude mcp add --transport http createworker https://www.createworker.com/api/mcp \
--header "Authorization: Bearer cw_live_…"
```
## Claude Desktop
Add to `claude_desktop_config.json`:
```json
{
"mcpServers": {
"createworker": {
"command": "npx",
"args": ["-y", "@createworker/mcp"],
"env": { "CREATEWORKER_API_KEY": "cw_live_…" }
}
}
}
```
## Cursor
Add to `.cursor/mcp.json` (same `command`/`args`/`env` shape as above).
## Configuration
| Env var | Required | Default |
| --- | --- | --- |
| `CREATEWORKER_API_KEY` | yes | — |
| `CREATEWORKER_BASE_URL` | no | `https://www.createworker.com` |
## Tools
Workers (`workers_list`, `worker_get/create/update/delete` — `create`/`update` take `externalExecutor`) · Tasks (`tasks_list`, `task_get/create/cancel/wait/deliverables`) · External-worker runner (`task_claim`, `task_progress`, `deliverable_submit`) · Chat (`chat_pending`, `chat_history`, `chat_reply`) · `approval_decide` · `clarification_answer` · `deliverable_get` · Knowledge (`knowledge_list/get/create/delete`) · Integrations — connect your own app (`connections_list`, `connection_create_api`, `connection_create_webhook`, `connection_delete`, `bindings_list`, `binding_create`, `binding_delete`) · `webhook_register` · `account_get`, `usage_list`.
A key's scopes and each worker's autonomy level still bound what actually executes — write actions stay approval-gated unless a worker is set to auto-execute.
## Example prompts
- "List my CreateWorker workers, then create a task for the support worker to summarize today's tickets and wait for the result."
- "Connect my site's API (https://api.example.com, bearer token) and bind it to my content worker so it can publish posts."
- "Be the runner for my external worker: poll `tasks_list` for ASSIGNED tasks, `task_claim` the oldest, do the work, and `deliverable_submit` the result. Also answer any `chat_pending` messages with `chat_reply`." (see the External Workers guide)
## License
MIT
TDQS
Scored across 28 tools
Each tool targets a distinct resource and action (account, approval, binding, clarification, connection, deliverable, knowledge, task, usage, webhook, worker). The descriptions clearly differentiate between similar-sounding tools like task_deliverables vs deliverable_get and webhook_register vs connection_create_webhook. No overlapping purposes.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., account_get, binding_create, task_cancel). Pluralization of nouns (bindings_list vs worker_get) is the only minor variation but does not detract from consistency.
28 tools cover a broad platform with workers, connections, tasks, knowledge, approvals, etc. While slightly on the higher side, each tool serves a clear purpose in the workflow and none feel redundant.
The tool set covers the full lifecycle for workers and tasks (CRUD, execution, approval, deliverables). Minor gaps include missing update functionality for knowledge documents and connections, but these are not critical for core workflows.