Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

Explore. Edit. Build. Test. Resume.

Overview · Features · Installation · Tools · Dashboard · Security · Roadmap


Overview

Claude Free Code MCP is an open-source, local Model Context Protocol (MCP) server that equips Claude Desktop with practical software-development tools. It can inspect a selected workspace, search code, make controlled edits, run approved commands, work with Git and GitHub, and save progress for later conversations.

Built with Node.js 20+, it uses the MCP stdio transport and requires no third-party npm packages. A private browser dashboard lets you approve sensitive operations before they execute.

IMPORTANT

This is not official Claude Code. It does not unlock paid Claude features, increase Free-tier usage limits, or make Claude Desktop an autonomous background agent. MCP availability depends on the Claude Desktop version and account. This local MCP server itself does not require a paid API key.

At a glance

Component

v1.0.0

Language

JavaScript (ES modules), Node.js 20+

Protocol

Local MCP over JSON-RPC stdio

Tools

40 coding and workflow tools

Workspace

One selected project directory per instance

Interface

Claude Desktop + private local approval dashboard

Network

Not required for basic local tools; GitHub uses optional gh

Persistence

Plans, notes, snapshots, checkpoints, audit logs

Tests

10 automated Node.js tests; Linux CI with Node 20 and 22


Related MCP server: Local Dev Bridge MCP

Features

Workspace exploration and bounded directory listing
Literal source-code search and glob matching
Multi-file reading and SHA-256 concurrency metadata
Create, replace, edit, move and delete project files
Preview changes and undo with guarded snapshots
Git status, diffs, history, branches, staging and commits
Optional GitHub repositories, issues and pull requests
Development tasks: test / build / lint / format / typecheck
Human-approved developer commands, PowerShell and CMD
Private local dashboard: approve, deny, trust or revoke
Project plans, notes, checkpoints and resume context
Audit trail for recent operations and permission decisions

Supported workflows

Environment

What it can do

Node.js / JavaScript / TypeScript

Search, edit and execute installed npm scripts

Python

Inspect and edit Python files, invoke installed Python tools

Java / Minecraft plugins

Work on Java sources and invoke Java/Maven/Gradle if installed

Go / Rust / .NET

Explore files and invoke installed toolchains

Git

Inspect changes, stage, commit and branch with approval

GitHub

Inspect repo/issue/PR information, create PRs via authenticated GitHub CLI

Compilers, SDKs, Git and GitHub CLI are not bundled. Install the tools you need separately and ensure they are in your PATH.


What It Is

+ A local MCP coding toolbox for Claude Desktop
+ A workspace-scoped source explorer and editor
+ A human-approved development command runner
+ A Git and optional GitHub workflow companion
+ A plan and checkpoint system to preserve context
+ A local dashboard for managing permissions

What It Is Not

- Official Anthropic Claude Code
- A way to bypass subscription or message limits
- An autonomous agent running without Claude Desktop
- A guarantee that every Claude Free account supports MCP
- An operating-system sandbox for approved commands
- A replacement for backups, Git or code review

How It Works

                     Claude Desktop
                  (Free or paid plan)
                           |
                 MCP / JSON-RPC stdio
                           |
                           v
              +--------------------------+
              |    Claude Free Code MCP  |
              |       Node.js Server     |
              +--------------------------+
                           |
        +------------------+------------------+
        |                  |                  |
        v                  v                  v
  Workspace Tools     Git / Commands      Local Context
  Read / Search       Build / Tests       Plans / Notes
  Write / Undo        GitHub via gh       Checkpoints
        |                  |                  |
        +------------------+------------------+
                           |
                           v
                Permission Coordinator
                           ^
                           |
                 127.0.0.1 dashboard
                 Approve / Deny / Trust
                           |
                           v
                  Selected Workspace

Claude decides when to call tools. The MCP does not independently generate prompts or continue coding when the chat stops.


Installation

Requirements

Component

Required?

Purpose

Claude Desktop

Yes

MCP client (tool access depends on account/version)

Node.js 20+

For manual setup

Run the local MCP server

Git

Optional

Git commands and history

GitHub CLI (gh)

Optional

GitHub repository/issue/PR operations

Language SDKs

Optional

Project builds and tests

API key

No

Not needed by the local MCP server

Method 1 — Claude Desktop extension (.mcpb)

If you have a compatible .mcpb distribution of this project:

  1. Open an updated Claude Desktop application.

  2. Go to Settings → Desktop app → Extensions (labels may vary).

  3. Select Install Extension and choose the .mcpb file.

  4. Select only the project folder you want Claude to work with.

  5. In a Claude conversation, ask: “Use workspace_info and project_tree to inspect my project.”

NOTE

The source repository contains an extension manifest, but doesnot guarantee a downloadable .mcpb on GitHub Releases. If you do not have a compatible package, use the manual method below.

Method 2 — Windows / PowerShell (manual configuration)

Clone the project:

git clone https://github.com/ImIpscanning/Claude-Free-Code-MCP.git
cd Claude-Free-Code-MCP
node --version
npm test

If Git is unavailable, choose Code → Download ZIP on GitHub and extract it.

Open Claude Desktop configuration:

%APPDATA%\Claude\claude_desktop_config.json

Add an MCP server entry (replace both paths with your own):

{
  "mcpServers": {
    "claude-free-code": {
      "command": "node",
      "args": [
        "C:\\Tools\\Claude-Free-Code-MCP\\src\\index.js",
        "C:\\Projects\\MyProject"
      ]
    }
  }
}
CAUTION

If the config already contains other MCP servers,merge the new entry rather than overwriting their settings. Keep the doubled backslashes in Windows JSON paths.

Restart Claude Desktop. Ask it to call workspace_info to verify the connection. You can create separate entries for different workspaces.

Manual run / diagnostics

node src/index.js "C:\Projects\MyProject"
npm test
npm run check

The MCP uses stdio, not an interactive shell menu. Claude Desktop is the MCP client.


Local Approval Dashboard

The browser dashboard is used for reviewing sensitive actions such as running programs, removing files, restoring snapshots, Git writes and PR creation.

With Claude Desktop and the MCP already running, launch:

npm run panel

Open the private URL printed in the terminal, similar to:

http://127.0.0.1:8765/?token=<your-private-token>

The port may change when occupied; never share an actual dashboard link or token.

Decision

Result

Approve once

Allow the requested action once

Deny

Reject it without executing

Trust exact request

Remember this action and parameter signature

Revoke

Remove a saved authorization

Audit

View recent operations and approval decisions

The dashboard is bound to 127.0.0.1, protected by a token, and checks the origin of write requests. Approval is not an OS sandbox: commands you approve run with your account's system permissions.


MCP Tool Reference

40 tools, organized by function:

Workspace & Search — 6

workspace_info       Show workspace, manifests and limits
project_tree        Explore a bounded folder tree
glob_files          Find files matching a pattern
search_code         Search literal code text and line numbers
read_file           Read file line ranges with SHA-256 token
read_files          Read a small batch of files

Editing — 7

preview_replace     Preview an exact replacement
write_file          Create or explicitly overwrite a file
replace_exact       Replace one exact occurrence
edit_lines          Apply non-overlapping line edits
make_directory      Create a folder
move_path           Move or rename with local approval
delete_path         Delete a file or empty directory with approval

Undo Snapshots — 2

list_snapshots      List earlier file states
restore_snapshot    Restore a snapshot with checks and approval

Git — 8

git_status          View working tree and current branch
git_diff            Inspect staged or unstaged diffs
git_log             View recent commits
git_branches        List local branches
git_stage           Stage selected files with approval
git_commit          Commit with approval
git_remote          View Git remotes
git_create_branch   Create/switch branch with approval

GitHub — 4

github_repo_view    Read repository metadata via gh
github_pr_list      List GitHub pull requests
github_issue_list   List GitHub issues
github_pr_create    Open pull request with local approval

GitHub integration uses your local GitHub CLI session. Install gh and authenticate using gh auth login.

Execution — 3

command_catalog     List allowed developer commands and tasks
run_task            Run a predefined development task
run_command         Run a chosen executable with argument array

run_task supports test, build, lint, format, typecheck, git-status and git-diff. Supported commands include Node.js, npm, Git, Python, Java, Go, Rust, .NET, PowerShell, CMD and others listed by command_catalog. Executions have time/output bounds and may require local approval.

Planning & Continuity — 9

plan_create         Create or replace a step-by-step plan
plan_update         Track todo / doing / done / blocked
plan_get            Read the saved plan
project_notes_read  Read persistent project notes
project_notes_write Save project conventions
checkpoint_save     Record progress and next steps
checkpoint_list     List saved checkpoints
checkpoint_read     Read a saved checkpoint
resume_context      Load plan, notes, checkpoint and Git status

Audit — 1

audit_recent        Inspect recent tool operations and decisions

Example Coding Sessions

Explore a project:

Use workspace_info, project_tree and search_code to map this repository. Explain the architecture before changing code.

Fix a bug:

Locate the cause, preview your proposed change with preview_replace, apply the smallest edit, inspect git_diff and ask before running tests.

Implement a feature:

Create a plan with plan_create. Work through the steps, verify after each one, and save a checkpoint if interrupted.

Prepare a pull request:

Review git_status and git_diff, stage only the intended files, describe the commit and request approval before opening a PR.

Resume after a Claude Free usage limit:

Before stopping:

Save checkpoint_save with finished work, blockers and next steps.

In a later conversation:

Use resume_context and the latest checkpoint. Check Git status and continue from unfinished work.

Checkpoints do not automatically restart Claude after its quota resets. You resume the conversation manually.


Project Structure

Claude-Free-Code-MCP/
├── .github/workflows/
│   └── tests.yml           CI: Node 20 / 22
├── src/
│   ├── index.js            MCP server bootstrap
│   ├── mcp.js              JSON-RPC stdio transport
│   ├── tools.js            40 MCP tool handlers
│   ├── paths.js            Workspace path protections
│   ├── process.js          Process runner / task catalog
│   ├── approvals.js        Approval and trust management
│   ├── dashboard.js        Private local HTTP interface
│   ├── dashboard-link.js   Discover dashboard URLs
│   ├── storage.js          Notes, snapshots, checkpoints, audit
│   └── config.js           Limits and configuration
├── test/
│   ├── dashboard.test.js
│   ├── mcp.test.js
│   └── tools.test.js
├── manifest.json
├── package.json
├── ARCHITECTURE.md
├── SECURITY.md
├── LICENSE
└── README.md

See Architecture and Security for further technical details.


Testing

npm test
npm run check

The automated suite tests MCP initialization and calls, tool schemas, extension metadata, path checks, edits and undo, approval behavior, persistence, deletion safeguards and dashboard access.

GitHub Actions runs the checks on Ubuntu with Node.js 20 and 22. Automated tests cannot guarantee compatibility with all Windows and Claude Desktop versions.

CI Tests


Security & Limitations

  • Workspace confinement: built-in file tools reject absolute paths, traversal, symlink escapes and direct Git-internal edits.

  • Approval: sensitive operations can require human review in the local panel; saved permissions are revocable.

  • Undo snapshots: restores check current hashes to reduce accidental overwrites of newer changes.

  • No OS sandbox: approved scripts, compilers and shells may access other files or networks.

  • External execution risk: npm scripts, Git hooks, build systems and GitHub CLI can have side effects.

  • Privacy: MCP notes/checkpoints are stored locally, but files sent into Claude chat follow your Claude account's data settings and terms.

  • Free-tier limits: Anthropic decides availability and usage limits for its chat and MCP features.

  • No background agent: progress is saved, but coding does not continue unattended.

WARNING

Select only a project folder you trust.Do not select your entire drive or home directory. Review every proposed command, avoid running as Administrator, and make Git commits or backups before significant edits.

See SECURITY.md for the complete security model.


Roadmap

Version / Phase

Focus

Status

v1.0.0

40 tools, dashboard, Git, snapshots and checkpoints

Current

Future

More Windows/Claude Desktop integration tests

Planned

Future

Improved diffs, rollback UX and error reporting

Proposed

Future

Optional .mcpb release automation

Proposed

Future

Additional per-project permission presets

Proposed

Planned work is not a statement of released functionality.


Technologies


Contributing

Bug reports, documentation changes, test cases and pull requests are welcome. Include your OS, Node.js version, reproduction steps, expected result and observed result. Remove secrets, tokens and private paths before sharing logs.

License

Distributed under the MIT License. See LICENSE.

Author

Developed by ImIpscanning.

Explore.
Edit.
Build.
Test.
Resume.

Claude Free Code MCP — Local Tools for Claude Desktop

Available Tools

40 tools
audit_recentC
Read-only

Inspect recent local operations and approval decisions.

Inputs: count.

checkpoint_listA
Read-only

List saved context checkpoints across Claude conversations.

Inputs: limit.

checkpoint_readB
Read-only

Read a saved checkpoint by ID, or the most recent one.

Inputs: id.

checkpoint_saveA

Save a restart/resume checkpoint for when Claude Free reaches its conversation limit.

Inputs: title (required), summary (required), nextSteps (required).

command_catalogA
Read-only

List allowed executable names and predefined development tasks. Every executable task requires local approval.

Inputs: no named parameters.

delete_pathA
Destructive

Delete a regular file (with undo snapshot) or an EMPTY folder. Requires approval; recursive deletion is disabled.

Inputs: file (required).

edit_linesA
Destructive

Apply multiple non-overlapping 1-based line edits atomically, with snapshot and optional expectedSha256.

Inputs: file (required), edits (required), expectedSha256.

git_branchesB
Read-only

List local Git branches.

Inputs: no named parameters.

git_commitA
Destructive

Create a Git commit with an explicit message; requires GUI approval. Hooks may execute.

Inputs: message (required).

git_create_branchB
Destructive

Create and switch to a new local Git branch after local approval.

Inputs: branch (required).

git_diffA
Read-only

Read unstaged or staged Git diffs; outputs are limited to 96 KB.

Inputs: file, staged.

github_issue_listB
Read-only

List GitHub issues in the current repository using gh CLI (requires gh auth).

Inputs: limit.

github_pr_createA
Destructive

Open a GitHub pull request using gh CLI. Requires local approval. Assumes branch has been pushed.

Inputs: body (required), title (required), base.

github_pr_listA
Read-only

List GitHub pull requests in the current repository using gh CLI (requires gh auth).

Inputs: limit.

github_repo_viewB
Read-only

Show GitHub repository metadata through optional authenticated gh CLI.

Inputs: no named parameters.

git_logC
Read-only

Read recent commits.

Inputs: count.

git_remoteB
Read-only

View Git remotes without changing repository settings.

Inputs: no named parameters.

git_stageA
Destructive

Stage selected workspace file paths. Requires GUI approval.

Inputs: files (required).

git_statusB
Read-only

Read Git status and current branch.

Inputs: no named parameters.

glob_filesB
Read-only

Find files matching a glob such as src/**/*.js, *.json or */test.py.

Inputs: glob (required), limit, directory.

list_snapshotsC
Read-only

See available undo snapshots for file changes.

Inputs: file, limit.

make_directoryA

Create a folder inside the workspace.

Inputs: directory (required).

move_pathA
Destructive

Move/rename a workspace file or folder, after approval in the local panel. No overwrites.

Inputs: to (required), from (required).

plan_createB

Create or replace a local project plan with up to 30 steps, visible in the dashboard.

Inputs: goal (required), steps (required).

plan_getA
Read-only

Read the current persisted task plan.

Inputs: no named parameters.

plan_updateA

Update step status and notes in an existing project plan.

Inputs: step (required), status (required), note.

preview_replaceA
Read-only

Preview a unique exact-string replacement without modifying the file.

Inputs: file (required), search (required), replacement (required).

project_notes_readA
Read-only

Read local project instructions/notes persisted outside the workspace.

Inputs: no named parameters.

project_notes_writeA

Save project-specific coding instructions and conventions. Does not alter source files.

Inputs: text (required).

project_treeA
Read-only

List a bounded directory tree. Excludes heavy dependency directories by default.

Inputs: maxDepth, directory, includeHidden.

read_fileB
Read-only

Read a UTF-8 source file by line range, including a SHA-256 concurrency token.

Inputs: file (required), maxLines, startLine.

read_filesA
Read-only

Read up to 8 UTF-8 files, capped at 40 KB each for context gathering.

Inputs: files (required).

replace_exactA
Destructive

Replace exactly one occurrence of text. Uses atomic write with undo snapshot.

Inputs: file (required), search (required), replacement (required), expectedSha256.

restore_snapshotA
Destructive

Restore a saved pre-edit version if the current hash still matches the snapshot. Requires local approval.

Inputs: snapshotId (required).

resume_contextA
Read-only

Read notes, current plan, recent checkpoint and Git status to help resume after a free-tier limit.

Inputs: no named parameters.

run_commandA
Destructive

Run a chosen developer executable using argument-array (no implicit shell), workspace cwd, timeout and human approval.

Inputs: args (required), reason (required), command (required), cwd, +1 more.

run_taskA
Destructive

Execute a predefined npm or git task; build/test/lint/format/typecheck require local human approval.

Inputs: task (required), timeoutSeconds.

search_codeA
Read-only

Search text in workspace source files, with line numbers, bounded results and total bytes.

Inputs: query (required), glob, limit, directory, +1 more.

workspace_infoA
Read-only

Show project root, project type, configured execution limits and capabilities.

Inputs: no named parameters.

write_fileA
Destructive

Create a UTF-8 file. Overwriting an existing file requires overwrite=true. Changes get snapshots.

Inputs: file (required), content (required), overwrite, expectedSha256.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 40 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers