Claude Code MCP
Related Servers
Alternatives to Claude Code MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol server for Claude Code that provides programmatic management of Claude Code CLI operations through a multi-agent collaborative system.2-
- FlicenseNot gradedqualityDmaintenanceA customizable Model Context Protocol server built with mcp-framework that enables Claude to access external tools and capabilities through a standardized interface.55 npm-
- AlicenseAqualityCmaintenanceLocal MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.3MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that allows Claude AI to interact with custom tools, enabling extension of Claude's capabilities through the MCP framework.-
- FlicenseDqualityDmaintenanceA server built on mcp-framework that enables integration with Claude Desktop through the Model Context Protocol.11-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude to manage software development projects with complete context awareness and code execution through Docker environments.14 npm4-
TDQS
Scored across 8 tools
Most tools have distinct purposes, such as bash for shell execution, codeReview for analysis, and file operations like editFile, readFile, and listFiles. However, grep and searchGlob could be slightly confusing as both involve searching, though grep targets text content while searchGlob focuses on file patterns, which is clarified in descriptions.
The naming is mixed with camelCase (codeReview, editFile, readFile, listFiles, searchGlob) and lowercase (bash, grep, think), lacking a uniform pattern. While the camelCase tools follow a verbNoun style, the inconsistency in case usage reduces predictability across the set.
With 8 tools, the count is well-scoped for a code and file management server, covering essential operations like execution, review, file handling, and search. Each tool serves a clear purpose without feeling excessive or insufficient for the domain.
The toolset provides strong coverage for code and file workflows, including creation, reading, editing, listing, searching, and review. A minor gap is the lack of a deleteFile tool, which agents might need to work around, but core operations are well-represented.