Retrieve schema from uplink #35
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
# Conflicts: # Cargo.lock # Cargo.toml # crates/mcp-apollo-server/Cargo.toml # crates/mcp-apollo-server/src/explorer.rs
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.
Significant rewrite of the server to support loading the supergraph schema from Uplink. Supports hot reloading the schema. A local schema file can also be used, and also supports hot reloading as the file changes.
Important Note - with this change, the MCP server requires the supergraph schema SDL, similarly to Apollo Router. It will no longer work with an API or subgraph schema. To use with a local schema file, this can be composed locally (with
rover supergraph compose) or downloaded from GraphOS (withrover graph fetch). The weather example has been updated with asupergraph.graphqlfile.Changes:
mcp-server-registry. This code is borrowed directly from router, and should be shared long-term.explorertool - this was using the wrong method to generate the URL, and needed more validation to prevent the AI model sending incorrect input.