openclaw-mcp-bridge
Related Servers
Alternatives to openclaw-mcp-bridge
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceExposes OpenClaw tools (web search, page fetching, browser automation, PDF analysis, messaging, inter-agent communication, Canvas) as MCP tools for ACP agents.7-
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to inspect local OpenClaw agents and sessions, and optionally request controlled work from a preconfigured agent.MIT
- AlicenseNot gradedqualityBmaintenanceExposes Agentweaver runs and outcomes as MCP tools for Claude Desktop and compatible clients.7MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with OpenClaw agents via MCP, supporting natural language queries and session management.3-
- AlicenseNot gradedqualityCmaintenanceExposes OpenClaw gateway tools to MCP clients like Claude Code and Codex, enabling local tool calls, file operations, and subagent session management through a stdio MCP server.406 npmMIT
- FlicenseNot gradedqualityDmaintenanceExposes app-registered tools as an MCP server for OpenClaw, forwarding actual tool execution back to the app over a WebSocket bridge.-
TDQS
Scored across 5 tools
Each tool owns a distinct phase of the lifecycle: oc_agents discovers targets, oc_run dispatches, oc_wait polls a known runId, oc_last recovers history without a runId, and oc_cancel aborts. The descriptions explicitly pre-empt the likely confusions (wait vs. last, running vs. history) and state when not to use each tool.
All tools share a consistent oc_ prefix and snake_case, which makes the family instantly recognizable. The only minor deviation is that oc_agents is a plural noun while the rest are verbs (run/wait/last/cancel), but this is readable and predictable.
Five tools is tight and well-scoped for a bridge to a local agent gateway; every tool covers a non-redundant operation with no filler. Nothing suggests a missing sibling or an over-stuffed surface.
The dispatch lifecycle — discover agents, run, poll, recover history, cancel — is fully covered, including recovery paths for lost runIds and stuck sessions. Minor gaps remain: there is no tool to enumerate active runs across agents or to check gateway/health status other than error codes like GATEWAY_UNAVAILABLE.