modelcontextprotocol / modelcontextprotocol/kotlin-sdk

WASM is missing in the multiplatform server sample

Open
#456 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement P3 ready for work samples
Dominant language
Kotlin
Stars
1.5k
Forks
248
Avg merge
1d 20h
Merged PRs (30d)
23

Description

In README.md, it says:

kotlin-mcp-server: demonstrates a multiplatform (JVM, Wasm) MCP server setup with various features and transports.

But it seems to be JVM-only.

After checking the history, I found that there once was a WASM sample added in https://github.com/modelcontextprotocol/kotlin-sdk/pull/81, but then removed in https://github.com/modelcontextprotocol/kotlin-sdk/pull/345.

The WASM sample was helpful, and it shows the SDK is multiplatform but not JVM-only. Should we add it back?

And also, the WASM sample was SSE-only, so I wonder if it is possible to create an STDIO MCP server targeting WASM.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with README.md and the samples/kotlin-mcp-server directory, then compare the changes from PRs 81 and 345. Check the current multiplatform and transport configuration to determine whether a WASM sample can be restored and whether STDIO is supported for WASM. Done means the sample and README accurately reflect the supported WASM targets and transports.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin, wasm
Domain
backend, build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.