Claude Free Code MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKSPACE_PATH | Yes | Absolute path to the single project folder the server is allowed to work with, passed as the argument to src/index.js (e.g. "C:\\Projects\\MyProject"). Select only a project folder you trust — never your entire drive or home directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workspace_infoA | Show project root, project type, configured execution limits and capabilities. |
| project_treeA | List a bounded directory tree. Excludes heavy dependency directories by default. |
| glob_filesB | Find files matching a glob such as src/**/*.js, *.json or */test.py. |
| search_codeA | Search text in workspace source files, with line numbers, bounded results and total bytes. |
| read_fileB | Read a UTF-8 source file by line range, including a SHA-256 concurrency token. |
| read_filesA | Read up to 8 UTF-8 files, capped at 40 KB each for context gathering. |
| preview_replaceA | Preview a unique exact-string replacement without modifying the file. |
| write_fileA | Create a UTF-8 file. Overwriting an existing file requires overwrite=true. Changes get snapshots. |
| replace_exactA | Replace exactly one occurrence of text. Uses atomic write with undo snapshot. |
| edit_linesA | Apply multiple non-overlapping 1-based line edits atomically, with snapshot and optional expectedSha256. |
| make_directoryA | Create a folder inside the workspace. |
| move_pathA | Move/rename a workspace file or folder, after approval in the local panel. No overwrites. |
| delete_pathA | Delete a regular file (with undo snapshot) or an EMPTY folder. Requires approval; recursive deletion is disabled. |
| list_snapshotsC | See available undo snapshots for file changes. |
| restore_snapshotA | Restore a saved pre-edit version if the current hash still matches the snapshot. Requires local approval. |
| git_statusB | Read Git status and current branch. |
| git_diffA | Read unstaged or staged Git diffs; outputs are limited to 96 KB. |
| git_logC | Read recent commits. |
| git_branchesB | List local Git branches. |
| git_stageA | Stage selected workspace file paths. Requires GUI approval. |
| git_commitA | Create a Git commit with an explicit message; requires GUI approval. Hooks may execute. |
| git_remoteB | View Git remotes without changing repository settings. |
| git_create_branchB | Create and switch to a new local Git branch after local approval. |
| github_repo_viewB | Show GitHub repository metadata through optional authenticated gh CLI. |
| github_pr_listA | List GitHub pull requests in the current repository using gh CLI (requires gh auth). |
| github_issue_listB | List GitHub issues in the current repository using gh CLI (requires gh auth). |
| github_pr_createA | Open a GitHub pull request using gh CLI. Requires local approval. Assumes branch has been pushed. |
| command_catalogA | List allowed executable names and predefined development tasks. Every executable task requires local approval. |
| run_taskA | Execute a predefined npm or git task; build/test/lint/format/typecheck require local human approval. |
| run_commandA | Run a chosen developer executable using argument-array (no implicit shell), workspace cwd, timeout and human approval. |
| plan_createB | Create or replace a local project plan with up to 30 steps, visible in the dashboard. |
| plan_updateA | Update step status and notes in an existing project plan. |
| plan_getA | Read the current persisted task plan. |
| project_notes_readA | Read local project instructions/notes persisted outside the workspace. |
| project_notes_writeA | Save project-specific coding instructions and conventions. Does not alter source files. |
| checkpoint_saveA | Save a restart/resume checkpoint for when Claude Free reaches its conversation limit. |
| checkpoint_listA | List saved context checkpoints across Claude conversations. |
| checkpoint_readB | Read a saved checkpoint by ID, or the most recent one. |
| resume_contextA | Read notes, current plan, recent checkpoint and Git status to help resume after a free-tier limit. |
| audit_recentC | Inspect recent local operations and approval decisions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.