Skip to content

rename(vnext): local-mcp source dir + glean_plugin server key - #9

Open
steve-calvert-glean wants to merge 1 commit into
mainfrom
steve/rename-local-mcp
Open

rename(vnext): local-mcp source dir + glean_plugin server key#9
steve-calvert-glean wants to merge 1 commit into
mainfrom
steve/rename-local-mcp

Conversation

@steve-calvert-glean

Copy link
Copy Markdown
Contributor

What

Two related naming cleanups to the local MCP server plumbing:

  1. sources/glean-vnextsources/local-mcp. The folder name described where the code came from (a folded-in "glean vnext" plugin, see feat: fold glean-vnext runtime MCP server into the glean plugin #3) rather than what it is: the local stdio MCP server, its glean_run skill, and the auto-approve hook. Every sibling sources/* dir is named by host/purpose (claude, codex, cursor, shared, dev-docs); this one wasn't.

  2. .mcp.json server key glean-localglean_plugin. Snake_case and glean-namespaced, matching the convention used for client-side Glean MCP aliases (e.g. glean_default). This is a different namespace from plugin-mcp, the name Glean's Admin console will use for the managed remote proxy server per the "Dynamic Tools: Decision Log" doc (Decision 4) — those two shouldn't collide, and dropping the glean prefix locally would lose namespacing against other MCP servers a user might have configured.

Details

  • All path/string references updated across pluginpack.config.ts, package.json, the CI shell-script guard (scripts/check-no-shell-scripts.mjs), .gitignore, both workflow files, and docs/skill-reconciliation.md.
  • The auto-approve hook's legacy-key lookup now falls back through glean_pluginglean-localglean, extending the fallback chain it already had (this isn't the first such rename) so a transitional install — only one of the hook or .mcp.json updated so far — doesn't silently stop auto-approving.
  • CHANGELOG.md files (root + per-target) are left untouched; they're historical release records that reference specific past commit SHAs.

Verification

  • npm run check:no-shell, npm run typecheck:bundle, npm run test:bundle (192 tests, including the renamed-key hook tests) all pass.
  • npm test (full build + validate for claude/cursor/codex) passes; confirmed the generated dist/{claude,codex}/plugins/glean/.mcp.json ship the new glean_plugin key.
  • grep -rn "glean-vnext" and grep -rn '"glean-local"' confirm no stray references outside the intentional CHANGELOG history and hook fallback chain.

🤖 Generated with Claude Code

sources/glean-vnext -> sources/local-mcp: the folder name described where
the code came from (a folded-in "glean vnext" plugin), not what it is (the
local stdio MCP server, its glean_run skill, and the auto-approve hook).
Every sibling sources/* dir is named by host/purpose; this one wasn't.

.mcp.json server key "glean-local" -> "glean_plugin": snake_case and
glean-namespaced to match the convention used for client-side Glean MCP
aliases (e.g. glean_default), distinct from the "plugin-mcp" name Glean's
Admin console will use for the managed remote proxy server per the Dynamic
Tools decision log (Decision 4) - those are two different namespaces and
shouldn't collide. The auto-approve hook's legacy-key lookup now falls back
through glean_plugin -> glean-local -> glean so a transitional install
(only one of hook/.mcp.json updated yet) doesn't stop auto-approving.

Updated every path/string reference across config, CI workflows, the CI
shell-script guard, and docs/skill-reconciliation.md. CHANGELOG.md files are
left untouched as historical release records.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant