Backstage MCP

Created By
iocanela year ago
A simple backstage mcp server using quarkus-backstage
Overview

what is Backstage MCP?

Backstage MCP is a simple server implementation that integrates Backstage with MCP using Quarkus, allowing users to manage and instantiate Backstage templates.

how to use Backstage MCP?

To use Backstage MCP, set up a Backstage installation with service-to-service communication enabled, and configure the necessary tokens. You can then interact with the server via command line to list and instantiate templates.

key features of Backstage MCP?

  • Lists available Backstage templates
  • Instantiates templates from the command line
  • Integrates with local AI agents like Goose

use cases of Backstage MCP?

  1. Managing Backstage templates for project setups
  2. Automating project creation using predefined templates
  3. Enhancing developer productivity with template instantiation

FAQ from Backstage MCP?

  • What is required to run Backstage MCP?

A Backstage installation with service-to-service communication enabled is required.

  • Can I use Backstage MCP without Goose?

Yes, but Goose enhances the functionality by allowing interactive shell commands.

  • How do I list available templates?

Use the command 'list all the available backstage templates' in the Goose shell.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
iocanel
Star
1
Language
Java
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago