Claude Code MCP Server
Related Servers
Alternatives to Claude Code MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to interact programmatically with Claude Code CLI, managing sessions, streaming outputs, and handling permission requests.77 npm1MIT
- AlicenseAqualityDmaintenanceWraps Anthropic Claude Code CLI as tools, allowing MCP clients to invoke headless Claude Code sessions.2379 npmMIT
- AlicenseNot gradedqualityBmaintenanceDelegates coding tasks to the local Claude Code CLI via MCP, offering run, review, and status tools for MCP-compatible agents.11 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables voice assistants to start, monitor, message, and approve local Claude Code sessions on your computer, including sessions already open in a terminal. It exposes session management, recaps, approvals, and history search as MCP tools.2GPL 3.0
- AlicenseAqualityDmaintenanceWraps Claude Code as tools for MCP clients, enabling autonomous coding tasks via a 4-tool lifecycle with session management, async polling, and permission controls.434 npm20MIT
- AlicenseNot gradedqualityAmaintenanceLets Codex delegate coding and repository work to an installed Claude Code CLI with permission-aware inspect/write access, model and effort selection, resumable and cloud-attached sessions, and durable synchronous or asynchronous jobs.MIT
TDQS
Scored across 3 tools
Each tool targets a distinct action: creating a cloud session, sending a follow-up message, and checking CLI auth. There is no plausible overlap or way an agent could confuse them.
All three tools use the same claude_ prefix followed by a clear snake_case verb_noun form (create_cloud_session, send_followup, auth_status). The pattern is entirely predictable.
Three tools is a lean but coherent set for driving Claude Code cloud sessions. It is slightly under-scoped, but no tool feels redundant or bloated.
The surface covers session creation, follow-ups, and auth, but has notable gaps: no way to list existing sessions, read a session's output/status, or terminate a session. Agents can partially work around this via the returned session_url, but the lifecycle is incomplete.