openclaw

MCP server exposing OpenClaw Gateway tools to Claude Code and other MCP-compatible clients

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio helms-ai-openclaw-mcp-server node /absolute/path/to/openclaw-mcp-server/dist/index.js \
  --env OPENCLAW_GATEWAY_URL="http://127.0.0.1:18789" \
  --env OPENCLAW_GATEWAY_TOKEN="your-token-here"

How to use

The OpenClaw MCP Server exposes the OpenClaw Gateway tooling to Claude Code and other MCP-compatible clients. It provides access to Messaging across multiple platforms (Telegram, WhatsApp, Discord, Slack, Signal, iMessage, Google Chat), Sessions for listing and interacting with OpenClaw sessions, Scheduling for cron-like automated tasks, Nodes to control paired devices, Web search capabilities, Memory file queries, Text-to-Speech (TTS), and a gateway for status and configuration. This server acts as a bridge between a local OpenClaw Gateway instance and MCP clients, translating natural language or structured inputs into gateway actions. To use it, run the MCP server alongside your OpenClaw Gateway, then configure your MCP client with the server as a named MCP server (openclaw) and provide the necessary environment tokens if your gateway requires authentication.

How to install

Prerequisites:

Node.js 18+ installed on the host
OpenClaw Gateway running locally (default: http://127.0.0.1:18789)
Gateway auth token if configured

Installation steps:

Clone the OpenClaw MCP Server repository or install via npm if published:
- git clone https://github.com/your-org/openclaw-mcp-server.git
- cd openclaw-mcp-server
Install dependencies and build:
```
npm install
npm run build
```
Run or install the server globally:
- Local run: node dist/index.js
- Global install (recommended for easy access):
```
npm install -g .
```
Ensure the OpenClaw Gateway is reachable from the server and that you have the gateway URL and token ready. Update environment variables if needed.
Add the MCP server configuration to your clients (Claude Desktop, Claude Code, Zed, VSCode Cline, Windsurf, etc.) using the absolute path to dist/index.js and the appropriate token.

Note: The exact command to start may vary if you deploy via a PM2/daemon manager or a container; adjust accordingly.

Additional notes

Tips and notes:

Always use absolute paths in MCP client configurations to avoid path resolution issues.
If your gateway requires authentication, set OPENCLAW_GATEWAY_TOKEN in the MCP server environment.
If the gateway URL is not the default, set OPENCLAW_GATEWAY_URL to the correct address.
After changing MCP server configurations in clients (Claude, Zed, Windsurf, etc.), reload or restart the client to pick up changes.
For security, avoid exposing the gateway token in shared configuration files; use environment variables where possible.
The server supports a wide range of OpenClaw features; refer to the README for detailed tool usage examples (messaging, sessions, scheduling, nodes, web, memory, TTS).

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.