OpenClaw MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENCLAW_GATEWAY_URL | No | Gateway HTTP URL | http://127.0.0.1:18789 |
| OPENCLAW_GATEWAY_TOKEN | No | Auth token (if required) |
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_message_sendB | Send a message via OpenClaw channels (Telegram, WhatsApp, Discord, Slack, Signal, etc.) |
| openclaw_message_broadcastB | Broadcast a message to multiple targets |
| openclaw_sessions_listB | List active OpenClaw sessions with optional filters |
| openclaw_sessions_historyB | Fetch message history for a session |
| openclaw_sessions_sendC | Send a message to another OpenClaw session |
| openclaw_sessions_spawnB | Spawn a background sub-agent in an isolated session |
| openclaw_cron_listB | List scheduled cron jobs |
| openclaw_cron_addC | Add a new cron job |
| openclaw_cron_removeC | Remove a cron job |
| openclaw_cron_runB | Trigger a cron job immediately |
| openclaw_nodes_statusA | Get status of paired nodes (mobile devices, remote machines) |
| openclaw_nodes_notifyC | Send a notification to a paired node |
| openclaw_nodes_camera_snapB | Capture a photo from a node's camera |
| openclaw_nodes_locationC | Get location from a paired node |
| openclaw_nodes_runC | Run a command on a paired node |
| openclaw_web_searchB | Search the web using Brave Search API |
| openclaw_web_fetchB | Fetch and extract readable content from a URL |
| openclaw_gateway_statusC | Get OpenClaw Gateway session status |
| openclaw_gateway_config_getA | Get current Gateway configuration |
| openclaw_ttsC | Convert text to speech |
| openclaw_memory_searchC | Search OpenClaw memory files semantically |
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 21 tools
Each tool has a distinct purpose, with clear separation between messaging, sessions, nodes, and other domains. Minor overlap between message_send and message_broadcast is resolved by description.
All tools follow a consistent openclaw_{category}_{action} pattern in snake_case, making names predictable and easy to parse.
21 tools cover multiple domains but are slightly above the ideal 3-15 range. However, the count is justified by the breadth of functionality and does not feel excessive.
While core workflows like cron, messaging, and web are well-covered, there are notable gaps: no memory write, no gateway configuration update, and no node pairing/unpairing. These gaps could hinder some agent tasks.