All servers / Developer / Repo Bridge MCP server
Repo Bridge MCP server
MCP server that turns ChatGPT Web into a real coding agent on your own repositories: read, search, edit, build, test, git, pull requests. OAuth 2.1. No OpenAI A
Tested by ConnectATDScore 84 out of 100. Tested 2026-11-18 on package version 1.0.1. Package: repo-bridge-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 14 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.7 seconds including download)
- Tools offered: 27
- Last published: 2026-08-08
- Weekly downloads (npm): 1,804
- License: MIT · Direct dependencies: 1
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
workspace_listno parametersList repositories the bridge can open and which one is currently active. Call this first when you do not know what is available.
workspace_open1 of 1 parameter describedOpen a local repository and return a full project brief: languages, build system, detected build/test/lint commands, module layout, git state, and the repo's AGENTS.md / CLAUDE.md instructions. Accepts an alias from workspace_list or an absolute path inside a configured root. Makes the workspace active for subsequent tool calls.
workspace_info1 of 1 parameter describedCurrent state of a workspace without re-reading the repository: branch, working-tree changes, recent commits, detected commands, and everything this bridge session has already changed. Use this to resume work ("continue on quantix").
repo_open_remote4 of 4 parameters describedClone (or refresh) a remote Git repository into an isolated managed workspace and check out a branch. Use for work on a repository that is not already on this machine. Returns the same project brief as workspace_open. Each task gets its own workspace so parallel tasks cannot interfere.
workspace_close2 of 2 parameters describedStop tracking a workspace. For managed (cloned) workspaces you can also delete the directory to reclaim disk. Never deletes a local workspace's files.
list_dir5 of 5 parameters describedList files and directories. Use for orientation in an unfamiliar area of the repo. Build outputs, node_modules and .git are skipped automatically. Prefer search_code when you are looking for something specific.
read_file5 of 5 parameters describedRead a file as text. Returns exact file content (no line numbers by default) so it can be copied verbatim into edit_file anchors. For large files pass start_line/end_line, or use search_code first to find the region worth reading. Credential files (.env, keys, cloud config) are never returned.
search_code9 of 9 parameters describedSearch file contents across the repository and return matching lines with file:line locations. This is the primary way to find code — far cheaper than reading files. Supports literal or regex patterns, glob filters, and surrounding context lines. Respects .gitignore.
find_files4 of 4 parameters describedFind files by name or glob pattern (e.g. "**/*Service.java", "**/test_*.py"). Use when you know roughly what a file is called but not where it lives.
write_file4 of 4 parameters describedCreate a new file, or replace / append to an existing one. Use this for NEW files. To change part of an existing file use edit_file instead — it is safer and much cheaper than resending the whole file.
edit_file3 of 3 parameters describedMake targeted edits to an existing file by replacing exact text. Each edit's old_string must appear exactly once (include surrounding lines to disambiguate) unless replace_all is set. All edits are applied atomically — if any anchor fails to match, the file is left untouched and you are told why. This is the preferred way to modify code.
move_path4 of 4 parameters describedMove or rename a file or directory inside the workspace.
delete_path3 of 3 parameters describedDelete a file, or a directory tree with recursive=true. Deleting the workspace root is refused. Prefer deleting specific files over directories.
create_dir2 of 2 parameters describedCreate a directory (including parents). write_file already creates parent directories, so this is only needed for empty directories.
file_info2 of 2 parameters describedCheck whether a path exists and get its size and modification time, without reading it.
run_command5 of 5 parameters describedRun a development command in the workspace (build tools, package managers, test runners, git, language toolchains). Commands run WITHOUT a shell: pipes, redirects, && and ; are rejected — issue separate calls instead. Only allowlisted executables are permitted; destructive commands require confirm=true. Prefer run_build / run_tests / run_lint, which pick the right command for this project automatically.
run_build5 of 5 parameters describedBuild the project using the build command detected from the repository (Maven, Gradle, npm/pnpm/yarn script, cargo, go, dotnet, make…). Returns exit code and output with error lines preserved even when the log is long.
run_tests5 of 5 parameters describedRun the project test suite using the command detected from the repository. Failing output is summarised with the failure lines pulled out, so you can go straight from "tests failed" to the responsible code. This is the tool to use in an implement → test → fix loop.
run_lint5 of 5 parameters describedRun the project linter / static checks using the command detected from the repository (eslint, ruff, clippy, go vet, spotless…).
git_status1 of 1 parameter describedCurrent branch, upstream tracking, ahead/behind counts, and every staged / unstaged / untracked file. Check this before committing, and to notice user changes you did not make.
git_diff5 of 5 parameters describedShow changes as a unified diff. against="worktree" (default, unstaged changes), "staged", "head" (staged + unstaged), or a branch/commit name to compare the current branch against it (uses the merge base). Use stat_only=true first on a large change to see which files moved before pulling in the full diff.
git_log3 of 3 parameters describedRecent commits, newest first. Useful for matching the project's commit-message conventions before committing.
git_branch4 of 4 parameters describedList branches, or create / switch to one. Creating a feature branch is the normal first step before making changes, since commits to protected branches are refused.
git_commit3 of 3 parameters describedStage and commit changes. By default every modified and untracked file is staged; pass `paths` to commit a subset. Refuses to commit on a protected branch — create a feature branch first. Write the message in the style of the repository's recent commits (check git_log).
git_restore4 of 4 parameters describedDiscard changes to specific files, or unstage them. This destroys uncommitted work, so it requires confirm=true and specific paths — it will never discard everything at once.
bridge_statusno parametersWhat this bridge is allowed to do: permission level, which capabilities are enabled, which executables may run, timeouts and output limits, protected branches, and whether GitHub/GitLab tokens are configured. Check this when a tool is refused, or before planning work that needs to push.
report_changes2 of 2 parameters describedSummarise everything done in this workspace: files changed (with per-file line counts from git), commands run and whether they passed, git operations, current branch and commit state. Use this to write an accurate final report instead of relying on memory — and to see what is still uncommitted.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.