# OpenClaw MCP - Complete Setup Guide

**Last updated:** March 2026  
**For:** MikesBlogDesign readers

OpenClaw’s new MCP server feature is a massive upgrade. It turns OpenClaw into a universal bridge so tools like Claude Code, Cursor, Codex and other MCP clients can directly use your messaging accounts (Slack, Telegram, Discord, WhatsApp, etc.) with minimal friction.

## Why This Is a Big Deal

- Before: Complex custom bridges, many hops, fragile connections
- After: Clean MCP interface, one hop, stable, easy to host anywhere

OpenClaw now exposes clean MCP tools such as:
- `conversations_list`
- `messages_send`
- `messages_read`
- `events_poll`
- `events_wait`
- `attachments_fetch`

## Installation & Basic Usage

### 1. Start the MCP Server

**Local / Simple:**
```bash
openclaw mcp serve
Remote Gateway (most common):
Bashopenclaw mcp serve \
  --url wss://your-gateway-host:18789 \
  --token-file ~/.openclaw/gateway.token
With password instead of token:
Bashopenclaw mcp serve \
  --url wss://your-gateway-host:18789 \
  --password-file ~/.openclaw/gateway.password
Useful flags:

--verbose or -v → more detailed logs
--claude-channel-mode on → force Claude-style notifications

2. Connect from MCP Client (Claude Code / Cursor example)

Add this to your client’s config:
JSON{
  "mcpServers": {
    "openclaw": {
      "command": "openclaw",
      "args": [
        "mcp",
        "serve",
        "--url",
        "wss://your-gateway-host:18789",
        "--token-file",
        "/absolute/path/to/gateway.token"
      ]
    }
  }
}

3. Available MCP Tools



ToolPurpose

conversations_list    List available conversations
messages_send         Send messages to any channel
messages_read         Read conversation history
events_poll           Poll for new events
events_wait           Wait for live events
attachments_fetch     Download non-text attachments


Pro Tips

Always use --token-file or --password-file — never hardcode secrets
Keep the MCP connection alive (most clients handle this)
Use messages_read for history — live events are session-only
For cloud setups, the upcoming HTTP/SSE transport will make things even easier

Troubleshooting

Make sure your OpenClaw Gateway is running and reachable
Check that sessions include proper channel/recipient metadata
Use --verbose to see detailed error messages
Confirm the WebSocket URL and token/password are correct


Questions?
Comment on the page at mikesblogdesign.com/openclawmcp or reach out on X.
Built for MikesBlogDesign • Clean & simple by design