feat: add sse mcp support

[aheizi]

Context

support sse mcp

Implementation

use @modelcontextprotocol/sdk SSEClientTransport

Screenshots

How to Test

step1:

here is a simple SSE MCP server : https://github.com/aheizi/simple-sse-mcp, you can start it yourself

or you can use https://mcp.composio.dev/

step2:

update cline_mcp_settings.json

{
  "mcpServers": {
    "exchange": {
      "type":"sse",
      "url": "http://localhost:3001/sse"
    }
  }
}

Now you can use this SSE MCP.

Get in Touch

aheizi

---

Important

Adds SSE MCP support in McpHub.ts with SSEClientTransport, error handling, and reconnection logic.

• Behavior:
  • Adds support for SSE MCP using SSEClientTransport in McpHub.ts.
  • Implements SSE-specific error handling and reconnection logic with exponential backoff in connectToServer() and handleSSEReconnection().
  • Updates McpSettingsSchema to include SSE configuration.
• Dependencies:
  • Updates @modelcontextprotocol/sdk to ^1.5.0 and adds eventsource to package.json.
• Configuration:
  • Introduces SSEConfigSchema and ServerConfigSchema in McpHub.ts to handle both Stdio and SSE configurations.

^{This description was created by for bb42fb6. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: cad2741

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

The pull request is quite large, with 4966 lines added and 3323 lines removed. While the changes in package.json and McpHub.ts seem related to adding SSE support, the size of the changes is substantial. If possible, consider splitting the pull request into smaller, more manageable parts. For example, you could separate the dependency updates in package.json from the implementation of SSE support in McpHub.ts. This would make it easier to review and test the changes.

[mrubens]

Awesome! Excited to take a look at this.

[hannesrudolph]

@mrubens I want this.. this is a big big deal.

[mrubens]

Looks good other than my one comment. Nice work!

[mrubens]

I merged main into your branch, hope that's ok.

[mrubens]

Do you think we should update the system prompt instructions around MCP to tell it about SSE support and the type field?

https://github.com/RooVetGit/Roo-Code/blob/main/src/core/prompts/sections/mcp-servers.ts

[punkpeye]

Can I recommend using https://www.npmjs.com/package/reconnecting-eventsource instead?

I've had a lot of issues with MCP SSE stability when implementing it in Glama.

reconnecting-eventsource helped a lot with that.

[aheizi]

This is really a good suggestion, i'll try it later.

[aheizi]

@punkpeye I have replaced reconnecting-eventsource with eventsource, thank you for your suggestion.

[punkpeye]

Adding reconnecting-eventsource would get rid of some of this boilerplate code too.

[punkpeye]

@aheizi after seeing this PR, I realized that the ecosystem would benefit from a higher level abstraction for interacting with MCP, and I built https://github.com/punkpeye/mcp-client. Would you consider using it for this PR?

[aheizi]

Do you think we should update the system prompt instructions around MCP to tell it about SSE support and the type field?

https://github.com/RooVetGit/Roo-Code/blob/main/src/core/prompts/sections/mcp-servers.ts

ok

[aheizi]

Do you think we should update the system prompt instructions around MCP to tell it about SSE support and the type field?

https://github.com/RooVetGit/Roo-Code/blob/main/src/core/prompts/sections/mcp-servers.ts

@mrubens done

[aheizi]

@aheizi after seeing this PR, I realized that the ecosystem would benefit from a higher level abstraction for interacting with MCP, and I built https://github.com/punkpeye/mcp-client. Would you consider using it for this PR?

I thought about it and think this is another matter; we can first use the native @modelcontextprotocol/sdk support for SSE MCP and then consider the optimization matters later.

@mrubens How do you think about it?

[mrubens]

@aheizi after seeing this PR, I realized that the ecosystem would benefit from a higher level abstraction for interacting with MCP, and I built https://github.com/punkpeye/mcp-client. Would you consider using it for this PR?

I thought about it and think this is another matter; we can first use the native @modelcontextprotocol/sdk support for SSE MCP and then consider the optimization matters later.

@mrubens How do you think about it?

Yeah that sounds fine to me. Excited to get this in. I just tried to resolve the conflicts.

[mrubens]

Looks good!