-
Notifications
You must be signed in to change notification settings - Fork 208
Add Experimental MCP Support #3396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
How to use the Graphite Merge QueueAdd the label graphite-merge to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
ec7daf7
to
9a95003
Compare
Signed-off-by: Stan Lo <[email protected]>
e8bc04b
to
68f6997
Compare
We decided not to continue with this approach because we identified a few challenges:
And so far we don't see a solution that can overcome all the challenges while providing a easy, robust experience to users. It also won't work for non-editor clients like Claude Code. So after some discussions, we decided that it's not worth continuing the type of integration with LLMs. That said, an alternative could be to use VS Code's LLM tooling API that directly requests information through Ruby LSP's custom server requests. It'll be a much simpler solution but will only work for VS Code (until Cursor supports the same APIs). |
I've tried this with ruby-lsp but it seems fails. |
Add Model Context Protocol (MCP) support to Ruby LSP
This PR adds support for the Model Context Protocol (MCP), enabling AI assistants to programmatically access Ruby project indexes and file contents that Ruby LSP already collects.
Connection Mechanism
The implementation uses a hybrid approach:
ruby-mcp-bridge
) connects the editor's MCP client to our HTTP serverArchitecture Diagram
Editor Setup
VS Code Configuration
Add to
.vscode/mcp.json
:See VS Code MCP documentation for more details.
Cursor Configuration
Add to
.cursor/mcp.json
:See Cursor MCP documentation for more details.
Notes For Manual Testing
This feature requires both the extension and server changes to work. So for testing:
gem "ruby-lsp", github: "Shopify/ruby-lsp", branch: "mcp"
Known Issues
gets
in the LSP communication channel. This issue may be specific to Cursor as it doesn't occur (or occurs much less frequently) in VS Code, and more often in certain projects (e.g.ruby/irb
) than others. The cause may be related to how Cursor handles MCP/LSP requests and requires more investigation.Supported Tools (TBD)
The MCP server provides four tools:
read_ruby_files - Access file contents, including from dependenciesThese tools enable AI assistants to understand Ruby code structure, navigate dependencies, and access relevant documentation that are not accessible through the editor's simple codebase indexing.