feat: Add MCP server inference (ie, lazy mcp server connections) #4
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
damassi
force-pushed
the
feat/mcp-inference
branch
from
c7e44ac to
1ff499b
Compare
damassi
force-pushed
the
feat/mcp-inference
branch
from
1ff499b to
812b893
Compare
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.
Similar to the TypeScript version, this adds MCP server inference into the loop, togglable via
mcp_server_inference: falsein theagent-chat-cli.config.yamlfile. If on, it will only connect mcp servers the user is asking about, which ultimately speeds things and adds a bit of fault tolerance, since the claude agent doesn't have to potentially boot many servers (and connect to many OAuth servers, each with their own browser interaction) on boot. This happens lazily, on demand.