openclaw-mcp-termux
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSPORT | No | Transport mode: stdio or http (default stdio). | stdio |
| BRIDGE_TOKEN | No | Auth token for remote Claude.ai connections (HTTP mode). | |
| OPENCLAW_URL | No | Gateway URL (default http://127.0.0.1:18789) | http://127.0.0.1:18789 |
| OPENCLAW_TIMEOUT_MS | No | HTTP timeout in milliseconds (default 660000). | 660000 |
| OPENCLAW_HOOK_SECRET | Yes | Webhook secret for /hooks/agent (async dispatch). | |
| OPENCLAW_GATEWAY_TOKEN | Yes | Gateway bearer token from openclaw.json (gateway.auth.token). Hex format. |
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 |
|---|---|
| agent_dispatchA | Send a task or message to an OpenClaw agent. Three modes:
|
| agent_queryA | Multi-view agent observation. Consolidates health checks, session listings, activity monitoring, and log access into a single tool.
|
| agent_controlA | Control running agent sessions: abort stuck agents, steer them in a new direction, compact their context, or reset them. Uses the gateway /tools/invoke API. If the gateway does not support a given action, returns a clear error with CLI fallback instructions. |
| openclaw_cliA | OpenClaw CLI operations: read/write config, run doctor, check version, restart instructions.
|
| file_readA | Read an entire file or a specific line range. Content comes back through JSON — no shell, no escaping issues. Use start_line / end_line for large files. Output is capped at 2000 lines. |
| file_writeA | Create or overwrite a file with the given content. Content goes through JSON parameters — never a shell — so there are no escaping or newline-stripping issues. Automatically creates parent directories if they do not exist. Use this for new files and full rewrites. For targeted edits to existing files, use file_edit instead. |
| file_editA | Replace a unique string in a file with another string. old_str must match the raw file content exactly and appear exactly once. Use this instead of shell-based sed/python for all file edits — content goes through JSON parameters, never a shell, so there are no escaping issues. |
| file_searchA | Search for a literal string pattern in a file or recursively in a directory. Returns structured hits with surrounding context lines. Case-insensitive. Replaces grep -n. For regex searches, use shell_exec. |
| shell_execA | Execute arbitrary shell commands on the Termux device. Useful for direct filesystem inspection and diagnostics. Only call when the user has explicitly requested execution, or when diagnostics are clearly required for the task at hand. Do not use for speculative exploration or as a default first step. |
| system_healthA | Snapshot of Termux device health: RAM, CPU load, disk space, OpenClaw version, gateway reachability, and active OpenClaw/node processes. Fast and read-only — safe to call any time. |
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 10 tools
Each tool has a clear primary job, and the agent_* and file_* prefixes separate control, observation, and execution well. Minor overlap exists between agent_query's health/log views and system_health's gateway/process snapshot, but the descriptions are specific enough to prevent serious misselection.
Names are consistently snake_case and mostly follow a verb_noun pattern like agent_dispatch, file_read, and shell_exec. openclaw_cli and system_health are noun-style deviations, but the overall pattern remains predictable and readable.
10 tools is well-scoped for an OpenClaw-on-Termux server: four agent-management tools, four file tools, plus shell execution and system health. Each tool has a distinct role with no obvious redundancy.
The surface covers agent dispatch, observation, control, configuration/diagnostics, file CRUD/search, and device health. Minor gaps like no remote gateway restart and no direct configured-agent listing are workable and do not create dead ends.