Connect other MCP clients to xSpeed Hub MCP
AI & MCP 2 min read Updated Oct 2026
The connection details any MCP client needs to reach xSpeed Hub, and setup guides for Windsurf, Zed, Kiro, OpenCode and other clients.
Your client is not in the list on xSpeed Hub MCP? If it can connect to a remote MCP server over HTTP, it can use xSpeed Hub with the details below. Several more clients have their own step-by-step guide.
xSpeed Hub MCP Recommended
https://app.xspeedcache.com/xspeed/mcp One MCP connection to all your connected xSpeed sites
Connection details
Any MCP client that can reach a remote HTTP server can connect with these.
- Transport
- Streamable HTTP (POST). Give the URL above as a remote server.
- Sign-in
- OAuth: the client registers itself (dynamic client registration) and opens an xSpeed Hub page where you approve access. PKCE is required.
- Or a token
- The connection token from Connect AI in the Hub, sent in a header. Only the workspace owner can see it.
- Server name
- Our guides use
xspeedhub.
Authorization: Bearer <your connection token>
Clients with a guide
Step-by-step setup for each of these is on its own page.
Claude Cowork Desktop agent · OAuth sign-in Windsurf Editor · OAuth sign-in or connection token Zed Editor · OAuth sign-in or connection token Kiro Editor · OAuth sign-in or connection token Antigravity Editor · OAuth sign-in or connection token OpenCode Terminal · OAuth sign-in or connection token Grok Build Terminal · OAuth sign-in or connection token Kimi Code Terminal · OAuth sign-in or connection token OpenClaw Always-on agent · OAuth sign-in or connection token Hermes Agent Always-on agent · OAuth sign-in or connection token Manus Always-on agent · Connection token