UMCP MCP Server

UMCP becomes available to MCP clients through the umcp mcp server. A lightweight framework for building MCP (Model Context Protocol) servers in Java. uMCP provides a simple abstraction layer over the official MCP Java SDK, making it easy to create and deploy MCP servers with TCP transport.

What UMCP does

A lightweight framework for building MCP (Model Context Protocol) servers in Java. uMCP provides a simple abstraction layer over the official MCP Java SDK, making it easy to create and deploy MCP servers with TCP transport.

Key capabilities

• Simple Abstractions — Clean interfaces (SyncCapability, AsyncCapability) for implementing MCP tools
• TCP Transport by Default — Always uses TCP transport via mcp-java-bridge
• Type Safety — Automatic type handling and JSON schema generation
• Builder Pattern — Fluent API for server configuration
• Minimal Dependencies — Lightweight framework built on top of the official SDK
• Claude Desktop Ready — Works seamlessly with Claude Desktop using the bridge connector

Tools it exposes

Once connected, the assistant can call these 3 tools directly:

• Prerequisites — The Prerequisites tool exposed by this server
• Maven — The Maven tool exposed by this server
• Gradle — The Gradle tool exposed by this server

Installing the umcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Requirements

• Java 17 or higher - Gradle 8.5+ (for building from source)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. UMCP sits in that group, and the shape of its toolset — Prerequisites, Maven, Gradle — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Maintained by cobach.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the umcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.