[MCP] Add effective server name header to MDM config#91
Open
rwjblue-glean wants to merge 1 commit into
Open
Conversation
Member
Author
|
CI should be fixed by #92 |
rwjblue-glean
force-pushed
the
rwjblue/mcp-mdm-effective-server-name-header
branch
from
17f7b13 to
ff495d5
Compare
david-hamilton-glean
approved these changes
Jul 2, 2026
Member
Author
|
discussed today; going to refactor this to leverage the existing metadata fields |
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
2 participants
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.
BLUF: MDM-generated MCP configs now carry Cursor's effective server-name header.
This updates
mcp-config.jsongeneration to includeX-Glean-MCP-Server-Name: extension-${serverName}alongside the existing MDM metadata header, preserves optional per-server headers in the config schema, and passes those headers through when configuring supported MCP host tools. This pairs with the server-side consumer of the header, askscio/scio#254253 (client-aware tool-name length budgets), part of the PACT-299 re-land. (It originally referenced #251984/#251985, which were reverted and re-landed as that stack.)Validation:
bunx vitest run src/config.spec.ts src/config-writer.spec.ts src/hosts/index.spec.tsbunx vitest runbunx tsc --noEmit./build.sh