openclaw-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | SSE server bind host | 127.0.0.1 |
| PORT | No | SSE server port | 3000 |
| OPENCLAW_URL | No | OpenClaw gateway URL | http://127.0.0.1:18789 |
| OPENCLAW_MODEL | No | Model to use for chat completions | default |
| RATE_LIMIT_PER_MIN | No | Max tool calls per minute | 60 |
| OPENCLAW_GATEWAY_TOKEN | Yes | Bearer token for gateway auth |
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_chatB | Send a message to OpenClaw and get a response |
| openclaw_statusA | 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 or session. |
| openclaw_task_cancelA | Cancel a pending task. Only works for tasks that haven't started yet. |
| openclaw_messageC | Send a message on Telegram or WhatsApp via the OpenClaw gateway |
| openclaw_memory_readA | Read a memory file from the OpenClaw workspace |
| openclaw_memory_writeC | Write content to a memory file in the OpenClaw workspace |
| openclaw_alertA | Send an urgent alert to Gabriel on Telegram via OpenClaw |
| openclaw_spawn_agentC | Spawn an OpenClaw sub-agent to perform a task |
| openclaw_web_searchB | Search the web via OpenClaw |
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 12 tools
Each tool has a clearly defined purpose: chat (sync/async), status, task management (status/list/cancel), platform messaging, memory operations, alerts, agent spawning, and web search. There is no meaningful overlap between the tools, as even similar actions (e.g., chat vs. message) target distinct contexts (OpenClaw conversation vs. external platform).
All tools share the 'openclaw_' prefix, which provides cohesion, but the pattern after the prefix is inconsistent. Some use verb-first (openclaw_chat, openclaw_web_search), some use noun-only (openclaw_status, openclaw_task_list), and some use noun-verb (openclaw_memory_read, openclaw_task_cancel). This mixed convention is readable but not predictable.
With 12 tools, the server is well-scoped for its purpose of controlling an OpenClaw instance. Each tool covers a distinct capability, and the count is within the ideal range for an assistant-like MCP server.
The toolset provides comprehensive coverage for chatting (sync/async), task management (status/list/cancel), messaging, memory read/write, alerting, agent spawning, and web search. Minor gaps exist, such as no explicit memory delete or session management, but these are not critical for the server's apparent purpose.