Openclaw MCP logo

Openclaw MCP

by freema

Routes Claude requests to OpenClaw gateways with synchronous chat, asynchronous tasks, health checks, and multi-instance targeting.

Install Openclaw MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "freema-openclaw-mcp": {
      "command": "npx",
      "args": [
        "openclaw-mcp"
      ],
      "env": {
        "OPENCLAW_URL": "YOUR_VALUE_HERE",
        "OPENCLAW_GATEWAY_TOKEN": "YOUR_VALUE_HERE",
        "OPENCLAW_AGENT_ID": "YOUR_VALUE_HERE",
        "OPENCLAW_MODEL": "YOUR_VALUE_HERE",
        "OPENCLAW_TIMEOUT_MS": "YOUR_VALUE_HERE",
        "MCP_CLIENT_ID": "YOUR_VALUE_HERE",
        "MCP_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "MCP_ISSUER_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

freema/openclaw-mcp connects Claude clients to one or more OpenClaw gateways through MCP. It provides synchronous chat, asynchronous task management, gateway status checks, and instance discovery. Local use runs through stdio with Claude Desktop, while remote deployments expose a Streamable HTTP endpoint with OAuth 2.1 protection. Reach for it when an MCP client needs to delegate conversations or longer-running work to OpenClaw.

Use cases

  • Delegate conversations from Claude to an OpenClaw assistant
  • Queue long-running OpenClaw requests and poll their results
  • Route requests across development, staging, and production gateways
  • Check OpenClaw gateway health from an MCP client

Key features

  • Synchronous OpenClaw chat
  • Asynchronous task queue and polling
  • Task listing and cancellation
  • Gateway health checks
  • Multi-instance gateway routing
  • OAuth 2.1 and Streamable HTTP support

Tools7

What Openclaw MCP lets your agent do. Expand a tool for its parameters.

Verified live~580 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

21/21 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · openclaw-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars188Stargazers on the source repository.
npm downloads588Package downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed7Callable tools this server registers over MCP.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How Openclaw MCP works

What freema/openclaw-mcp does

freema/openclaw-mcp bridges MCP clients and OpenClaw AI assistant gateways. It lets a connected client send messages to OpenClaw, retrieve responses, inspect gateway health, and select among configured OpenClaw instances.

The bridge supports both immediate and deferred conversations. Synchronous chat waits for a response, while asynchronous chat returns a task identifier so longer operations can be checked separately. Task tools cover status lookup, listing, and cancellation of queued work.

A single bridge can be configured with multiple OpenClaw gateways, such as separate development, staging, and production instances. Each instance can have its own URL, authentication, and timeout settings, and tools can target an instance by name.

How it works

For local use, the package runs as an MCP process over stdio. Claude Desktop starts it with npx openclaw-mcp, and the bridge communicates with an OpenClaw gateway at the configured URL.

For remote use, start the server with the HTTP transport and expose its /mcp endpoint through HTTPS. The remote setup uses OAuth 2.1, CORS controls, and configurable redirect URIs for Claude.ai. When a reverse proxy is involved, the public issuer URL and proxy trust setting must match the deployment so OAuth metadata and forwarded request handling work correctly.

Asynchronous tasks belong to the MCP connection that created them. In HTTP mode, clients can only inspect or cancel tasks from that same connection; reconnecting creates a new task scope.

Setup and configuration

The Docker image is available from GitHub Container Registry, and the package can also be launched with npx. A basic local configuration supplies the OpenClaw URL and gateway token, with optional agent, model, and timeout settings.

For an HTTP deployment, configure an MCP client ID and secret. Set MCP_ISSUER_URL to the public HTTPS address when using a reverse proxy, and set TRUST_PROXY=1 in that arrangement. Claude.ai connector URLs must end in /mcp; using the bare domain targets the server root instead of the MCP endpoint.

The deployment examples use port 3000 for the bridge and port 18789 for an OpenClaw gateway. Claude.ai setups can restrict authorization callbacks with MCP_REDIRECT_URIS, including the exact callback paths used by Claude.

Tools and capabilities

  • openclaw_chat sends a message and waits for the OpenClaw response.
  • openclaw_chat_async queues a message and immediately returns a task_id.
  • openclaw_task_status retrieves the state and completed result of an asynchronous task.
  • openclaw_task_list lists tasks, with optional status, session, or instance filtering.
  • openclaw_task_cancel cancels a task that has not started.
  • openclaw_status checks gateway health information.
  • openclaw_instances lists configured gateways, their URLs, and the default instance.

Limitations and notes

Cancellation only applies to pending tasks. Task identifiers are scoped to their creating MCP connection, so a task may appear unavailable after reconnecting or when queried by another HTTP client. Remote deployments also need correct HTTPS, OAuth issuer, redirect URI, and proxy settings for Claude.ai authentication.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Openclaw MCP

freema/openclaw-mcp is an MCP server that connects Claude clients to OpenClaw AI assistant gateways. Its main tools send synchronous or asynchronous chat requests, check gateway health, manage queued tasks, and list configured OpenClaw instances for targeted routing.

Install it with `npx openclaw-mcp` for a local Claude Desktop setup, or run the published Docker image from GitHub Container Registry. Configure the OpenClaw URL and gateway token, then add the process or HTTP endpoint to your MCP client.

Yes, freema/openclaw-mcp works with Claude Desktop over stdio. Add `npx openclaw-mcp` as the server command and provide `OPENCLAW_URL`, `OPENCLAW_GATEWAY_TOKEN`, and any optional agent, model, or timeout settings in the client configuration.

Connect Claude.ai to the server's HTTPS `/mcp` endpoint using OAuth 2.1. Configure an MCP client ID and secret, set the public issuer URL behind a reverse proxy, and register Claude's exact authorization callback paths through `MCP_REDIRECT_URIS`.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpenclaw MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/freema-openclaw-mcp?style=directory)](https://allmcps.com/mcp/freema-openclaw-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/freema-openclaw-mcp"><img src="https://allmcps.com/api/badge/freema-openclaw-mcp?style=directory" alt="Openclaw MCP on AllMCPs" /></a>