@createworker/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CREATEWORKER_API_KEY | Yes | Your CreateWorker API key | |
| CREATEWORKER_BASE_URL | No | Base URL for the CreateWorker API | https://www.createworker.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| account_getA | Get the API key's organization and credit wallet balance. |
| usage_listB | List recent credit usage ledger entries (paginated). |
| workers_listB | List the org's AI workers. Use a worker's id to create tasks for it. |
| worker_getA | Get one worker by id (role, status, autonomy level). |
| worker_createA | Create a worker. roleKey is a CreateWorker role (e.g. OPERATIONS_ASSISTANT, CUSTOMER_SUPPORT_AGENT, RESEARCH_ANALYST). Autonomy defaults per role. |
| worker_updateC | Update a worker's name and/or status. |
| worker_deleteC | Archive (soft-delete) a worker. |
| tasks_listB | List tasks, optionally filtered by worker or status. |
| task_getA | Get full task detail: status, proposals, approvals, executions, deliverables. |
| task_createA | Create a task for a worker. Runs asynchronously — then poll with task_get or use task_wait. Writes stay approval-gated unless the worker auto-executes. |
| task_cancelB | Cancel a task that has not yet executed. |
| task_waitA | Poll a task until it reaches a terminal or actionable status (PROPOSED, COMPLETED, FAILED, …) or the timeout. Returns the final task detail. |
| task_deliverablesA | List the deliverables a task produced (the worker's output content). |
| approval_decideA | Decide a PROPOSED task's action: APPROVE (execute), REJECT, or EDIT (provide editedAction). |
| clarification_answerB | Answer a worker's clarifying question (CLARIFICATION_PENDING) by selecting an option. |
| deliverable_getA | Get a single deliverable by id, including its full content. |
| knowledge_listB | List the org's knowledge documents (paginated). |
| knowledge_getA | Get a knowledge document by id. |
| knowledge_createA | Create a text knowledge document (chunked/embedded asynchronously). Use this to give workers reference material — e.g. your API docs. |
| knowledge_deleteB | Delete a knowledge document by id. |
| connections_listC | List integration connections (generic API + webhook). |
| connection_create_apiB | Create a generic_api connection so a bound worker can call YOUR app's API (outbound). allowedHosts is the required SSRF allowlist (e.g. ['api.example.com']). |
| connection_create_webhookB | Create a webhook connection: returns an endpointUrl + signingSecret (once) your app POSTs events to, which become tasks for the bound worker. |
| connection_deleteB | Disconnect an integration connection by id. |
| bindings_listC | List worker↔connection bindings, optionally for one worker. |
| binding_createC | Bind a connection to a worker so the worker can use it. purpose: OUTBOUND (worker calls your API), INBOUND (your app triggers the worker), or BOTH. |
| binding_deleteA | Remove a worker↔connection binding by id. |
| webhook_registerB | Subscribe a URL to CreateWorker events (task.completed, proposal.needs_approval, …). Returns a signing secret (once). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.