Best for
- Users who want to integrate self-hosted OpenClaw with Claude.
- Users managing multiple OpenClaw instances from a unified interface.
O
OpenClaw MCP Server
Community
MCP server securely bridging Claude with a self-hosted OpenClaw assistant.
GitHub source repository ↗
63FMRS · C
The server provides seamless integration with OpenClaw, supporting both sync and async tasks and multi-instance. Security is emphasized with OAuth and CORS controls. Deployment requires careful configuration.
The OpenClaw MCP server is a secure bridge connecting Claude.ai or Claude Desktop to a self-hosted OpenClaw assistant via OAuth 2.1 authentication. It allows Claude to delegate tasks to OpenClaw instances, supporting both synchronous and asynchronous operations. The server supports multi-instance mode for orchestrating multiple OpenClaw gateways from a single MCP server.
Tools
openclaw_chat
Send messages to OpenClaw and get responses.
openclaw_status
Check OpenClaw gateway health.
openclaw_instances
List all configured OpenClaw instances.
openclaw_chat_async
Queue a message and get a task ID immediately.
openclaw_task_status
Check task progress and get results.
openclaw_task_list
List your tasks with filtering.
openclaw_task_cancel
Cancel a pending task.
Setup
For Claude Desktop (local): run npx openclaw-mcp, then add the binary configuration to claude_desktop_config.json with environment variables. For Claude.ai (remote): use Docker or CLI with HTTP transport, enable authentication, and configure OAuth redirect URIs.
claude_desktop_config.json
{
"mcpServers": {
"openclaw": {
"command": "npx",
"args": [
"openclaw-mcp"
],
"env": {
"OPENCLAW_URL": "http://127.0.0.1:18789",
"OPENCLAW_GATEWAY_TOKEN": "your-gateway-token",
"OPENCLAW_MODEL": "openclaw",
"OPENCLAW_TIMEOUT_MS": "300000"
}
}
}
}
Fit and risk
Not for
- Users without an OpenClaw instance.
- Users requiring unauthenticated production deployments.
Required permissions
- Access to the OpenClaw gateway HTTP API.
- Requires a gateway token (Bearer) for authentication.
Risks and side effects
- Security risks in production if not properly secured (authentication must be enabled).
- OAuth callback exposure if misconfigured; precise redirect URIs are recommended.
- Exposing gateway URL and secrets could lead to security issues.
Troubleshooting
- Ensure the connector URL ends with `/mcp`, otherwise a 404 may occur after OAuth.
- Ensure `MCP_ISSUER_URL` is set to your public HTTPS URL and `TRUST_PROXY` is enabled to avoid authentication issues.
- If you see 'Unregistered redirect_uri', check that `MCP_REDIRECT_URIS` exactly matches Claude's callback path.
Use cases
Delegating tasks from Claude to OpenClaw assistants.
Orchestrating multiple OpenClaw instances (e.g., prod, staging, dev) from a single MCP server.
Running long-running operations asynchronously without blocking responses.
Supported clients
Claude DesktopFull support
Claude.aiFull support