Bee Agent & Model Context Protocol with Backstage

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.