openclaw-control-mcp
Related Servers
Alternatives to openclaw-control-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to manage GoClaw AI gateway infrastructure through a comprehensive suite of 66 tools for managing agents, sessions, and configurations. It provides real-time gateway context and guided workflows with enterprise-grade security features like audit logging and secret scrubbing.6611MIT
- AlicenseNot gradedqualityBmaintenanceEnables administration of LibreChat through MCP, providing tools to manage Skills, Agents, scheduled tasks, Prompt library, and visibility/permissions. It also offers a generic API request tool for interacting with upstream endpoints.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to access model registry, prediction logging, drift detection, bias/fairness auditing, compliance and governance queries, explanation generation, LLM/RAG monitoring, content safety, alert management, multi-agent workflow tracking, and performance metrics through 197 tools across 18 domains. Supports stdio and hosted Streamable HTTP transports, plus MCP Apps interactive audit cards.35 PyPIMIT
- AlicenseBqualityFmaintenanceExposes OpenClaw tools (web search, page fetching, browser automation, PDF analysis, messaging, inter-agent communication, Canvas) as MCP tools for ACP agents.7-
- 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
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude.ai and Claude Desktop to securely connect to self-hosted OpenClaw gateways, chat with assistants, check gateway health, list configured instances, and manage long-running tasks across multiple instances.406 npmMIT
TDQS
Scored across 143 tools
Many tools have overlapping purposes within the same domain: four variants of sending messages (openclaw_send, openclaw_agent, openclaw_chat_send, openclaw_sessions_send), two abort tools (openclaw_chat_abort, openclaw_sessions_abort), and multiple approval-policy tools (openclaw_exec_approval_* vs openclaw_exec_approvals_*) that are easy to confuse. The descriptions are detailed, but the sheer number of near-miss CRUD operations makes misselection likely.
Naming is a mix of domain_action (openclaw_cron_list), domain_subdomain_action (openclaw_node_pair_list), camelCase method names (openclaw_tts_setProvider), and plural/singular inconsistencies (openclaw_exec_approval_list vs openclaw_exec_approvals_get). While the openclaw_ prefix provides a uniform namespace, the structure after it is inconsistent enough to hurt predictability.
143 tools is an extreme count for a single MCP server, far beyond even a heavy 25+ threshold. While the gateway has a large surface area, exposing every JSON-RPC method plus convenience wrappers and escape hatches results in a sprawling toolset that is overwhelming for an agent to navigate.
The toolset is remarkably comprehensive across gateway domains: sessions, agents, config, cron, skills, nodes, approvals, TTS, and more. Missing operations like skill uninstall, a pending-node list, or a session message history (only tail/preview) are minor gaps; the coverage is strong enough that most workflows have no dead ends.