Backstage MCP
by iocanel
This is an example of using Backstage with MCP via Quarkus Backstage. It allows listing available Backstage templates and instantiating them from the command line.
Last updated: N/A
What is Backstage MCP?
Backstage MCP is an example server that integrates Backstage with MCP (Machine Controller Protocol) using Quarkus Backstage. It provides a command-line interface for interacting with Backstage templates.
How to use Backstage MCP?
The server requires a Backstage installation with Service to Service communication enabled. It can be integrated with local AI agents like Goose by configuring the agent to use the server. Templates can be listed and instantiated using specific commands within the agent's shell, utilizing a values.yaml file for template parameters.
Key features of Backstage MCP
List available Backstage templates
Instantiate templates from the command line
Integration with Goose AI agent
Uses Quarkus Backstage for Backstage API interaction
Use cases of Backstage MCP
Automating Backstage template instantiation
Integrating Backstage with AI agents for simplified project creation
Creating projects from templates using command-line tools
Streamlining the process of setting up new projects based on Backstage templates
FAQ from Backstage MCP
What is Backstage?
What is Backstage?
Backstage is an open-source developer portal platform.
What is MCP?
What is MCP?
MCP stands for Machine Controller Protocol.
What is Quarkus Backstage?
What is Quarkus Backstage?
Quarkus Backstage is a Quarkus extension for building Backstage applications.
What is Goose?
What is Goose?
Goose is a local AI agent that runs as an interactive shell and supports plugins (including mcp servers).
How do I get default values for a template?
How do I get default values for a template?
Use the backstage CLI: quarkus backstage template info --show-default-values <template name>