Backstage is an open-source developer portal platform created by Spotify that helps organizations build and manage their internal developer platforms, providing tools for service catalog, documentation, and more.
Provides comprehensive knowledge and tools for Backstage development including plugin scaffolding, API reference documentation, code examples, and access to community resources for building and customizing Backstage applications.
Provides comprehensive Backstage framework knowledge and development assistance through an MCP server. Enables plugin development, API reference access, code scaffolding, and community resource discovery for Backstage customization.
7
69 npm
2
MIT
Why this server?
Provides tools for querying the service catalog, fetching TechDocs, looking up ownership, exploring dependency graphs, and scaffolding new services from golden-path templates via Backstage.
An MCP server that maps any repository into architecture diagrams, providing tools for scanning code facts, building import graphs, and generating Mermaid/DOT diagrams, plus architecture rule enforcement for CI.
5
29 npm
2
MIT
Why this server?
Supports the Backstage ecosystem (including Red Hat Developer Hub plugin development) by discovering plugin packages, analyzing git changes and coverage reports, and recommending/generating test plans and Playwright briefs across unit, integration, component, and e2e layers.
Enables coverage-driven test generation for RHDH plugin forests by analyzing git diffs and coverage reports, recommending the cheapest test layer, and emitting actionable test briefs, including Playwright MCP prompts for UI gaps.
10
Apache 2.0
Why this server?
Connects StackVitals portal, catalog, and ownership information with Backstage.
Gives AI agents one MCP interface to inspect CI health and flaky tests, pull request flow, delivery/DORA metrics, dependency risks, community health, insights, and org portal data across GitHub repositories. It exposes 11 core tools by default and all 35 with --tools all.
Apache 2.0
Why this server?
Backstage plugin for API governance, providing risk scorecards and breaking change detection directly in Backstage.
Signed, offline-verifiable authorization for API-contract changes. Before a contract change (OpenAPI, GraphQL, Protobuf, AsyncAPI, MCP manifests) merges or deploys, the agent calls preflight_change_set; the decision is deterministic, signed, and verifiable without calling CodeRifts. Three tools: preflight_change_set, verify_receipt, get_decision_details. Only a granted change can proceed.
4 npm
MIT
Why this server?
Integrates with Backstage catalogs for service discovery and topology.
Enables AI agents to query Backstage catalog data as a typed graph over MCP, answering blast-radius, ownership and escalation, dependency, path, change-risk, and catalog-drift questions through bounded read-only tools.
Apache 2.0
Why this server?
Provides integration with Backstage by parsing catalog-info.yaml files to build a system map of components, APIs, systems, and users, enabling AI agents to traverse service ownership and dependencies.
MCP server that aggregates documentation and code context across GitHub repositories, auto-generates a system map from Backstage catalog files, and provides search capabilities for docs, code, issues, and API schemas to AI agents.
