MCP Server SDK Usage
MCP Server SDK Setup
Add this dependency to build MCP servers:
<dependency>
<groupId>com.ajaxjs</groupId>
<artifactId>aj-mcp-server</artifactId>
<version>1.2</version>
</dependency>
We can find the latest version:
The server module includes:
McpServercore processing engineFeatureMgrfor annotation-based feature discovery@Tool,@Resource,@Promptannotations- Transport implementations for HTTP/SSE and Stdio
Creating a Server
To create an MCP server, you need to:
- Define Service Classes: Create classes annotated with
@McpService - Annotate Methods: Use
@Tool,@Prompt, or@Resourceannotations - Initialize Feature Manager: Scan packages for annotations
- Configure Transport: Set up HTTP/SSE or Stdio transport, and some details of server
- Start Server: Call
server.start()
Creating MCP Service Class
AJ-MCP automatically discovers, registers, and manages MCP features (tools, resources, and prompts) through annotation-based scanning.
This system enables developers to expose functionality simply by annotating methods with @Tool, @Resource, or @Prompt annotations within classes
marked with @McpService.
@McpService
public class MyServerFeatures {
@Tool(description = "Echoes a string")
public String echoString(@ToolArg(description = "Input string") String input) {
return input;
}
@Prompt(description = "Basic greeting prompt")
public PromptMessage greeting(@PromptArg(description = "Name") String name) {
PromptMessage message = new PromptMessage();
message.setRole(Role.USER);
message.setContent(new ContentText("Hello " + name));
return message;
}
}
Server Feature Management
Each server uses a FeatureMgr instance to coordinate package scanning, annotation processing, and feature storage. The stores are instance-scoped, so multiple servers in the same JVM do not share tools, resources, or prompts.
Annotation System
The annotation system is built around several key annotations that mark classes and methods for MCP exposure:
| Annotation | Target | Purpose |
|---|---|---|
| @McpService | Class | Marks a class for service discovery |
| @Tool | Method | Exposes a method as an MCP tool |
| @ToolArg | Parameter | Defines tool method parameters |
| @Resource | Method | Exposes a method as an MCP resource |
| @Prompt | Method | Exposes a method as an MCP prompt |
| @PromptArg | Parameter | Defines prompt method parameters |
Calling FeatureMgr.init() scans a package and registers methods from classes annotated with @McpService. A class that cannot be loaded is logged and skipped without aborting the rest of the scan.
Initialize Feature Manager
The FeatureMgr.init() method orchestrates the entire annotation discovery process. It begins by scanning specified packages for classes annotated
with @McpService.
FeatureMgr mgr = new FeatureMgr();
mgr.init("com.foo.myproduct");
Server Configuration
After feature manager initialization with package scanning, we can configure the server with:
- Server instance creation with transport layer setup
- Server configuration with name and version
- The page size for paginated responses
ServerConfig contains the server name, version, supported protocol versions, and page size.
During initialization, the server returns the requested protocol version when it is supported; otherwise, it returns its highest supported version.
FeatureMgr mgr = new FeatureMgr();
mgr.init("com.foo.myproduct");
McpServer server = new McpServer();
server.setFeatureMgr(mgr);
server.setTransport(new ServerStdio(server));
ServerConfig serverConfig = new ServerConfig();
serverConfig.setName("MY_MCP_Server");
serverConfig.setVersion("1.0");
serverConfig.setPageSize(8);
server.setServerConfig(serverConfig);
server.start();