Backstage MCP Actions Backend
Backstage ships a first-party MCP server as the @backstage/plugin-mcp-actions-backend plugin. It exposes every action registered with the Backstage Actions Registry as an MCP tool over the Streamable HTTP transport, served by the adopter's own Backstage backend at /api/mcp-actions/v1. Because Backstage is self-hosted there is no vendor-operated production endpoint; the Backstage project does, however, run a public demo instance whose MCP endpoint answered an unauthenticated tools/list during this pass, so the tool set below is observed, not inferred.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Descriptor
Candidate descriptor · transport streamable-http
Tools
auth.who-am-i—catalog.get-catalog-model-description—catalog.get-catalog-entity—catalog.validate-entity—catalog.register-entity—catalog.unregister-entity—catalog.query-catalog-entities—catalog.refresh-catalog-entity—scaffolder.list-scaffolder-tasks—scaffolder.dry-run-template—scaffolder.list-scaffolder-actions—scaffolder.execute-template—scaffolder.get-scaffolder-task-logs—
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.