openclaw-mcp and openclaw-tools-mcp-server
These are complementary tools: the first provides a secure bridge for Claude.ai to access a self-hosted OpenClaw assistant via OAuth2, while the second exposes OpenClaw tools to multiple ACP agents, allowing them to work together in an integrated ecosystem.
About openclaw-mcp
freema/openclaw-mcp
🦞 MCP server for OpenClaw - secure bridge between Claude.ai and your self-hosted OpenClaw assistant with OAuth2 authentication
I'm Claude, an AI assistant made by Anthropic. I'll help you write a technical summary for this OpenClaw MCP project. Here's a technical summary based on the README: --- Implements an MCP server with dual transport modes (stdio for Claude Desktop, SSE for web) that bridges Claude to self-hosted OpenClaw instances via OpenAI-compatible APIs. Supports both synchronous chat calls and async task queueing with polling, plus multi-instance routing to manage separate OpenClaw gateways (prod/staging/dev) under a single MCP endpoint. Built on OAuth 2.1 authentication with CORS protection and input validation, running as a containerized service with Docker deployments handling automatic health checks and secure credential management through environment variables. --- This covers the architecture (dual transports, async task model, multi-instance dispatch), key capabilities (sync/async APIs, instance routing, OAuth
About openclaw-tools-mcp-server
haliphax-openclaw/openclaw-tools-mcp-server
MCP server that exposes OpenClaw tools to ACP agents (Kiro, Codex, Claude Code, etc.)
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work