dc4386f0f1Update Kotlin-MCP-Server with STDIO support, logging & CORS ### Summary - Added support for STDIO transport mode (default behavior). - Configured CORS and migrated SSE server to Ktor's Netty engine. - Redirected logs to `./build/stdout.log` and updated log levels. - New `TestEnvironment` setup for integration testing. - Enhanced documentation with examples for server execution and MCP Inspector usage. - Introduced shadow JAR plugin for building runnable artifacts. ### Motivation and Context Improves server versatility and developer experience by enabling STDIO and refining setup. ## How Has This Been Tested? Unit tests, tested locally (see README.md in sample) **NB! sse plain configuration is not working at the moment** ## Breaking Changes No ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. --> - [ ] I have read the [MCP Documentation](https://modelcontextprotocol.io) - [ ] My code follows the repository's style guidelines - [ ] New and existing tests pass locally - [ ] I have added appropriate error handling - [ ] I have added or updated documentation as needed ## Additional context <!-- Add any other context, implementation notes, or design decisions -->
2.9 KiB
2.9 KiB
MCP Kotlin Server Sample
A sample implementation of an MCP (Model Context Protocol) server in Kotlin that demonstrates different server configurations and transport methods.
Features
- Multiple server operation modes:
- Standard I/O server
- SSE (Server-Sent Events) server with plain configuration
- SSE server using Ktor plugin
- Built-in capabilities for:
- Prompts management
- Resources handling
- Tools integration
Getting Started
Running the Server
The server defaults STDIO transport.
You can customize the behavior using command-line arguments. Logs are printed to ./build/stdout.log
Standard I/O mode (STDIO):
./gradlew clean build
Use the MCP inspector to connect to MCP via STDIO (Click the "▶️ Connect" button):
npx @modelcontextprotocol/inspector --config mcp-inspector-config.json --server stdio-server
SSE with plain configuration:
NB!: 🐞 This configuration may not work ATM
./gradlew run --args="--sse-server 3001"
or
./gradlew clean build
java -jar ./build/libs/kotlin-mcp-server-0.1.0-all.jar --sse-server 3001
Use the MCP inspector
to connect to http://localhost:3002/ via SSE Transport (Click the "▶️ Connect" button):
npx @modelcontextprotocol/inspector --config mcp-inspector-config.json --server sse-server
SSE with Ktor plugin:
./gradlew run --args="--sse-server-ktor 3002"
or
./gradlew clean build
java -jar ./build/libs/kotlin-mcp-server-0.1.0-all.jar --sse-server-ktor 3002
Use the MCP inspector
to connect to http://localhost:3002/ via SSE transport (Click the "▶️ Connect" button):
npx @modelcontextprotocol/inspector --config mcp-inspector-config.json --server sse-ktor-server
Server Capabilities
- Prompts: Supports prompt management with list change notifications
- Resources: Includes subscription support and list change notifications
- Tools: Supports tool management with list change notifications
Implementation Details
The server is implemented using:
- Ktor for HTTP server functionality (SSE modes)
- Kotlin coroutines for asynchronous operations
- SSE for real-time communication in web contexts
- Standard I/O for command-line interface and process-based communication
Example Capabilities
The sample server demonstrates:
- Prompt: "Kotlin Developer" - helps develop small Kotlin applications with a configurable project name
- Tool: "kotlin-sdk-tool" - a simple test tool that returns a greeting
- Resource: "Web Search" - a placeholder resource demonstrating resource handling