SkillFoxx

Type a name, a task or a service

Match with Foxx AI

GigaCode Bridge MCP

Gigacode-bridge-mcp

MCP server that delegates isolated code edits to GigaCode CLI in temporary Git worktrees and returns a patch for independent review

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • The GigaCode agent edits repository files in a temporary worktree, which is not an OS sandbox
  • The patch comes back for review and an error in it reaches the project only when applied
All reasons and checks
Russian stack

grishingrishin/gigacode-bridge-mcpAuthor:grishingrishin

Install

Services

Manual install

make setup

In the extracted release archive directory; choose Codex for automatic registration.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The GigaCode agent edits repository files in a temporary worktree, which is not an OS sandbox
  • The patch comes back for review and an error in it reaches the project only when applied

This is third-party code. Review the repository files before installing.

What it does

The Go server works over stdio and gives a primary agent such as Codex a tool for delegating small tasks to the GigaCode CLI agent. Each task runs in a temporary Git worktree and the result comes back as a patch. The decision on a task, acceptance and applying the patch stays with the primary agent: the server applies nothing to the original project and makes no commits. Installation is from a release archive for macOS on Apple Silicon or Intel and Linux on amd64 or arm64 with `make setup`. The installer registers the server in Codex, backs up `config.toml` and keeps other entries. For other clients it prints the path of the executable, and connection is manual. An optional `delegate-to-gigacode` skill is copied to `~/.codex/skills` and hints to the agent which tasks to hand over. API documentation, small mechanical edits and focused tests fit well. Architectural decisions, security changes and complex logic stay with the primary agent.

Who it is for. Developers on Codex who want to offload small routine to GigaCode CLI and accept the result only after reviewing the patch.

Good fit when

  • Exported functions in `src/utils.go` get documentation with no change of behavior
  • A series of similar edits goes to a second agent while the main one handles a harder task
  • Focused tests are written for a function and the primary agent reviews the patch
  • Edits are isolated in a separate tree so the working directory stays clean

Not a fit when

  • The repository has uncommitted changes: the server neither saves nor stashes them and declines delegation
  • The task creates new files: only existing tracked files are supported for now
  • The system is Windows: binary builds exist only for macOS and Linux
  • The edit touches security or complex business logic

Example request

Add documentation to the exported functions in src/utils.go without changing their behavior and show the patch before applying.

MCP

Transport
stdio
Authentication
not required

Environment variables

GIGACODE_BIN
Path to GigaCode CLI if it is not at `~/.gigacode/bin/gigacode`.

Limitations

A clean Git working tree with at least one commit, an installed and signed-in GigaCode CLI at `~/.gigacode/bin/gigacode` (another path is set with the `GIGACODE_BIN` variable) and a stdio client are required.

Only specified existing tracked files of one repository can be changed. A temporary worktree isolates Git edits but does not replace an OS sandbox, so trust only your own projects and tasks. Operation is verified on macOS, while Linux builds are cross-compiled without a check on a real host. Binaries are not signed or notarized and macOS will require allowing the launch manually.

How to disable. Run `make teardown` in the archive directory and choose removal of the Codex connection and the binary, or `make uninstall` to remove the binary only.

FAQ

How do I install GigaCode Bridge MCP?

Download the release archive for your platform, extract it and run `make setup`. Building from source needs Go 1.25 or newer.

Does the server apply the patch to the project?

No. It returns a patch for review and the primary agent or a person applies it. The server makes no commits.

How do I check the connection without calling the model?

Run `gigacode-bridge-mcp --check` from the install directory, `~/.local/bin` by default.

How do I set another GigaCode path?

Pass the `GIGACODE_BIN` variable when registering the server: `codex mcp add gigacode-bridge-mcp --env GIGACODE_BIN=... -- <binary>`.

Which tasks should be delegated?

Documentation, small mechanical edits and focused tests. The `delegate-to-gigacode` skill hints at this choice to the primary agent without forcing a call.

Discussion

No questions or reviews yet.

All GigaChat tools
Russian stack

A small Python MCP server for Sber's GigaChat API: authorizes with a Basic key and calls the models directly from an agent, tested on OpenCode under Windows

MCP serverExtended access
Russian stack

A GigaCode workspace where the assistant takes a task in words, finds a ready process made of steps and runs it with a plan and a report in outputs

WorkflowExtended access

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialAuthenticationRepository starsMain difference
GigaCode Bridge MCP (this card)nonot required0
GigaCode project flows with hooks, gates and OpenSpecno0a set of roles for GigaCode without a bridge from another agent
GigaMCP: a Chrome extension with MCP tools for GigaChatno0a GigaChat server without code edit delegation

README in short

The English README has requirements, installation from an archive, an example request, a delegation task table, limitations, troubleshooting, update, removal and building from source.

README badge

Report a problem

Foxx AIGigaCode Bridge MCP
Foxx AI

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.