Add e2e tests for remote MCP servers #2444
Merged
+368
−0
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.
What
Adds end-to-end tests for remote MCP server functionality to verify
thv runworks correctly with remote servers.Why
We document how to run remote MCP servers in our user guide, but we had no automated tests to verify this functionality actually works. This PR adds comprehensive e2e tests using the
mcp-specremote server from the registry.Changes
test/e2e/remote_mcp_server_test.goTesting
All 9 tests pass locally:
Tests are labeled with
"mcp"and will run in thee2e-tests-core (mcp)CI job.