Repository navigation
catalog: Consolidate Power BI MCP on the registry entry - #77
Merged
Merged
Conversation
Remove the duplicate contributor entry and copied descriptor so Power BI uses the supported registry-reference resolver and retains automatic version refreshes. Add regression coverage for a single entry across registry version updates and document the supported reference policy. Regenerate the catalog from the live GitHub MCP Registry, including its current timestamp, repository-statistic, and Context7 version updates. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🟢 Approval recommended
The consolidation is consistent across sources, generated output, documentation, and regression coverage.
0 open findings
What changed in this PR
Consolidates Power BI MCP discovery on the registry-managed entry, preserving automatic upstream version refreshes.
Changes:
- Removes the duplicate local entry and descriptor.
- Adds regression coverage for registry version updates.
- Documents supported MCP references and metadata usage.
| File | Description |
|---|---|
tests/test_generate_ai_catalog.py |
Tests single registry-backed Power BI generation. |
descriptors/microsoft/powerbi-modeling-mcp.json |
Removes the copied descriptor. |
catalog/microsoft/powerbi-modeling-mcp.json |
Removes the duplicate source entry. |
CONTRIBUTING.md |
Documents registry-reference guidance. |
ai-catalog.json |
Removes the duplicate and refreshes generated registry data. |
🧠 Review effort: Balanced
💡 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 free
to 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.
Summary
1.0.0to2.0.0.Why this consolidation
The copied descriptor and the registry descriptor both describe
@microsoft/powerbi-modeling-mcp@1.0.0, usingstdioand--start. However, the copied descriptor's raw GitHub URL is not supported by Agent Finder's current catalog MCP-reference resolver.Changing that URL while retaining a second identifier would still leave duplicate resources. Creating a local override of the registry identifier would shadow automatic registry version updates. Removing the duplicate leaves the existing registry import as the single source of truth without changing generator logic.
Retained generated identifier:
Current descriptor URL:
This follows up on #76, which made the copied descriptor URL-backed for ingestion but did not make that URL compatible with reference resolution.
Validation
PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s tests— 28 tests passed.PYTHONDONTWRITEBYTECODE=1 python3 scripts/generate_ai_catalog.py --check— passed.stdiotransport, and--startargument.Generated catalog refresh
This branch is based on
mainafter #63 merged. The normal generator observed further live-registry changes while this work was in progress: refreshed timestamps, repository star counts, and Context7 moving from4.3.0to4.4.1. Those generated-only updates are included; no unrelated contributor entries or generator rules were changed.After merge
The merged catalog still needs normal ingestion, successful enrichment with qualifying trust, and search projection. No production data was changed and no ingestion, enrichment, or reconciliation jobs were triggered as part of this PR.