Bcain99 Fixes

[bcain99]

• Fixed bug where mcp sse client was not re-using connections for the /message endpoint (due to not draining io)
• Added http client transport parameters for client keepalives
• Fixed bug where handleListTools was not releasing mutex

Summary by CodeRabbit

• Bug Fixes
  • Improved connection reuse and response handling for HTTP requests, enhancing reliability and performance.
  • Fixed an issue where a server read lock was not properly released during tool listing, preventing potential resource contention.

[coderabbitai[bot]]

Walkthrough

This change updates the HTTP client configuration and response body handling in the SSE client implementation. The HTTP client is now initialized with a custom transport that optimizes connection reuse parameters. Additionally, the response body in the sendRequest method is fully read into memory and closed explicitly, improving resource management and error reporting. On the server side, a missing call to release a read lock is added in the handleListTools method to ensure proper synchronization.

Changes

Files/Paths	Change Summary
client/sse.go	Updated HTTP client initialization with a custom transport for better connection reuse; improved response body handling in sendRequest by reading and closing the body explicitly, enhancing error reporting and resource management.
server/server.go	Added a missing call to release a read lock (RUnlock) in the handleListTools method to ensure correct synchronization.

Possibly related PRs

• mark3labs/mcp-go#88: Also modifies client/sse.go, focusing on removing the SSE read timeout feature to fix client hangs; related by file and component.
• mark3labs/mcp-go#55: Updates client/sse.go to add configurable headers and read timeout options, directly modifying the sendRequest method and client setup, making it closely related.

[!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 8cdb6c68ebbd2d0d583cc5f861e6f89ed08c9b89 and f6c405d8676e4b69e0533096dd2f68020483d291.

📒 Files selected for processing (2)

• client/sse.go (2 hunks)
• server/server.go (1 hunks)

🔇 Additional comments (3)

server/server.go (1)

798-799: Great fix for the missed mutex unlock!

This change correctly adds the missing s.mu.RUnlock() after collecting and sorting the tools. It ensures the read lock is released as soon as it's no longer needed, before pagination and returning the result. Without this fix, the read lock would be held for longer than necessary, potentially causing performance issues or deadlocks if other parts of the code needed to acquire a write lock.

client/sse.go (2)

59-67: Excellent improvement to the HTTP client configuration for connection reuse.

Replacing the default HTTP client with a custom one that has specified connection pool parameters is a great optimization for an SSE client. The configuration now:

• Allows up to 100 idle connections in the pool
• Limits to 10 idle connections per host
• Sets a reasonable 90-second timeout for idle connections
• Explicitly enables keepalives

This will significantly improve connection reuse for frequent client-server communication.

---

314-320: Good fix for proper response body handling.

This change properly drains the response body, which is essential for connection reuse in HTTP clients. The code now:

1. Reads the entire body with io.ReadAll()
2. Closes the body immediately after reading
3. Returns an error if reading fails
4. Includes the response body text in error messages

This ensures that connections can be properly reused, fixing the bug where connections weren't being reused for the /message endpoint.

✨ Finishing Touches

• [ ] 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[StarpTech]

@bcain99 could you add a test?