chore(mcp): drop .mcp.json — shared servers moved to user scope - #7
Merged
Conversation
Kit 1.9.0 put four generic MCP servers into every scaffolded project and the P4 fleet pass carried them into 77 repos. That made every future MCP change cost 77 pull requests, and the same names already sat at user scope on different definitions — precedence is local > project > user, so the duplicate never errored, it just resolved by whichever directory you were in. All nineteen servers are declared once at user scope now. Nothing in this repo was unique to it, so the file goes rather than shrinks. Verified before this landed, not after: a bare directory with no `.mcp.json` resolves all nineteen namespaces. `GITHUB_PAT` — referenced by the github server in all 77 repos and defined nowhere on this host — is now derived from the gh CLI, so that server authenticates for the first time. Carrier: project-scaffold 1.11.0 removed `templates/.mcp.json`, so no new project inherits this. Plan: modes/flynn/plans/plan-mcp-centralization.md.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Part of the fleet-wide MCP centralization. This repo's
.mcp.jsonis removed — nothing it declared was unique to it.Why
Kit 1.9.0 put four generic servers —
exa,github,chrome-devtools,playwright— into every scaffolded project, and the P4 fleet pass carried them into 77 repos. Two consequences:cd. The same names already sat at user scope on different definitions (exakeyed vianpxthere, keyless HTTP here). Precedence is local > project > user, so the duplicate never errored — it silently resolved by whichever directory you were in.The rule now: shared tooling is declared once at user scope; a project
.mcp.jsonexists only for servers unique to that project. Measured across all 80 files in the fleet, nothing was unique — even42bros-datais a fixed URL with an env-supplied token.Verified before this landed, not after
.mcp.jsonresolves all nineteen server namespaces.GITHUB_PATwas defined nowhere on this host — so thegithubserver in all 77 repos had been launching with an empty token since the kit shipped it. It is now derived from the gh CLI (gh auth token), which means it authenticates for the first time and rotates withgh authinstead of being a pasted secret.Carrier
project-scaffold1.11.0 removedtemplates/.mcp.json, so no new project inherits this. Full reasoning and phases:tron-modes/modes/flynn/plans/plan-mcp-centralization.md.