kotlin-sdk/samples/kotlin-mcp-server
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Konstantin Pavlov 7bdd6b93f6
Refactor integration tests (#256)
## Motivation and Context

Flaky integration tests

## How Has This Been Tested?

`./gradlew check`

## Changes

- Use random port for Ktor in tests
- Remove unused `TestUtils` utility class.
- Replace `runTest` with `runBlocking` in test cases.
- Adjust imports and formatting for consistency.
- Add `Awaitility` dependency for dynamic server setup.
- Update `Duration` usage from milliseconds to seconds.
- Minor configuration and code formatting updates.

## 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)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [x] Test 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
-->
2025-09-11 19:38:09 +03:00
..
src Refactor integration tests (#256) 2025-09-11 19:38:09 +03:00
build.gradle.kts Remove dependency on CIO engine (#223) 2025-09-11 14:30:36 +03:00
README.md add ios and wasm targets (#81) 2025-05-29 05:01:50 +00:00
settings.gradle.kts modularize sdk (#208) 2025-08-04 11:53:38 +02:00

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)
  • 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:

  1. Start the server
  2. 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