mcp-developer-portal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BACKSTAGE_URL | Yes | Backstage instance URL | |
| BACKSTAGE_TOKEN | No | Backstage API token | |
| PORTAL_INDUSTRY | No | Industry context (fintech/manufacturing) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_catalog_toolC | Search the Backstage service catalog by name, kind, or owner. |
| get_entity_toolC | Get full details for a catalog entity. |
| get_techdocs_toolB | Fetch TechDocs documentation for a catalog entity. |
| get_ownership_toolC | Look up who owns a service or component. |
| get_dependencies_toolB | Get upstream and downstream dependencies for a service. |
| list_templates_toolA | List available golden-path scaffolding templates. |
| scaffold_service_toolC | Scaffold a new service from a golden-path template. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a uniquely defined purpose: dependencies, entity details, ownership, techdocs, templates, scaffolding, and catalog search. No two tools overlap in functionality.
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.
Seven tools is a well-scoped set for a developer portal. They cover key operations without being excessive or insufficient for the intended domain.
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.