openclaw-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENCLAW_GATEWAY_URL | No | OpenClaw gateway URL | http://localhost:18789 |
| OPENCLAW_GATEWAY_TOKEN | Yes | Auth token from your OpenClaw config |
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 |
|---|---|
| ask_agentA | Send a message to an OpenClaw agent and get their response. Use agent names like 'daemon', 'soren', 'ash', 'mira', 'jace', 'pip'. |
| list_agentsA | List all available OpenClaw agents from the gateway. |
| agent_statusA | Check the status of a specific OpenClaw agent session. |
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 serves a clearly distinct purpose: listing agents, checking a specific agent's status, and sending a message. There is no overlap between these operations.
Most tools follow a verb_noun pattern (ask_agent, list_agents), but agent_status deviates by using noun_noun. The inconsistency is minor and the names remain clear.
Three tools is a well-scoped set for an agent interaction server, covering the core needs of discovery, status checking, and messaging without unnecessary bloat.
The set covers the primary lifecycle of interacting with agents, but lacks explicit session management (e.g., start/stop). This is a minor gap for a basic agent gateway server.