| Filename | Latest commit message | Latest commit date |
|---|---|---|
b1ba0cd371<!-- Provide a brief summary of your changes --> Replace the CIO dependency with only server/client core dependency. ## Motivation and Context <!-- Why is this change needed? What problem does it solve? --> In order to minimize the size of package. There are probably other existing engines like Netty/Tomcat(server) or Java/OkHttp/Apache(client) in the classpath. So we can reuse existing infrastructure. ## How Has This Been Tested? <!-- Have you tested this in a real application? Which scenarios were tested? --> I have run: - kotlin-sdk-client: jvmTest, jsTest - kotlin-sdk-test: jvmTest, jsTest - kotlin-sdk-server: allTests - All `build` of samples I have an issue about `samples/kotlin-mcp-server`. `io.modelcontextprotocol` is not found in `commonMain`. ## Breaking Changes <!-- Will users need to update their code or configurations? --> Yes. They need to `implementation` CIO engine manually if they use it in their app. ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [x] Breaking change (fix or feature that would cause existing functionality to change) - [x] 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 - [x] 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 --> closes https://github.com/modelcontextprotocol/kotlin-sdk/issues/111 --------- Co-authored-by: Konstantin Pavlov <1517853+kpavlov@users.noreply.github.com> |
||
| .. | ||
| src | ||
| build.gradle.kts | ||
| README.md | ||
| settings.gradle.kts | ||
MCP Kotlin Server Sample
A sample implementation of an MCP (Model Communication Protocol) server in Kotlin that demonstrates different server configurations and transport methods for both JVM and WASM targets.
Features
- Multiple server operation modes:
- Standard I/O server (JVM only)
- SSE (Server-Sent Events) server with plain configuration (JVM, WASM)
- SSE server using Ktor plugin (JVM, WASM)
- Standard I/O server (JVM only)
- Multiplatform support
- Built-in capabilities for:
- Prompts management
- Resources handling
- Tools integration
Getting Started
Running the Server
You can run the server on the JVM or using Kotlin/WASM on Node.js.
JVM:
To run the server on the JVM (defaults to SSE mode with Ktor plugin on port 3001):
./gradlew runJvm
WASM:
To run the server using Kotlin/WASM on Node.js (defaults to SSE mode with Ktor plugin on port 3001):
./gradlew wasmJsNodeDevelopmentRun
Connecting to the Server
For servers on JVM or WASM:
- Start the server
- Use the MCP inspector to connect to
http://localhost:<port>/sse
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
- Kotlin coroutines for asynchronous operations
- SSE for real-time communication
- Standard I/O for command-line interface
- Common Kotlin code shared between JVM and WASM targets