MCP Service Broker

MCP Service Broker

By dbbaskette GitHub

Spring Cloud OSB Implementation of an Open Service Broker for MCP Servers

mcp-service-broker spring-cloud
Overview

What is MCP Service Broker?

MCP Service Broker is a Spring Cloud Open Service Broker that allows for the registration and binding of Model Context Protocol (MCP) servers, supporting various profiles including Cloud Foundry, local, and Kubernetes.

How to use MCP Service Broker?

To use MCP Service Broker, you can run it locally using Maven, bind a Postgres service in Cloud Foundry, or utilize the REST API for managing MCP servers.

Key features of MCP Service Broker?

  • Register MCP servers via Cloud Foundry Service Broker API or REST API
  • Bind MCP servers to applications with credentials provided at bind time
  • REST API for graphical management
  • React UI for catalog and registration
  • Profile-based persistence options: in-memory, Postgres
  • Actuator endpoints for health and information monitoring

Use cases of MCP Service Broker?

  1. Registering and managing MCP servers in a Cloud Foundry environment.
  2. Binding MCP servers to applications for seamless integration.
  3. Utilizing the REST API for automated server management.

FAQ from MCP Service Broker?

  • Can I use MCP Service Broker with Kubernetes?

Yes! MCP Service Broker supports Kubernetes profiles for local development.

  • How do I start the React UI?

You can start the React UI by navigating to the frontend/ directory and following the instructions in the README.

  • What are the actuator endpoints?

The actuator endpoints include /actuator/health for health status and /actuator/info for application information.

Content

MCP Service Broker

A Spring Cloud Open Service Broker for registering and binding Model Context Protocol (MCP) servers. Supports Cloud Foundry, local, and Kubernetes profiles.

Features

  • Register MCP servers via Cloud Foundry Service Broker API or REST API
  • Bind MCP servers to apps (credentials provided at bind time)
  • REST API for graphical management
  • React UI for catalog and registration (see frontend/)
  • Profile-based persistence: in-memory (local/k8s), Postgres (Cloud Foundry)
  • Actuator endpoints for health/info

Quick Start

Local Development

./mvnw spring-boot:run -Dspring-boot.run.profiles=local

Cloud Foundry

Bind a Postgres service and push with cloudfoundry profile. Datasource auto-configured from VCAP_SERVICES.

REST API

  • GET /api/mcp-servers - List all MCP servers
  • POST /api/mcp-servers - Register new MCP server (JSON body)
  • DELETE /api/mcp-servers/{instanceId} - Delete MCP server

UI

  • Start the React UI in frontend/ (see frontend README)

Profiles

  • local: In-memory repo
  • cloudfoundry: Postgres via JPA (VCAP_SERVICES)
  • kubernetes: In-memory repo

Spring Boot Actuator Endpoints

The following actuator endpoints are enabled by default:

  • /actuator/health — Returns application health status (useful for Cloud Foundry, Kubernetes, and monitoring tools).
  • /actuator/info — Returns application info (can be customized in application properties).

You can access these endpoints at:

To expose more actuator endpoints, update management.endpoints.web.exposure.include in your properties files.

License

MIT

No tools information available.
MCP Service Broker
MCP Service Broker by dbbaskette

Spring Cloud OSB Implementation of an Open Service Broker for MCP Servers

mcp-service-broker spring-cloud
View Details