cahn91/gpt-repo-mcp

★ 28TypeScriptAudience · vibe coderComplexity · 3/5Setup · moderate

Mindmap

mindmap
  root((repo))
    What it does
      ChatGPT to local repo
      Read and write files
      Plan and commit code
    Permission modes
      Read only
      Write mode
      Ship mode
    Safety
      No push or shell
      Path boundaries
      Secret file guards
    Workflow
      Plan then implement
      Git diff review
      Agent coordination

mindmap root((repo)) What it does ChatGPT to local repo Read and write files Plan and commit code Permission modes Read only Write mode Ship mode Safety No push or shell Path boundaries Secret file guards Workflow Plan then implement Git diff review Agent coordination

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Ask ChatGPT in plain language to read and summarize files in your local project without leaving the chat interface.

USE CASE 2

Have ChatGPT plan a code change, write it directly into your repo, and show you the git diff for review.

USE CASE 3

Coordinate between ChatGPT and another AI coding agent by saving task descriptions to files and reading back their output.

USE CASE 4

Grant read-only access to ChatGPT so it can inspect your codebase and git history without risk of changes.

Tech stack

TypeScriptNode.js

Getting it running

Difficulty · moderate Time to first run · 30min

Requires Node.js 20+ and a tunneling service to expose a local URL that ChatGPT can reach from outside your machine.

No license information was mentioned in the explanation.

In plain English

GPT Repo MCP is a TypeScript server that connects ChatGPT to code repositories on your local machine. Once set up, you can ask ChatGPT in plain language to read files, inspect the current state of changes, plan edits, and write code directly into your project. It acts as a bridge between the ChatGPT web interface and your local file system. The connection works through a tunneling service that gives ChatGPT a URL it can reach from outside your machine. You approve which repositories ChatGPT can access and choose a permission level for each one. The read mode lets ChatGPT look at files and git history but change nothing. The write mode adds the ability to create or update files, with safety checks for file size, path boundaries, and accidental inclusion of secrets. The ship mode further allows staging and committing changes locally, but never pushing to a remote or running arbitrary shell commands. The main workflow the tool supports is having ChatGPT plan a change, optionally implement it directly by writing files, review the resulting git diff, and then recommend the next step. There is also a coordination flow for working with other AI coding agents: ChatGPT can prepare a task description for a tool like Codex or Claude, save it to a file in the repository, and later read back whatever that agent wrote as a result. The tool provides a structured set of named operations covering repository browsing, file reading, planning, git review, file writing, and local commit preparation. There are no tools for operations like push, rebase, branch deletion, or running shell commands. The project is not affiliated with OpenAI or Anthropic. It requires Node.js version 20 or later and is released as an open-source TypeScript project.

Copy-paste prompts

Prompt 1

I want to set up gpt-repo-mcp so ChatGPT can read my local TypeScript project, walk me through installing it, running the tunneling service, and approving my repo with read-only permissions.

Prompt 2

How do I use gpt-repo-mcp in write mode to have ChatGPT implement a new feature in my repo and then review the git diff before committing?

Prompt 3

Show me the coordination flow: how do I use gpt-repo-mcp to have ChatGPT write a task file for Claude to implement, then read back Claude's output?

Prompt 4

What safety limits does gpt-repo-mcp enforce in write mode, specifically around file size, path boundaries, and secrets?

Open on GitHub → Explain another repo

← cahn91 on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.