MCP Service Broker

@dbbaskette

Repository

About MCP Service Broker

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

#mcp-service-broker #spring-cloud #service-broker

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Service Broker?

A Spring Cloud Open Service Broker that registers and binds Model Context Protocol (MCP) servers. It supports Cloud Foundry, local, and Kubernetes profiles for managing MCP server lifecycle.

How to use MCP Service Broker?

Run locally with ./mvnw spring-boot:run -Dspring-boot.run.profiles=local. For Cloud Foundry, bind a Postgres service and push with the cloudfoundry profile. Use the REST API (GET /api/mcp-servers, POST /api/mcp-servers, DELETE /api/mcp-servers/{instanceId}) or the React UI in frontend/.

Key features of MCP Service Broker

Register MCP servers via Cloud Foundry Service Broker API or REST API
Bind MCP servers to apps with credentials at bind time
Profile-based persistence: in‑memory (local/Kubernetes) or Postgres (Cloud Foundry)
React UI for catalog and registration
Spring Boot Actuator endpoints for health and info

Use cases of MCP Service Broker

Register an MCP server for use by a Cloud Foundry application
Manage MCP server registrations via a graphical REST API or React UI
Bind MCP servers to apps in local development or Kubernetes environments
Monitor MCP server health using Actuator endpoints

FAQ from MCP Service Broker

What profiles are available?

Three profiles: local (in‑memory), cloudfoundry (Postgres via JPA), and kubernetes (in‑memory).

How do I run the server locally?

Run ./mvnw spring-boot:run -Dspring-boot.run.profiles=local from the project root.

How is data persisted?

Data is stored in‑memory for local and Kubernetes profiles, and in a Postgres database for the Cloud Foundry profile (auto‑configured from VCAP_SERVICES).

What endpoints are exposed?

REST API endpoints under /api/mcp-servers and Actuator endpoints /actuator/health and /actuator/info are enabled by default.

Is there a user interface?

Yes, a React UI is provided in the frontend/ directory (see its own README for setup).

Frequently asked questions

What profiles are available?

Three profiles: `local` (in‑memory), `cloudfoundry` (Postgres via JPA), and `kubernetes` (in‑memory).

How do I run the server locally?

Run `./mvnw spring-boot:run -Dspring-boot.run.profiles=local` from the project root.

How is data persisted?

Data is stored in‑memory for local and Kubernetes profiles, and in a Postgres database for the Cloud Foundry profile (auto‑configured from VCAP_SERVICES).