One Annotation to Rule AI: um-sdk Turns Java Methods into MCP Tools
The project offers a practical template for making existing Java business code AI-callable without learning MCP from scratch, and its lightweight framework gives Western teams a concrete alternative to Spring for memory-constrained deployments. The honest SNAPSHOT and private-repo caveats set expectations that this is a personal toolkit to adapt, not a drop-in enterprise dependency.
um-sdk, published on Gitee under Apache-2.0, collects the repetitive scaffolding every Java project needs into one dependency and adds an AI-native layer. A single @McpTool annotation exposes a business method as a callable tool for Cursor, Claude, or any MCP-compatible client, with Stdio, HTTP, and Embedded transports. The package also includes um-agent, which abstracts five LLM platforms, supports streaming, memory, and multi-model routing to cut costs by sending different task types to cheaper models.
The project is organized around two host stacks. um-spring-starter drops into existing Spring Boot apps without changing architecture, while um-ultra-starter is a zero-framework-dependency IoC/AOP container with millisecond startup and tens of megabytes of memory, designed for edge devices, CLI tools, and Serverless functions. The core modules include um-util (20+ static utility classes), um-enums (internationalized, SPI-provided dynamic enums), um-epay, um-mail, um-mcp, and um-agent. A unified cache module, um-ultra-cache, exposes one interface for memory, Redis, and MongoDB with built-in anti-cache-breakdown logic and an escape hatch to the native client.
The author, a decade-plus Java developer, explicitly lists the downsides: the version is still SNAPSHOT, artifacts live on a private Nexus repository (though the source is open), um-ultra's ecosystem is far smaller than Spring's, the community is tiny, and there is a learning curve for the Plugin SPI extension mechanism. The open code lets teams build locally if they cannot access the private Maven repo.
The annotation-driven MCP layer shifts the burden from protocol plumbing to writing good description fields, which means the quality of AI-integrated Java systems now depends on how well developers write plain-language documentation for their own methods.
Offering both a Spring add-on and a standalone ultralight framework in the same SDK is a smart gamble: it lets teams adopt the AI bridge without committing to a full framework replacement.
A solo developer maintaining a broad toolkit (utilities, enums, payment, mail, cache, MCP, agent) will have difficulty matching the reliability guarantees that teams behind Hutool or Spring provide, regardless of how well the individual modules are designed.
The private Nexus repository is a practical obstacle for Western teams; despite being open source, the default Maven coordinates point to a non-public URL, so adoption requires either access or a self-build step.