modelcontextprotocol / modelcontextprotocol/kotlin-sdk
StreamableHTTP Client integration tests
Open
Nobody has claimed this yet.
P3
ready for work
tests
- Dominant language
- Kotlin
- Stars
- 1.5k
- Forks
- 248
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 23
Description
Create integration tests for Client with StreamableHTTP transport:
1. Roots
- Capabilities https://modelcontextprotocol.io/specification/draft/client/roots#capabilities
- Listing Roots https://modelcontextprotocol.io/specification/draft/client/roots#listing-roots
- Bad request
- Security - Allow
- Security - Deny
- Root list changes https://modelcontextprotocol.io/specification/draft/client/roots#root-list-changes
2. Sampling
- Capabilities
- Creating Messages - Text https://modelcontextprotocol.io/specification/draft/client/sampling#creating-messages
- Creating Messages - Image
- Creating Messages - Audio
3. Elicitation
- Capabilities
- Creating Elicitation Requests - Text https://modelcontextprotocol.io/specification/draft/client/elicitation#creating-elicitation-requests
- Creating Elicitation Requests - Structured Data https://modelcontextprotocol.io/specification/draft/client/elicitation#structured-data-request
- Supported Schema Types - String
- Supported Schema Types - Number
- Supported Schema Types - Enum
- Reject Response
- Cancel Reponse
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Client integration-test entry points for the StreamableHTTP transport and compare the unchecked Roots, Sampling, and Elicitation cases with the linked MCP specification sections. Add coverage for each listed scenario, including bad requests, security decisions, audio, structured data, rejection, and cancellation, with all checklist items passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- api, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100