Uh oh!
There was an error while loading. Please reload this page.
Group related MCP integrations by family - #1702
Open
altaywtf wants to merge 2 commits into
Open
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds first-class “family” metadata for MCP integrations so the integrations catalog can group multiple related MCP services under a single provider family card (beyond the previously hard-coded Google/Microsoft grouping).
Changes:
- Removed the hard-coded multi-service family allowlist and now treat any non-empty
integration.familyas eligible for grouping (only grouping when a family has >1 integration). - Extended MCP server registration/config schemas and plumbing to carry an optional
familythrough to persisted config and catalog display metadata. - Added focused unit tests and an e2e scenario verifying two related MCP services collapse into a single family group in the UI.
Reviewed changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| packages/react/src/lib/integration-grouping.ts | Generalizes grouping to any declared family (no hard-coded allowlist). |
| packages/react/src/lib/integration-grouping.test.ts | Adds coverage for grouping arbitrary families and clarifies an existing test name. |
| packages/plugins/mcp/src/sdk/types.ts | Adds optional family to MCP integration config schemas. |
| packages/plugins/mcp/src/sdk/plugin.ts | Plumbs family from MCP server input → stored config → catalog display descriptor. |
| packages/plugins/mcp/src/sdk/plugin.test.ts | Verifies MCP family is projected into the integration catalog response. |
| packages/plugins/mcp/src/sdk/describe-auth-methods.test.ts | Verifies display metadata includes family for remote and stdio configs when present. |
| packages/plugins/mcp/src/api/handlers.ts | Passes optional family through API payload → MCP server input. |
| packages/plugins/mcp/src/api/group.ts | Extends add-server HTTP payload schemas with optional family. |
| e2e/scenarios/integration-families.test.ts | Browser scenario proving two MCP services with the same family collapse into one card. |
| .changeset/mcp-integration-families.md | Publishes the MCP plugin change as a patch release note. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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 freeto 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.
Only Google and Microsoft integrations could collapse into provider groups, and MCP integrations had no way to declare a family. Multi-service providers therefore stayed as unrelated flat rows.