openclaw-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_ENABLED | No | Whether to enable authentication (required for production or remote use). | |
| CORS_ORIGINS | No | Comma-separated list of allowed CORS origins, e.g., https://claude.ai. | |
| OPENCLAW_URL | Yes | The URL of the OpenClaw gateway server. | http://127.0.0.1:18789 |
| MCP_CLIENT_ID | No | The client ID used for MCP authentication. | |
| MCP_ISSUER_URL | No | The public HTTPS URL of the MCP server, required for OAuth metadata when running behind a reverse proxy. | |
| MCP_CLIENT_SECRET | No | The client secret used for MCP authentication. | |
| OPENCLAW_GATEWAY_TOKEN | Yes | The gateway token used for authentication with OpenClaw. |
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 |
|---|---|
| openclaw_chatC | Send a message to OpenClaw and get a response |
| openclaw_statusB | Get OpenClaw gateway status and health information |
| openclaw_chat_asyncA | Send a message to OpenClaw asynchronously. Returns a task_id immediately that can be polled for results. Use this for potentially long-running conversations. |
| openclaw_task_statusB | Check the status of an async task. Returns status, and result if completed. |
| openclaw_task_listA | List all tasks. Optionally filter by status, session, or instance. |
| openclaw_task_cancelA | Cancel a pending task. Only works for tasks that haven't started yet. |
| openclaw_instancesA | List all configured OpenClaw instances. Shows instance names, URLs, and which is the default. Use instance names in other tools to target a specific OpenClaw gateway. |
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 7 tools
Most tools have distinct purposes, but openclaw_chat and openclaw_chat_async could be confused if an agent skims descriptions. The async variant is clearly labeled, so overall disambiguation is good but not perfect.
All tools use the consistent pattern 'openclaw_verb_noun' with snake_case. This makes it easy to predict tool names and understand their function.
Seven tools is ideal for an API gateway wrapper. Each tool covers a distinct operation without redundancy, and the scope is well-scoped for interacting with OpenClaw instances.
The set covers core operations: chat (sync/async), instance management, health status, and task management. Minor gap: no tool for listing sessions or conversation history, but the core workflows are complete.