Spring MCP Bridge

@brunosantoslab

Basic information

About Spring MCP Bridge

Spring MCP Bridge config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "spring-mcp-bridge": {
      "command": "python",
      "args": [
        "spring_boot_mcp_converter.py",
        "--project",
        "/path/to/spring-project",
        "--output",
        "./mcp_server",
        "--name",
        "MyAPI"
      ]
    }
  }
}

Spring MCP Bridge tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

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

Overview

What is Spring MCP Bridge?

Spring MCP Bridge is a tool that automatically converts REST endpoints from Spring Boot applications into an MCP (Message Conversation Protocol) server, allowing AI assistants like Claude, Cursor, and other MCP-compatible tools to directly interact with your APIs. It is designed for developers who want to integrate existing Spring Boot APIs with AI assistants without manual coding.

How to use Spring MCP Bridge?

Clone the repository, then scan your Spring Boot project using python spring_boot_mcp_converter.py --project /path/to/spring-project --output ./mcp_server --name MyAPI. Run the generated MCP server with cd mcp_server && pip install -r requirements.txt && python main.py, and configure your MCP client to use http://localhost:8000.

Key features of Spring MCP Bridge

Automatic scanning of all REST endpoints.
Zero configuration – no modifications to existing Spring boot code.
Preserves request/response models as MCP tools.
Extracts Javadoc to enhance tool descriptions.
Generates complete README and usage instructions.

Use cases of Spring MCP Bridge

Letting Claude, Cursor, or other MCP clients query and mutate your Spring Boot APIs.
Rapidly exposing existing RESTful services to AI agents without custom integration code.
Exploring and testing Spring Boot APIs through natural language conversations.

Frequently asked questions

Does Spring MCP Bridge include authentication?

No, it does not currently include authentication. If your Spring Boot API requires authentication, you need to modify the handler code to include the appropriate headers or tokens.

What Spring Boot features are supported?

It supports REST controllers (`@RestController`, `@Controller`), HTTP methods (`@GetMapping`, `@PostMapping`, `@PutMapping`, `@DeleteMapping`, `@PatchMapping`), request parameters (`@RequestParam`), path variables (`@PathVariable`), request bodies (`@RequestBody`), and Java models/DTOs.

How does Spring MCP Bridge work?

It scans Java source code to extract metadata from REST endpoints, converts Java types to JSON Schema types, generates a FastAPI application that maps MCP calls to Spring REST calls, and forwards requests from the MCP client to the Spring Boot application.

What are the runtime requirements for Spring MCP Bridge?

You need Python 3.8+, Spring Boot 3.x, and FastAPI. The generated MCP server runs on HTTP port 8000 and expects the Spring Boot application to be available (default: `http://localhost:8080`). The `SPRING_BASE_URL` can be configured in the generated `main.py`.

Comments

More Developer Tools MCP servers

Modelglass

Modelglass turns "which model should I use?" into a lookup instead of a guess. Seven tools give your agent live pricing across image, language, video, and audio models. Sourced and versioned, not scraped once and forgott

SSH MCP Server

hypnosis

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

FARPY

mangomunchr

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP

LastPing

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

offprompt

MCP server that lets Claude Code, Cursor or Codex ask you for API keys on a local page and write them to .env. The agent only ever sees key names.