home / mcp / openclaw mcp server

OpenClaw MCP Server

Provides MCP-based bridge between OpenClaw and Claude to orchestrate AI workflows across systems.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "freema-openclaw-mcp": {
      "url": "https://mcp.your-domain.com",
      "headers": {
        "AUTH_ENABLED": "true",
        "OPENCLAW_URL": "http://127.0.0.1:18789",
        "MCP_CLIENT_ID": "openclaw",
        "MCP_CLIENT_SECRET": "YOUR_SECRET",
        "OPENCLAW_GATEWAY_TOKEN": "your-gateway-token"
      }
    }
  }
}

You can connect OpenClaw to Claude via a Model Context Protocol (MCP) server that acts as a bridge between your local or remote AI setup and Claude. This MCP server lets you orchestrate tasks across OpenClaw and Claude, enabling advanced interactions without relying solely on messaging channels.

How to use

Set up your MCP server so Claude can talk to OpenClaw. You can run the server locally for development or deploy it behind a reverse proxy for production. You will connect Claude Desktop or Claude.ai to your MCP server using the provided client credentials and the MCP endpoint.

How to install

Prerequisites you need before starting:

Install and run locally

npx openclaw-mcp

Install and run remotely (production style)

To run the MCP server with authentication and remote access, enable authentication, set your OAuth client details, and expose the server via a public URL. Use these environment variables along with the MCP runner.

AUTH_ENABLED=true MCP_CLIENT_ID=openclaw MCP_CLIENT_SECRET=your-secret \
  MCP_ISSUER_URL=https://mcp.your-domain.com \
  CORS_ORIGINS=https://claude.ai OPENCLAW_GATEWAY_TOKEN=your-gateway-token \
  npx openclaw-mcp --transport sse --port 3000

Configure Claude to connect

In Claude Desktop, add a connector pointing to your local MCP or remote MCP URL. For local development, you typically run the MCP locally and register it under the Claude Desktop configuration. For remote usage, provide the MCP client credentials you configured above.

Important security note

When running behind a reverse proxy, ensure MCP issuer URL is your public HTTPS URL so OAuth metadata does not advertise localhost. This prevents authentication failures for clients.

Available tools

openclaw_chat

Send messages to OpenClaw and obtain responses via MCP integration.

openclaw_status

Check the health status of the OpenClaw gateway.

openclaw_chat_async

Queue a chat message and receive a task_id immediately for long-running operations.

openclaw_task_status

Poll for progress and results of asynchronous tasks.

openclaw_task_list

List and filter all tasks by status or other criteria.

openclaw_task_cancel

Cancel a pending long-running task if needed.