feat: register the lerd MCP server with OpenCode - #1547
Open
geodro wants to merge 1 commit into
Open
Conversation
OpenCode is the one client so far that shares neither of the two JSON shapes lerd already writes. Its entry lives under an mcp key rather than mcpServers or servers, names the transport local rather than stdio, folds the command and its arguments into a single array, and expects the entry to say it is enabled. That is a new format rather than another row in the table, so lerdJSONEntry now takes the client it is building for instead of a bare needsType flag. Everything else was already general enough to carry it. mergeServerJSON and removeServerJSON key off the client's own ServerKey, so the merge, the removal and the has-lerd check needed nothing. It reads AGENTS.md from the project root, which the codex entry already writes, so the only context file it claims for itself is the copy under its own config directory. Same reasoning the antigravity entry uses for GEMINI.md. Closes #1542
|
Thank you for adding this! |
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
2 participants
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.
OpenCode is the one client so far that shares neither of the two JSON shapes lerd already writes. Its entry lives under an mcp key rather than mcpServers or servers, names the transport local rather than stdio, folds the command and its arguments into a single array, and expects the entry to say it is enabled. That made it a new format rather than another row in the table, so lerdJSONEntry now takes the client it is building for instead of a bare needsType flag.
Everything else was already general enough to carry it. mergeServerJSON and removeServerJSON key off the client's own ServerKey, so the merge, the removal and the has-lerd check needed no changes at all.
OpenCode reads AGENTS.md from the project root, which the codex entry already writes, so the only context file it claims for itself is the copy under its own config directory. That is the same reasoning the antigravity entry uses for GEMINI.md.
Registered at opencode.json in the project root and ~/.config/opencode/opencode.json globally, both taken from OpenCode's own documentation rather than inferred.
Closes #1542