How do I configure Backstage for authentication?
Enable static token-based external access in Backstage’s `appConfig` with the token and subject fields provided.
Bee Agent & MCP with Backstage
@evanshortiss
Basic information
About Bee Agent & MCP with Backstage
A sample MCP Server and Agent that uses it to pull data from a Backstage instanace
Bee Agent & MCP with Backstage config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryBee Agent & MCP with Backstage tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Bee Agent & Model Context Protocol with Backstage?
This repository demonstrates how to create a Model Context Protocol (MCP) server that provides tools for LLMs to communicate with a Backstage instance. It includes a sample agent built with the Bee Agent Framework to interact with the MCP server.
How to use Bee Agent & Model Context Protocol with Backstage?
Configure Backstage with static token-based authentication. Then prepare and run the MCP server by navigating to server/, installing dependencies (npm i), copying .env.template to .env, editing with valid values, and starting with npm run build && npm start. In a separate terminal, run the agent by changing to agent/, copying .env.template, installing dependencies, and executing npm run build && npm start.
Key features of Bee Agent & Model Context Protocol with Backstage
- MCP server exposing tools for LLMs to use Backstage APIs.
- Sample agent built with the Bee Agent Framework.
- Integration via static token-based HTTP authentication.
- Runs locally on
http://localhost:8080.
Use cases of Bee Agent & Model Context Protocol with Backstage
- Demonstrating how an LLM agent can interact with Backstage using the MCP protocol.
- Prototyping custom MCP servers for Backstage integration.
- Exploring the Bee Agent Framework with real-world MCP tooling.
Frequently asked questions
What dependencies are required to run the MCP server?
Node.js and npm are needed. Install dependencies with `npm i` in the `server/` directory.
How do I set environment variables?
Copy `.env.template` to `.env` and edit the file with valid values for your Backstage instance.
What transport does the MCP server use?
The server listens on HTTP at `http://localhost:8080` by default.
Can I use the agent without the MCP server?
No; the agent is designed to interact with the MCP server, which must be running first.
More AI & Agents MCP servers
F
fhirHydrant
faulkjOpen-source Node.js FHIR MCP server with SMART Backend Services, metadata-aware search/CRUD tools, compact responses, FHIRPath filtering, safe pagination, audit events, and terminology lookup.
14
Simplepages
SimplepagesBuild and edit landing pages and websites from your AI assistant, and pull how they are performing.
AON — Agent Offer Network
AONAON MCP connects AI agents to real, buyable products and services with live pricing and tracked links—enabling builders to earn developer revenue share from attributed clicks and conversions.
2
TruVerifAI Panel-review
TruVerifAITruVerifAI's Panel Review is the guardian agent for AI's highest-stakes coding decisions: four frontier models argue over an AI coding agent's riskiest designs, diffs, and commits before they execute, with local review g
1
HeyLead: LinkedIn Outreach & Lead Generation MCP Server
D4umakHeyLead: AI agent for LinkedIn outreach. Finds the right people, writes in your voice, follows up and handles replies, from Claude Code, Cursor, any MCP client or a web dashboard.
9
Comments