The openclaw-mcp server bridges AI clients (like Claude.ai) with the OpenClaw AI assistant gateway, enabling both synchronous and asynchronous interactions.
openclaw_chatβ Send a message to OpenClaw and receive an immediate response; supports optional session ID for conversation continuity.openclaw_statusβ Check the health and operational status of the OpenClaw gateway.openclaw_chat_asyncβ Queue a message for asynchronous processing and receive atask_idimmediately; supports priority levels and session IDs.openclaw_task_statusβ Poll the progress of a queued async task and retrieve its result once complete.openclaw_task_listβ List all async tasks with optional filtering by status (pending,running,completed,failed,cancelled) or session ID.openclaw_task_cancelβ Cancel a pending task that hasn't started processing yet.
OpenClaw MCP Server
π¦ Model Context Protocol (MCP) server for OpenClaw AI assistant integration.
Demo
Why I Built This
Hey! I created this MCP server because I didn't want to rely solely on messaging channels to communicate with OpenClaw. What really excites me is the ability to connect OpenClaw to the Claude web UI. Essentially, my chat can delegate tasks to my Claw bot, which then handles everything else β like spinning up Claude Code to fix issues for me.
Think of it as an AI assistant orchestrating another AI assistant. Pretty cool, right?
Quick Start
Docker (Recommended)
Pre-built images are published to GitHub Container Registry on every release.
Create a docker-compose.yml:
Generate secrets and start:
Then in Claude.ai add a custom MCP connector pointing to your server with MCP_CLIENT_ID=openclaw and your MCP_CLIENT_SECRET.
Tip: Pin a specific version instead of
latestfor production:ghcr.io/freema/openclaw-mcp:1.1.0
Local (Claude Desktop)
Add to your Claude Desktop config:
Remote (Claude.ai) without Docker
Important: When running behind a reverse proxy (Caddy, nginx, etc.), you must set
MCP_ISSUER_URL(or--issuer-url) to your public HTTPS URL. Without this, OAuth metadata will advertisehttp://localhost:3000and clients will fail to authenticate.
See Installation Guide for details.
Architecture
Available Tools
Sync Tools
Tool | Description |
| Send messages to OpenClaw and get responses |
| Check OpenClaw gateway health |
Async Tools (for long-running operations)
Tool | Description |
| Queue a message, get task_id immediately |
| Check task progress and get results |
| List all tasks with filtering |
| Cancel a pending task |
Documentation
Installation β Setup for Claude Desktop & Claude.ai
Configuration β Environment variables & options
Deployment β Docker & production setup
Threat Model β What Claude can/can't trigger, trust boundaries & attack surfaces
Logging β What gets logged, where, and what is never logged
Development β Contributing & adding tools
Security β Security policy & best practices
Security
β οΈ Always enable authentication in production!
Configure CORS to restrict access:
See Configuration for all security options.
Requirements
Node.js β₯ 20
OpenClaw gateway running with HTTP API enabled:
// openclaw.json { "gateway": { "http": { "endpoints": { "chatCompletions": { "enabled": true } } } } }
License
MIT
Author
Created by TomΓ‘Ε‘ Grasl
Related Projects
OpenClaw β The AI assistant this MCP connects to
MCP Specification β Model Context Protocol docs