Bring LSP diagnostics up and out to an MCP server consumable by any MCP client #76
+1,564
−16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was mostly slopped together so I could get lsp diagnostics in other MCP Clients while I wait for this to mature a bit more. Happy to change anything if desired. The MD is pretty slop, I can clean that up before merge for sure. I was planning on adding more tools to the MCP-exposed server as they become available to the LSP portion. I kept the .opencode.json format so that the server can use the same config files as the primary tool regardless of where it's called from.
Love the work you've put into this thus far! Thanks!