Skip to main content

Client Compatibility

Every client and framework in the Integrate section works with Civic. Connection method depends on what the client supports.

AI Clients

ClientConnection MethodGuide
ChatGPTRemote URL (dev/admin accounts only)Setup
Claude CodeHub Bridge (stdio)Setup
Claude DesktopRemote URLSetup
Claude.aiRemote URLSetup
CodexRemote URL (Hub Bridge for offline)Setup
CursorHub Bridge (stdio)Setup
Gemini CLIRemote URL (httpUrl)Setup
GooseRemote URLSetup
JetBrains AImcp-remote bridge (Node 20+)Setup
ManusCustom Header (Bearer token)Setup
Mistral Le ChatRemote URLSetup
OpenClawRemote URLSetup
VS CodeHub Bridge (stdio)Setup
WindsurfRemote URL (serverUrl)Setup

Frameworks & SDKs

FrameworkTransportGuide
Anthropic SDKStreamable HTTP (beta header required)Setup
LangChain / LangGraphstreamable_http via MultiServerMCPClientSetup
OpenAI Agents SDKStreamable HTTPSetup
OpenAI SDKStreamable HTTPSetup
Python / Pydantic AIStreamable HTTPSetup
Python / civic-mcp-client-pythonHTTP (SSE)Setup
Vercel AI SDKStreamable HTTPSetup

Connection Methods

Remote URL — paste https://app.civic.com/hub/mcp into the client's MCP settings. Fastest setup, no local software needed.

Hub Bridge — local stdio proxy via npx -y @civic/hub-bridge@latest. Required for clients that only support stdio/local MCP servers. Needs Node.js 18+.

mcp-remotenpx mcp-remote bridges stdio clients to HTTP. Used by JetBrains. Needs Node.js 20+.

See Connection Methods for full technical details.