Skip to content

Epic: MCP Gateway management UI #353

Description

@R-Lawton

Summary

Right now managing MCP Gateways means writing YAML and running kubectl/oc commands. There's no way to see what's registered, test tools, or register new servers without switching between the terminal, YAML files, and external tooling like MCP Inspector.

This epic adds MCP management pages to the Kuadrant Backstage plugin — browse servers, inspect tools and prompts, test tool execution, register new servers through a guided form, and see gateway health at a glance.

This is the Backstage/RHDH equivalent of kuadrant-console-plugin#667. The console plugin targets OpenShift with PatternFly; this targets RHDH with Material UI. Same functionality, different component library. Backstage-specific designs are TBD.

Console plugin designs (PatternFly, for reference): https://www.figma.com/proto/oizjCN6EVed31dW71YXS3K/RHCL-MCP?node-id=137-138949

Architecture

  • Frontend: New pages/routes in plugins/kuadrant
  • Backend: New endpoints in plugins/kuadrant-backend for MCP resource CRUD (MCPGatewayExtension, MCPServerRegistration, Gateway, HTTPRoute, ReferenceGrant)
  • MCP Inspector: Backend proxies MCP protocol calls through the developer-portal-controller's MCP proxy API (design doc). The proxy discovers gateways from MCPGatewayExtension CRs and forwards JSON-RPC requests (initialize, tools/list, tools/call, prompts/list, prompts/get) to the correct gateway endpoint.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttriage/acceptedReviewed, prioritised, and ready for work

    Type

    No type

    Projects

    • Status
      No status

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions