MCP Service Broker

An MCP service broker based on Spring Cloud Open Service Broker, supporting the registration and binding of MCP servers in Cloud Foundry, local, and Kubernetes environments, and providing REST API and React UI management interfaces.

Cloud platform Developer tools #Service broker #MCP protocol #Cloud native #Microservices .Java

rating : 2 points

downloads : 8

update time : 2025-04-28

What is MCP Service Broker?

MCP Service Broker is a Spring Cloud-based service broker specifically designed for registering and managing Model Context Protocol (MCP) servers. It provides a unified way to connect and use MCP servers, supporting multiple deployment environments including Cloud Foundry, local development, and Kubernetes.

How to use MCP Service Broker?

You can register MCP servers through the REST API or the Cloud Foundry service broker API, and connect the MCP servers to your application through a simple binding operation. The system provides both graphical interface and command-line operation methods.

Applicable scenarios

Suitable for scenarios where MCP servers need to be managed and used in different environments, especially in multi-cloud environments or hybrid cloud deployments. Typical use cases include AI model services, context-aware applications, and distributed computing.

Main features

Multi-platform supportSupports three environments: Cloud Foundry, local development, and Kubernetes, meeting different deployment requirements.

REST API managementProvides a complete REST API interface, supporting registration, query, and deletion operations of MCP servers.

Graphical management interfaceComes with a built-in React front-end interface, providing an intuitive MCP server management experience.

Flexible storage solutionAutomatically selects the storage solution based on the environment, using in-memory storage locally and PostgreSQL in Cloud Foundry.

Monitoring endpointsComes with built-in Spring Boot Actuator endpoints, providing health check and information query functions.

Advantages and limitations

Advantages

Simplify the management and usage process of MCP servers

Support multiple deployment environments, with strong adaptability

Provide both graphical interface and API operation methods

Automatically configure data sources, reducing manual configuration work

Limitations

Data is not persistent in local development mode

Basic technical knowledge is required for initial configuration

Currently only in-memory storage is supported in Kubernetes mode

How to use

Start the service

Select an appropriate startup method based on your environment. Use the 'local' configuration file for local development and the 'cloudfoundry' configuration file for Cloud Foundry.

Register your MCP server through the REST API or the front-end interface. You need to provide the server address and necessary authentication information.

Bind to an application

Bind the MCP server to your application. After binding, connection credentials will be automatically provided.

Use monitoring endpoints

Check the service status and get information through the Actuator endpoints.

Usage examples

Use in a Cloud Foundry environmentDeploy MCP Service Broker on the Cloud Foundry platform and connect to the PostgreSQL service for data persistence.

Local development testingQuickly test MCP server connections in a local development environment, using in-memory storage for rapid iteration.

Frequently Asked Questions

How to choose the correct configuration file?

How is the data stored?

How to access the front-end UI?

How to extend Actuator endpoints?

Related resources

Spring Cloud Open Service Broker documentation

Official documentation to understand the implementation principle of the service broker

React front-end code repository

Source code of the front-end UI

MCP protocol specification

Official specification of the Model Context Protocol

🚀 MCP Service Broker

A platform based on Spring Cloud Open Service Broker for registering and binding Model Context Protocol (MCP) servers. It supports Cloud Foundry, local, and Kubernetes environments.

✨ Features

Register MCP servers via the Cloud Foundry Service Broker API or REST API.
Bind MCP servers to applications (providing credentials upon binding).
Offer a REST API for graphical management.
Provide a React-based UI for catalog browsing and registration (see the frontend/ folder).
Use persistent configuration files: in-memory (local/Kubernetes) and Postgres (Cloud Foundry).
Enable actuator endpoints for health status and information monitoring.

🚀 Quick Start

Local Development

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

Cloud Foundry Environment

Bind a Postgres service and deploy using the cloudfoundry profile. The data source is automatically configured from VCAP_SERVICES.

REST API Usage

GET /api/mcp-servers — List all MCP servers.
POST /api/mcp-servers — Register a new MCP server (requires a JSON-formatted request body).
DELETE /api/mcp-servers/{instanceId} — Delete the MCP server with the specified ID.

User Interface

Start the React-based UI in the frontend/ folder (see the frontend README).

📚 Documentation

Configuration Profiles

local: Use in-memory storage.
cloudfoundry: Connect to a Postgres database via JPA (automatically configured from VCAP_SERVICES).
kubernetes: Use in-memory storage.

Spring Boot Actuator Endpoints

The following actuator endpoints are enabled by default:

/actuator/health — Return the application's health status (suitable for Cloud Foundry, Kubernetes, and monitoring tools).
/actuator/info — Return the application's information (can be customized in the application properties file).

Access these endpoints as follows:

Local: http://localhost:8081/actuator/health and http://localhost:8081/actuator/info
Cloud Foundry: https://.cfapps.io/actuator/health and /actuator/info
Kubernetes: http://:8080/actuator/health and /actuator/info

To expose more actuator endpoints, modify the management.endpoints.web.exposure.include configuration in the properties file.