Access detailed guides for developing Backstage plugins, covering setup, structure, APIs, testing, and best practices to build custom extensions.
MIT
306,755 tools. Last updated 2026-07-27 04:52
"Backstage" matching MCP tools:
- Retrieve comprehensive Backstage framework overview including core features, benefits, and architecture to understand platform capabilities and implementation.MIT
- Retrieve Backstage API references for REST endpoints, GraphQL, and client libraries to support plugin development and framework customization.MIT
- Access Backstage community resources including support channels, plugins, FAQs, learning materials, adoption stories, and contribution guidelines to enhance your development experience.MIT
- Retrieve code examples and samples for Backstage development scenarios including plugins, catalog, templates, and configuration to accelerate framework customization.MIT
- Search Backstage documentation and resources to find information on specific topics or keywords for development and customization.MIT
Matching MCP Servers
- AlicenseAqualityDmaintenanceProvides 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.Last updated7342MIT
- AlicenseBqualityBmaintenanceMCP server wrapping Backstage — query service catalog, fetch TechDocs, and scaffold services via AI agents.Last updated7Apache 2.0
- Search the Backstage service catalog by name, kind, or owner to find services.Apache 2.0
- Retrieve TechDocs documentation for any entity in the Backstage catalog by providing its name.Apache 2.0
- Generate a plugin scaffold template for Backstage development by specifying plugin type, name, and optional features to accelerate plugin creation.MIT
- Retrieve complete details of a catalog entity by providing its name, kind, and namespace. Accesses Backstage service catalog data through the developer portal.Apache 2.0
- Render a service blueprint as a self-contained HTML page. Supports two modes: (1) classic Shostack single-actor blueprint — user action, frontstage, backstage, support, evidence, pain/delight; (2) two-actor HI-loop blueprint — when `actors` is supplied, renders two swim lanes with a line of interaction between them (e.g. customer ↔ lawyer, patient ↔ doctor, buyer ↔ agent). Each actor gets their own actions, frontstage (what they see), and evidence. Optionally accepts an ideal-state to render side-by-side with the current state.Connector