A
licenseB
qualityD
maintenanceAn MCP server that integrates with the OpenClaw API to enable AI assistants to send messages across multiple platforms, execute system commands, and manage calendar events and emails.
5
1
MIT
openclaw-mcp
Related Servers
Alternatives to openclaw-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Claude Code to interact with OpenClaw AI agents (Daemon, Soren, Ash, etc.) via the gateway API, providing tools to ask agents, list them, and check their status.3195 npmMIT
- AlicenseNot gradedqualityCmaintenanceA universal MCP server for spawning agents with any OpenAI-compatible LLM, supporting cloud and local models, and integrating with Claude Code, OpenCode, and Codex CLI.MIT
- AlicenseAqualityBmaintenanceMCP server to dynamically load Claude Code skills into AI agents531 npm15MIT
- AlicenseAqualityDmaintenanceMCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.4779 npm2Apache 2.0
- AlicenseBqualityDmaintenanceA personal MCP server for AI assistant integration that provides custom tools, resources, and prompts for use with Claude Desktop and other MCP-compatible clients.2MIT
TDQS
A3.5/5.0
Scored across 12 tools
Disambiguation5/5
Each tool has a clearly defined purpose: chat (sync/async), status, task management (status/list/cancel), platform messaging, memory operations, alerts, agent spawning, and web search. There is no meaningful overlap between the tools, as even similar actions (e.g., chat vs. message) target distinct contexts (OpenClaw conversation vs. external platform).
Naming Consistency3/5
All tools share the 'openclaw_' prefix, which provides cohesion, but the pattern after the prefix is inconsistent. Some use verb-first (openclaw_chat, openclaw_web_search), some use noun-only (openclaw_status, openclaw_task_list), and some use noun-verb (openclaw_memory_read, openclaw_task_cancel). This mixed convention is readable but not predictable.
Tool Count5/5
With 12 tools, the server is well-scoped for its purpose of controlling an OpenClaw instance. Each tool covers a distinct capability, and the count is within the ideal range for an assistant-like MCP server.
Completeness4/5
The toolset provides comprehensive coverage for chatting (sync/async), task management (status/list/cancel), messaging, memory read/write, alerting, agent spawning, and web search. Minor gaps exist, such as no explicit memory delete or session management, but these are not critical for the server's apparent purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues