- Notifications
You must be signed in to change notification settings - Fork 46
Releasing 1.1.0 #453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Releasing 1.1.0 #453
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
Sync main → develop (PR #404)
Sync main → develop (PR #397)
Sync main → develop (PR #409)
chore: Only initialize a single HTTP client for graphql requests
Sync main → develop (PR #416)
Sync main → develop (PR #422)
Sync main → develop (PR #420)
Sync main → develop (PR #425)
Sync main → develop (PR #427)
Sync main → develop (PR #431)
Sync main → develop (PR #434)
Sync main → develop (PR #436)
feat: Add configuration option for metric temporality
chore: Rmcp sdk update 0.8.x
…geset chore: Rmcp sdk update 0.8.x changeset
Change default port from 5000 to 8000
Fix compatibility issue with VSCode/Copilot
Add support for forwarding headers from MCP clients to GraphQL APIs
✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 0 new, 9 changed, 0 removedBuild ID: 31f7a60c5c8ac38a460a6d32 URL: https://www.apollographql.com/docs/deploy-preview/31f7a60c5c8ac38a460a6d32 |
docs: add note about port change
DaleSeo approved these changes Oct 21, 2025
| Opened sync PR main → develop: #464 Merge status: clean ✅ |
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.
[1.1.0] - 2025-10-16
❗ BREAKING ❗
Change default port from 5000 to 8000 - @DaleSeo PR #417
The default server port has been changed from
5000to8000to avoid conflicts with common development tools and services that typically use port 5000 (such as macOS AirPlay, Flask development servers, and other local services).Migration: If you were relying on the default port 5000, you can continue using it by explicitly setting the port in your configuration file or command line arguments.
🚀 Features
feat: Add configuration option for metric temporality - @swcollard PR #413
Creates a new configuration option for telemetry to set the Metric temporality to either Cumulative (default) or Delta.
Some observability vendors require that one is used over the other so we want to support the configuration in the MCP Server.
Add support for forwarding headers from MCP clients to GraphQL APIs - @DaleSeo PR #428
Adds opt-in support for dynamic header forwarding, which enables metadata for A/B testing, feature flagging, geo information from CDNs, or internal instrumentation to be sent from MCP clients to downstream GraphQL APIs. It automatically blocks hop-by-hop headers according to the guidelines in RFC 7230, section 6.1, and it only works with the Streamable HTTP transport.
You can configure using the
forward_headerssetting:Please note that this feature is not intended for passing through credentials as documented in the best practices page.
feat: Add mcp-session-id header to HTTP request trace attributes - @swcollard PR #421
Includes the value of the Mcp-Session-Id HTTP header as an attribute of the trace for HTTP requests to the MCP Server
🐛 Fixes
Fix compatibility issue with VSCode/Copilot - @DaleSeo PR #447
This updates Apollo MCP Server’s tool schemas from Draft 2020-12 to Draft‑07 which is more widely supported across different validators. VSCode/Copilot still validate against Draft‑07, so rejects Apollo MCP Server’s tools. Our JSON schemas don’t rely on newer features, so downgrading improves compatibility across MCP clients with no practical impact.
🛠 Maintenance
Update rmcp sdk to version 0.8.x - @swcollard PR #433
Bumping the Rust MCP SDK version used in this server up to 0.8.x
chore: Only initialize a single HTTP client for graphql requests - @swcollard PR #412
Currently the MCP Server spins up a new HTTP client every time it wants to make a request to the downstream graphql endpoint. This change creates a static reqwest client that gets initialized using LazyLock and reused on each graphql request.
This change is based on the suggestion from the reqwest documentation