Claude Free Code MCP
Related Servers
Alternatives to Claude Free Code MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude Desktop and Claude Code to list, search, and read files, run one terminal command, query SQLite, and manage named scheduled tasks without calling the Claude API.121MIT
- AlicenseAqualityBmaintenanceProvides Claude Desktop with direct access to your local file system for development tasks, enabling file operations (read, write, edit), directory browsing, command execution, and codebase search within a configured projects directory.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Desktop to analyze repositories, fetch and create issues, inspect pull request diffs, and comment on pull requests through the GitHub API using natural-language commands.1MIT
- AlicenseAqualityDmaintenanceAllows Claude to execute terminal commands on your computer and perform file system operations including surgical code editing with diff-based replacements.197MIT
- AlicenseCqualityBmaintenanceEnables Claude Desktop to control a local host machine through shell, file, git, network, Docker, package, and system monitoring tools, with approval-gated destructive operations.1461MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Desktop to work with a local Windows 10/11 machine through scoped project file editing, read-only PowerShell/CMD diagnostic tasks, desktop observation, and locally approved mouse/keyboard interaction with allowlisted applications.MIT
TDQS
Scored across 40 tools
Most tools target clearly distinct resources and actions (git_* vs github_* vs file operations vs plan/checkpoint tools). A few clusters overlap enough to require careful reading: read_file vs read_files, preview_replace vs replace_exact vs edit_lines, run_task vs run_command, and checkpoint_read vs resume_context. The descriptions generally resolve these, so misselection is possible but not likely.
All names use snake_case, but ordering is mixed: verb-first (read_file, search_code, restore_snapshot) coexists with noun-first (workspace_info, project_tree, command_catalog, project_notes_read, checkpoint_save, github_pr_list). The pattern is readable and predictable within categories, but the inconsistent verb/noun ordering keeps it from being a clean convention.
40 tools is heavy for a coding-assistant server, spanning filesystem, git, GitHub, plans, checkpoints, commands, notes and audit. Several tools could be consolidated (read_file/read_files, the three checkpoint tools, plan_get with resume_context), so the surface feels over-scoped rather than each tool earning a distinct place.
Coverage is broad: file read/write/edit/move/delete with snapshots, git status/diff/log/branch/stage/commit, GitHub repo/PR/issue reads plus PR creation, plus plans, checkpoints, notes, audit and command execution. Noticeable gaps remain around git push/pull, GitHub issue creation/update, and PR review/merge, but core coding workflows are workable.