MCP: federate documented internal components

[adierkens]

Closes #

Final React PR (5/5) in the #8217 -> #8227 -> #8228 -> #8229 -> this PR stack. This PR targets adierkens-recommend-primer-components (#8229).

Depends on the docs-generated catalog endpoint in https://github.com/github/primer-docs/pull/1191.

Changelog

New

• Add list_internal_components for documented, GitHub-only Primer-internal catalog entries.

Changed

• Add opt-in sourceScope: "all" recommendations that return documented internal candidates separately from installable public components.

Removed

• None.

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; if selected, include a brief description as to why

Testing & Reviewing

The safe default is sourceScope: "public": get_component remains exclusively for installable public @primer/react components. sourceScope: "all" adds a separate, bounded, non-installable internalComponents collection with visibility and availability labels. The catalog is docs-generated, revisioned, bounded, and explicitly reports unavailable, stale, and no-match states without a private fallback.

• npx --yes -p node@26.4.0 node node_modules/vitest/vitest.mjs --run packages/mcp/src
• npm run type-check -w @primer/mcp
• npm run build -w @primer/mcp
• npm run lint
• npm run lint:css
• npm run format:diff
• npm run build

Review the public/private boundary, the separate internal candidate collection, and the docs endpoint dependency. No private implementation, Storybook bodies, or github-ui source is exposed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 348f97a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@primer/mcp	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

⚠️ Action required

👋 Hi, this pull request contains changes to the source code that github/github-ui depends on. If you are GitHub staff, test these changes with github/github-ui using the integration workflow. Check the integration testing docs for step-by-step instructions. Or, apply the integration-tests: skipped manually label to skip these checks.