Cursor Bridge plugin
Two MCP plugins for Windows: Cursor Bridge serves Cursor index answers to Codex and Claude Code, Grok Build Supervisor runs Grok.
- 83 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The bridge drives the Cursor app through remote debugging and can run its agent on a task
- The supervisor hands implementation to the Grok Build agent, which changes project files
Install
- Works in
Manual install
claude plugin marketplace add Vanyangyang/cursor-bridgeThen `claude plugin install cursor-bridge@vanyangyang` and a client restart. For Grok Build Supervisor: `claude plugin install grok-build-supervisor@vanyangyang`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The bridge drives the Cursor app through remote debugging and can run its agent on a task
- The supervisor hands implementation to the Grok Build agent, which changes project files
This is third-party code. Review the repository files before installing.
What it does
The repository holds two independent plugins. Cursor Bridge opens the Cursor context engine (CCE) to the Codex, Claude Code, Grok Build and Pi clients, meaning the ready project index and the Cursor agent search. One project question returns compact `path:line` references with a relevance note, so the main agent does not guess directories or repeat `grep`. The optional `cursor_do` tool sends a clearly scoped task to the Cursor agent. Grok Build Supervisor works differently: the plan and review stay with Codex, Claude Code or Pi while Grok Build does the implementation, and the supervisor follows the run and the checks. By default the CCE source is the Cursor IDE through remote debugging, and an experimental CLI mode exists with your own key for an OpenAI-compatible provider.
Who it is for. Windows users who work in Codex or Claude Code but want the Cursor project index and the Grok Build agent.
Good fit when
- Codex must find where a function is implemented in the project and get `path:line` references from the Cursor index
- A small clearly scoped task should go to the Cursor agent straight from the current client through `cursor_do`
- The plan and review stay with your client while implementation goes to Grok Build under supervision
- You need to check the Cursor connection state with `cursor_status`
Not a fit when
- You work on macOS or Linux: the plugins support Windows only and were not accepted elsewhere
- You need old Cursor versions: the author supports only the latest and ships no fixes for archived releases
- Cursor is not installed and signed in: an installed Cursor and a local project it can open are required
Example request
Through Cursor Bridge find where payment is handled in the project and return path:line references with short notes.Limitations
Windows 11 only: live testing ran on Cursor 3.23.12 and macOS was not accepted. Node.js 18 or newer, an installed and signed-in Cursor and a project it can open are required. The bridge drives Cursor through remote debugging on port `9223` and does not inspect your subscription, so models and quotas stay whatever Cursor already has. The author supports only the latest Cursor. The CLI mode for CCE is experimental and not yet stable. Upgrading from version 5.3.6 or earlier needs a one-time migration.
How to disable. In Claude Code run `claude plugin uninstall cursor-bridge@vanyangyang` and in Codex remove the plugin through plugin management. Stop the related Cursor processes with debug port `9223` and return to a normal Cursor launch.
FAQ
How do I install Cursor Bridge in Codex?
Run `codex plugin marketplace add Vanyangyang/cursor-bridge --ref main` and `codex plugin add cursor-bridge@vanyangyang`. The Grok supervisor installs separately: `codex plugin add grok-build-supervisor@vanyangyang`.
How do I install it in Claude Code?
Run `claude plugin marketplace add Vanyangyang/cursor-bridge` and `claude plugin install cursor-bridge@vanyangyang`, then restart the client and initialize the plugin. The supervisor installs with `claude plugin install grok-build-supervisor@vanyangyang`.
What is CCE?
Cursor Context Engine: the existing Cursor project index and agent search. The bridge picks the right method, semantic retrieval, exact search, source reading or agent exploration, and returns compact evidence with file and line references.
Does it work on macOS?
No, only Windows is supported. The author did no acceptance for macOS or Linux and states it in the warning at the top of the README.
Is a separate subscription needed?
No, the bridge does not touch the Cursor subscription: models, quotas and bring-your-own-key options stay whatever your signed-in Cursor already has.
Discussion
No questions or reviews yet.
Related
PluginsCodex Bridge sends questions and file analysis from Claude Code, Cursor and VS Code to the official Codex CLI via Python MCP.
A Codex skill hands planning and review to ChatGPT over a local MCP bridge and keeps execution and checks in Codex
Codex MCP Tool (cexll)
Codex MCP Tool
An MCP server that sends tasks to Codex CLI from Claude Code and Cursor: code review via @ refs, a sandbox, patch edits, ideas
The Claude Code plugin delegates reviews, investigations and edits to Grok Build while tracking runs and saved results.
An MCP server on your machine that lets ChatGPT and Claude edit code, run tests and check Git in a local repository
Gives the agent an understanding of your repository: it indexes the code and answers questions about it in Claude Code, Cursor, Codex, Windsurf and more
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Cursor Bridge (this card) | no | 83 | |
| Grok Build bridge for Claude Code | no | 279 | a Claude Code plugin that delegates review, investigation and edits to Grok Build without using the Cursor index |
| Grok Build | yes | 27,757 | the xAI terminal agent itself, which reads Claude Code skills and MCP servers |
README in short
The page explains two plugins that install separately and opens with a warning that only Windows is supported. A quick start per client for Codex, Claude Code, Grok Build and Pi, a section on CCE, compatibility and update history, the CCE source choice, the MCP tool list and a migration from 5.3.6 or earlier follow.