openclaw-task-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENCLAW_BASE_URL | Yes | The base URL of the OpenClaw Gateway | |
| OPENCLAW_API_TOKEN | Yes | Gateway token with permission to invoke tools | |
| OPENCLAW_TIMEOUT_MS | No | Timeout in milliseconds for requests | 30000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_taskC | Start a subagent task via OpenClaw sessions_spawn |
| list_tasksC | List tasks via sessions_list, filtered to subagent by default |
| get_task_statusA | Get task status from sessions_history and include result when available |
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 3 tools
Each tool targets a distinct action: creating a task, listing tasks, and checking status. There is no overlap or ambiguity between purposes.
All tool names follow a consistent verb_noun pattern: start_task, list_tasks, get_task_status. The naming is uniform and predictable.
Three tools is a well-scoped set for task lifecycle management. Each tool earns its place and there is no redundancy or bloat.
The core task lifecycle is covered: starting, listing, and retrieving status. A minor gap is the lack of an explicit cancel/abort operation, but the primary workflow works without dead ends.