Skip to main content
Glama
mcp-developer-portal

mcp-developer-portal

by brianpelow

mcp-developer-portal

MCP server wrapping Backstage — query service catalog, fetch TechDocs, and scaffold services via AI agents.

CI License Python MCP

Overview

mcp-developer-portal is a Model Context Protocol server that exposes your Backstage internal developer portal to AI agents. It enables LLMs to query the service catalog, fetch TechDocs documentation, look up ownership, explore dependency graphs, and scaffold new services from golden-path templates.

Built for platform engineering teams in regulated financial services and manufacturing who use Backstage as their engineering system of record.

Related MCP server: jt-mcp-server

Tools exposed

Tool

Description

search_catalog

Search the Backstage catalog by name, kind, or owner

get_entity

Get full details for a catalog entity

get_techdocs

Fetch TechDocs documentation for an entity

get_ownership

Look up who owns a service or component

get_dependencies

Get upstream and downstream dependencies

scaffold_service

Create a new service from a golden-path template

list_templates

List available scaffolding templates

Quick start

pip install mcp-developer-portal

export BACKSTAGE_URL=https://your-backstage.example.com
export BACKSTAGE_TOKEN=your_backstage_token

mcp-developer-portal

Configuration

Variable

Description

Required

BACKSTAGE_URL

Backstage instance URL

Yes

BACKSTAGE_TOKEN

Backstage API token

No

PORTAL_INDUSTRY

Industry context (fintech/manufacturing)

No

Contributing

See CONTRIBUTING.md.

License

Apache 2.0 — see LICENSE.

Available Tools

7 tools
get_dependencies_toolB

Get upstream and downstream dependencies for a service.

Inputs: name (required), kind. Returns: result

get_entity_toolC

Get full details for a catalog entity.

Inputs: name (required), kind, namespace. Returns: result

get_ownership_toolC

Look up who owns a service or component.

Inputs: name (required), kind. Returns: result

get_techdocs_toolB

Fetch TechDocs documentation for a catalog entity.

Inputs: name (required), kind, namespace. Returns: result

list_templates_toolA

List available golden-path scaffolding templates.

Inputs: no named parameters. Returns: result

scaffold_service_toolC

Scaffold a new service from a golden-path template.

Inputs: template_name (required), service_name (required), owner (required), description. Returns: result

search_catalog_toolC

Search the Backstage service catalog by name, kind, or owner.

Inputs: query, kind, owner. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a uniquely defined purpose: dependencies, entity details, ownership, techdocs, templates, scaffolding, and catalog search. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., get_dependencies_tool, list_templates_tool, scaffold_service_tool), with verbs like get, list, search, and scaffold clearly indicating the action.

    Tool Count5/5

    Seven tools is a well-scoped set for a developer portal. They cover key operations without being excessive or insufficient for the intended domain.

    Completeness4/5

    The tool surface covers essential read operations (get, list, search) and a key write operation (scaffold). Minor gaps exist, such as missing create/update for entities beyond scaffolding, but the core developer portal workflow is well-supported.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers