Internal MCP Server #38
Merged
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 pull request introduces an internal MCP server using Helix and updates the main package imports to expose MCP server functionality. The primary focus is on providing users with a clear starting point for utilizing the MCP server, including configuration options and different execution modes.
Package update:
helix/mcp.pyto implement an internal MCP server for Helix MCP Endpoints.helix/__init__.pyto import and exposeMCPServerand `ToolConfig.New MCP server example:
examples/mcp_server.pythat demonstrates how to set up and run an MCP server using the Helix client, including disabling specific tools and providing options for synchronous, background, and asynchronous execution.