Skip to content

feat: Implement Streamable-HTTP Client Basic #168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Apr 19, 2025
Merged

Conversation

leavez
Copy link
Contributor

@leavez leavez commented Apr 17, 2025

This PR implements the basic streamable-http transport for the client side.

This implementation follows the specification, including (but not limited to)

  • upgradable to SSE response
  • SessionID management
    • optional session id
    • 404 response handling
    • client closes session with a DELETE request

The features below are not supported:

  • batching (not supported in other transports either)
  • continuously listening for server notifications when no request is in flight
  • stream resuming
  • server -> client request (not supported in other transports either)

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Introduced a streamable HTTP client supporting JSON-RPC communication with session management and server-sent event (SSE) streaming.
    • Added support for sending requests, notifications, and receiving asynchronous server notifications.
    • Implemented session handling, graceful shutdown, and customizable HTTP headers and timeouts.
  • Tests

    • Added comprehensive tests covering initialization, request/response handling, notification delivery, concurrency, and error scenarios.

Copy link
Contributor

coderabbitai bot commented Apr 17, 2025

Walkthrough

This change introduces a new streamable HTTP transport mechanism for JSON-RPC communication within the client package. It adds the StreamableHTTP transport, supporting both standard JSON and server-sent events (SSE) streaming responses, session management, and notification handling. The client package is extended with a function to create clients using this transport. Comprehensive unit tests are included to validate initialization, request/response handling, notifications, concurrency, and error scenarios using a mock HTTP server.

Changes

File(s) Change Summary
client/http.go New file providing a constructor function NewStreamableHttpClient to create a streamable HTTP-based MCP client.
client/transport/streamable_http.go New file implementing the StreamableHTTP transport for JSON-RPC over HTTP with support for single JSON and SSE streaming, session management, notification handling, graceful shutdown, and configuration options.
client/transport/streamable_http_test.go New file containing unit tests for StreamableHTTP, including a mock server, tests for request/response handling, notifications, concurrency, and error cases.

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5a3f37a and eb43178.

📒 Files selected for processing (1)
  • client/transport/streamable_http.go (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • client/transport/streamable_http.go

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (4)
client/http.go (1)

11-14: Error message refers to “SSE” while constructing Streamable‑HTTP transport

The constructor returns “failed to create SSE transport”, but the surrounding code and PR terminology call it “streamable‑http”. This can confuse users when debugging.

-		return nil, fmt.Errorf("failed to create SSE transport: %w", err)
+		return nil, fmt.Errorf("failed to create streamable‑http transport: %w", err)
client/transport/streamable_http.go (2)

206-228: Double‑closing resp.Body & partial SSE detection

SendRequest defers resp.Body.Close() (line 179) but hands the same reader to handleSSEResponse, whose readSSE closes it again (line 286). Closing an already‑closed body is safe but signals oversight.

Additionally, only exact text/event-stream is recognised. Apply the same strings.HasPrefix improvement as above to avoid false negatives.


314-330: SSE parser drops messages with multiline data / no explicit event:

The SSE spec allows:

  • multiple data: lines per event (should be concatenated with “\n”)
  • events without an event: field (default event name message)

Current logic overrides data on every line and ignores events lacking event: – losing information.

Suggest accumulating data across lines and treating empty event as "message" before dispatching.

Do you want a patched parser implementation?

client/transport/streamable_http_test.go (1)

281-287: Variable errors shadows stdlib package, harming readability

Inside the “MultipleRequests” sub‑test, the slice errors := make([]error, …) hides the imported errors package, which may be needed later and confuses readers.
Rename the slice to e.g. errs to avoid shadowing.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 37ac814 and 1f4d6a8.

📒 Files selected for processing (3)
  • client/http.go (1 hunks)
  • client/transport/streamable_http.go (1 hunks)
  • client/transport/streamable_http_test.go (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
client/transport/streamable_http_test.go (2)
mcp/types.go (1)
  • JSONRPCNotification (192-195)
client/transport/streamable_http.go (1)
  • NewStreamableHTTP (65-84)
client/transport/streamable_http.go (2)
client/client.go (1)
  • Client (16-24)
mcp/types.go (1)
  • JSONRPCNotification (192-195)
🔇 Additional comments (2)
client/transport/streamable_http.go (1)

163-169: 🛠️ Refactor suggestion

Content‑Type equality check too strict; real servers usually append charset

Accept / server reply commonly contains application/json; charset=utf-8.
A strict equality test will mis‑route such responses to the “unexpected content type” branch.

-	switch resp.Header.Get("Content-Type") {
+	ct := resp.Header.Get("Content-Type")
+	switch {
+	case strings.HasPrefix(ct, "application/json"):

Remember to import strings.

Likely an incorrect or invalid review comment.

client/transport/streamable_http_test.go (1)

205-224: SendRequestWithTimeout uses a pre‑canceled context – good, but assert type

The assertion checks errors.Is(err, context.Canceled) which is correct, yet if future implementation wraps the error, this might break. Consider using context.Cause (Go 1.20+) or errors.Is on ctx.Err() for resilience.
No change required, just a note.

@ezynda3 ezynda3 merged commit dd3210c into mark3labs:main Apr 19, 2025
2 checks passed
@deviantony
Copy link
Contributor

Nice, I wonder if we should add more documentation to the README about how to use this

@ls0f
Copy link

ls0f commented Apr 22, 2025

Nice work! Is the server-side implementation coming soon?

@leavez
Copy link
Contributor Author

leavez commented Apr 22, 2025

Nice work! Is the server-side implementation coming soon?

I'm working on it, but very few minutes on it every day. So it will not be very quick.

@leavez
Copy link
Contributor Author

leavez commented May 12, 2025

Nice work! Is the server-side implementation coming soon?

I'm working on it, but very few minutes on it every day. So it will not be very quick.

#273

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants