feat: create mcp infrastructure#1763
Draft
jonmorehouse wants to merge 1 commit into
Draft
Conversation
|
This PR was marked as stale, and will be closed after 3 more days. Add the #keep-open label to prevent this from being closed. |
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
1 participant
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 PR creates the basic MCP infrastructure for Nuon's API based MCP.
The premise here is that we enable tool handlers alongside each part of the application, such as an api handler and this
allows us to create custom experiences for interacting with the system via MCP.
@im-Amitto, I know you had some work in here. My thinking is that we should consolidate your cli based MCP into this,
and then have the nuon cli's stdio mcp just proxy to the api, using local credentials. What do you think?