Connect from other MCP clients
The Syntropic MCP server is a standard remote MCP server. Any client that speaks the MCP spec can connect — follow your client's normal MCP setup flow with the values below.
Connection details
| Field | Value |
|---|---|
| URL | https://mcp.getsyntropic.com/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 (PKCE). No API key or client ID/secret needed — the client opens a browser window for Syntropic sign-in (Google, or Enterprise SSO) on first use. |
That's it. Every supported client uses the same URL and the same OAuth flow. The rest is just where you paste that URL.
Client-specific notes
If your client is listed below, its docs will tell you exactly where to put the URL.
- ChatGPT — follow the dedicated ChatGPT setup guide.
- Codex CLI — OpenAI docs. Add the URL to
~/.codex/config.toml, then runcodex mcp login syntropic. - Cursor — Cursor MCP docs. Settings → Tools & MCP → New MCP Server, or edit
~/.cursor/mcp.json. - Windsurf — Cascade MCP docs. Command Palette → "MCP: Add Server" → HTTP, or edit
~/.codeium/windsurf/mcp_config.json. - Zed — Zed MCP docs. Native Streamable HTTP support varies by version; use the
mcp-remotebridge if the direct URL doesn't work.
Fallback: mcp-remote bridge
If your client only supports stdio transport or has limited OAuth handling, run Syntropic through mcp-remote — a small local proxy that speaks stdio to your client and Streamable HTTP + OAuth to Syntropic:
{
"mcpServers": {
"syntropic": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.getsyntropic.com/mcp"]
}
}
}
You'll need Node.js installed. The OAuth token is cached at ~/.mcp-auth/.
Calling from the Anthropic or OpenAI API directly
If you're building your own agent on top of the Messages API or the OpenAI Responses API, you can pass Syntropic as a remote MCP server. You handle the OAuth flow once (typically via the MCP Inspector) and pass the resulting access token on each request.
See Anthropic's MCP connector docs or OpenAI's MCP tools guide for the exact request shape.
Troubleshooting
If the connection doesn't work, see Troubleshooting. The most common issues are URL typos, networks blocking mcp.getsyntropic.com, and stale cached OAuth tokens.