Which integrations are available for this server?

Provides tools for accessing channel-routed OpenClaw conversations, reading message transcripts, and sending replies through Discord as a conversation channel. Provides tools for accessing channel-routed OpenClaw conversations, reading message transcripts, and sending replies through Slack as a conversation channel. Provides tools for accessing channel-routed OpenClaw conversations, reading message transcripts, and sending replies through Telegram as a conversation channel.

How do I use claw-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@claw-mcp search the workspace for deployment notes" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

claw-mcp

A remote Model Context Protocol server that wraps OpenClaw's stdio MCP bridge (openclaw mcp serve) and serves the OpenClaw agent workspace read-only, over stateless Streamable HTTP. It is meant to sit behind an identity-aware proxy such as Pomerium, which handles MCP OAuth and per-tool policy.

Started from mcp-typescript-template; its history is kept here as the starting point.

Tools

Tool	Source	What it does
`workspace_list`	wrapper	List files in the agent workspace (skips `.git`, `node_modules`)
`workspace_read`	wrapper	Read a text file, optionally a line range (max 1 MB, no binaries)
`workspace_search`	wrapper	Line search across workspace files (substring or regex)
`conversations_list`, `conversation_get`	bridge	Channel-routed OpenClaw conversations (Discord, Slack, Telegram...)
`messages_read`, `attachments_fetch`	bridge	Transcript and attachments for a session key
`events_poll`, `events_wait`	bridge	Live event queue since the bridge connected
`messages_send`	bridge	Reply through a conversation's existing channel route
`permissions_list_open`, `permissions_respond`	bridge	Pending exec/plugin approvals

Bridge conversation tools only cover sessions with a channel route (a channel plus a recipient). Web UI chats such as agent:main:main are not listed, but messages_read works on them by session key.

Related MCP server: AIPI Bridge MCP

How it works

One shared bridge. The HTTP side is stateless (MCP 2026-07-28: a fresh server per request), but the bridge's event queue only exists while it stays connected. So one openclaw mcp serve child is shared by all requests and respawned lazily if it exits (src/openclaw.ts).
Loopback + password. A Gateway in trusted-proxy auth mode accepts only proxy-forwarded identity, plus gateway.auth.password from loopback callers. So the server runs in the Gateway's network namespace (a compose network_mode: service:<gateway> sidecar) and the bridge dials ws://127.0.0.1:18789 with the password file.
Workspace tools run in the wrapper itself (src/workspace.ts), reading a read-only mount of ~/.openclaw/workspace. Paths are realpath-checked to stay inside the root.

Future direction: one bridge per proxy-authenticated user rather than one shared bridge, so OpenClaw's own per-user scopes apply.

Running

Build Dockerfile.openclaw with OPENCLAW_VERSION matching the Gateway and APP_UID matching the Gateway's user (workspace files are mode 600):

clawmcp:
  build:
    context: ../claw-mcp
    dockerfile: Dockerfile.openclaw
    args: [OPENCLAW_VERSION=2026.9.8, APP_UID=1001]
  environment:
    OPENCLAW_GATEWAY_PASSWORD_FILE: /run/clawmcp/gateway-password
    OPENCLAW_WORKSPACE_DIR: /workspace
  volumes:
    - ./gateway-password:/run/clawmcp/gateway-password:ro
    - ./state:/home/clawmcp/.openclaw
    - ./openclaw-home/.openclaw/workspace:/workspace:ro
  network_mode: service:openclaw-gateway

The MCP endpoint is http://<gateway-host>:3000/mcp; GET /health is a liveness check.

Configuration

Variable	Default	Description
`PORT`	`3000`	HTTP port
`SERVER_NAME` / `SERVER_VERSION`	from `package.json`	MCP server identity
`LOG_LEVEL`	`info`	`error` / `warn` / `info` / `debug`
`OPENCLAW_BIN`	`openclaw`	CLI used to spawn `openclaw mcp serve`
`OPENCLAW_GATEWAY_URL`	`ws://127.0.0.1:18789`	Gateway WebSocket (loopback for the password fallback)
`OPENCLAW_GATEWAY_PASSWORD_FILE`	—	File holding `gateway.auth.password`
`OPENCLAW_WORKSPACE_DIR`	—	Workspace to serve read-only; empty disables `workspace_*`
`OPENCLAW_EXCLUDED_TOOLS`	—	Comma-separated bridge tools to hide and refuse; prefer proxy tool policy
`OPENCLAW_CALL_TIMEOUT_MS`	`310000`	Per-call bridge timeout (`events_wait` can take 300s)

Development

npm install
npm run dev        # watch mode (needs the openclaw CLI on PATH)
npm run lint && npm run format:check && npm run build && npm run test:ci

See AGENTS.md for project structure and conventions.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

OmegaAIOAuth
com.queryomega
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
Workplace & Productivity App Automation
2
CommsOAuth
io.github.Osis-AI-LLC
Workspace messaging: conversations, contacts, agents, and connected lines through scoped OAuth.
Communication Workplace & Productivity
1
AgentPub B
io.github.FrankShen18
Agent-to-agent messaging: directory, public lobby, DMs, channels, search. Stateless MCP + REST.
Communication App Automation Autonomous Agents
191
Agent Commons B
pw.algo.ai
Public and private rooms for agents, with messages, files, search, and resumable events.
Communication Agent Orchestration Knowledge & Memory
971

Related MCP Servers

a2a-mcp-bridge
Agent Orchestration Autonomous Agents
ytugarev
A
license
A
quality
C
maintenance
Bridges MCP clients (like Claude Desktop) to A2A agents, enabling message sending and agent card retrieval via a stateless, non-persistent server.
Updated 2 months ago (2026-08-08 11:42 UTC)
3
MIT
AIPI Bridge MCP
Project Management Documentation Access Search
the-great-abby
F
license
Not graded
quality
C
maintenance
Exposes a curated set of Bot Army tools (chat, GTD tasks, docs search, dice roll) to external SSE-only MCP clients via authenticated SSE transport.
Updated a month ago (2026-08-26 23:12 UTC)
-
project-tasks-mcp
Project Management Developer Tools Autonomous Agents
augustoOliveira1993
F
license
Not graded
quality
B
maintenance
Enables managing projects, features, tasks, dependencies, executions, and human review through a Streamable HTTP endpoint, along with persistent inter-agent cooperation via task messaging and event subscriptions. It also supports administrative actions such as approvals, cancellations, unblocking, and member management.
Updated 2 days ago (2026-10-05 20:01 UTC)
-
MCPs
Search Web Scraping AI & Machine Learning
mrzys
A
license
Not graded
quality
C
maintenance
Exposes remote, agent-facing MCP endpoints over Streamable HTTP for web search, webpage parsing, local knowledge-base retrieval and document creation, and delegation of tasks to configurable LLM providers. Also bundles an admin console with onboarding, provider/model configuration, API-key management, and call logging.
Updated a month ago (2026-09-11 12:52 UTC)
MIT