Model Context Protocol on Coderrob

Improving the Backstage MCP Server with MCP Kernel

Sat, 19 Sep 2026 10:00:00 -0500

An MCP server for Backstage needs to preserve the meaning of a Catalog operation all the way from the tool call to the backend. A valid JSON response is only useful if the server asked the right question.

I’ve been updating my Backstage MCP Server around that requirement: improve the Catalog integration, make the runtime boundaries explicit, and verify the process an MCP client actually launches.

If you are new to the project, start with Introducing the Backstage MCP Server for what it does, example Catalog lookups, and client setup.

Creating and Publishing MCP Kernel

Fri, 18 Sep 2026 10:00:00 -0500

An MCP server needs more than a collection of tool handlers. Once you add service clients, shared context, authorization rules, and cleanup, you have an application to maintain.

I created and published MCP Kernel to handle that repeated application code. It gives TypeScript MCP servers reusable plugins, typed context, shared request policies, and lifecycle management so you can spend more time building the tools your application needs.

You can find it on GitHub and npm.

Introducing the Backstage MCP Server

Thu, 17 Sep 2026 10:00:00 -0500

If your team uses Backstage, your software catalog already contains information an AI assistant needs: service names, owners, APIs, and relationships between components. Giving the assistant access to that information can save you from copying catalog entries into a conversation every time you ask about a service.

I built Backstage MCP Server to connect an MCP-compatible assistant to the Backstage Software Catalog. It exposes tools for looking up entities, inspecting relationships, validating descriptors, and making authorized catalog changes.