-
Notifications
You must be signed in to change notification settings - Fork 2
Switch MCP server from stdio to SSE/Streamable HTTP transport #26
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or requestplatformNew platforms, backends, transportsNew platforms, backends, transports
Description
Problem
The current MCP server uses stdio transport, meaning it must be spawned as a child process by a single MCP client (e.g. Claude Desktop). This means:
- Only one client can use it at a time (Claude Desktop OR Claude CLI, not both)
- Server lifecycle is tied to whichever client spawned it
- Each client needs its own config entry
Solution
Switch to SSE (Server-Sent Events) or Streamable HTTP transport:
- MCP server runs as a standalone long-lived HTTP server on
localhost:9876/mcp - Any number of MCP clients connect via URL
- Server runs independently — start once, all clients share it
- The WebSocket bridge to the Chrome extension stays the same
- Claude Desktop config uses
"url"instead of"command"+"args"
Implementation
- Swap
StdioServerTransportforStreamableHTTPServerTransport(orSSEServerTransport) - Add Express/Hono HTTP server to host the transport
- Update Claude Desktop config format to URL-based
- Add
npx domshell serveentrypoint - Update README docs
Sprint item
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestplatformNew platforms, backends, transportsNew platforms, backends, transports