Bee Agent & Model Context Protocol with Backstage
@evanshortiss
About Bee Agent & Model Context Protocol with Backstage
A sample MCP Server and Agent that uses it to pull data from a Backstage instanace
Config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTools
No tools detected
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.
FAQ from Bee Agent & Model Context Protocol with Backstage
How do I configure Backstage for authentication?
Enable static token-based external access in Backstage’s appConfig with the token and subject fields provided.
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.
Frequently asked questions
How do I configure Backstage for authentication?
Enable static token-based external access in Backstage’s `appConfig` with the token and subject fields provided.
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.
Basic information
More AI & Agents MCP servers
Model Context Protocol for Unreal Engine
chongdashuEnable AI assistant clients like Cursor, Windsurf and Claude Desktop to control Unreal Engine through natural language using the Model Context Protocol (MCP).
Open Multi-Agent Canvas
CopilotKitThe open-source multi-agent chat interface that lets you manage multiple agents in one dynamic conversation and add MCP servers for deep research
Perplexity Ask MCP Server
ppl-aiThe official MCP server implementation for the Perplexity API Platform
1Panel
1Panel-dev🔥 1Panel is a modern, open-source VPS control panel — and the only one with native AI agent support. Run Ollama models, deploy OpenClaw agents, and manage your entire server stack from one clean web interface.
Web Agent Protocol
OTA-Tech-AI🌐Web Agent Protocol (WAP) - Record and replay user interactions in the browser with MCP support
Comments