Fix loading and tool discovery for non-stdio MCP transports (HTTP/SSE) #11
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.
Summary
Changes Made
Core Fixes
client.NewStreamableHttpClient()for HTTP MCP serversclient.NewStdioMCPClient()for subprocess-based servers{{VAR}}to{{.VAR}}across all example configsNew Examples
Testing Results
✅ Filesystem Server (stdio): 14 tools discovered from
secure-filesystem-server v0.2.0✅ AWS Knowledge Server (HTTP): 3 tools discovered from
AWSDocumentationMCPProdGateway v1.0.0✅ Template Variables: Correctly detected and resolved from
variables.yml✅ Dual Transport: Both stdio and HTTP transports working simultaneously
Test Plan
Files Changed
internal/services/tool_discovery_client.go- Added mcp-go convenience method usageexamples/mcps/*.json- Fixed template syntax in all configsexamples/mcps/aws-knowledge.json- New HTTP server exampleexamples/mcps/variables.example.yml- Added missing variable examples🤖 Generated with Claude Code