One MCP, three surfaces — Claude, ChatGPT, Cursor

Same MCP protocol, three clients — but Cursor can use local stdio while Claude and ChatGPT need public HTTPS from their cloud. "Works in Cursor" is not org-ready until the same URL works in chat connectors too.

Source: Influzer.ai

Teams ship one MCP server and assume org rollout is done when Cursor connects. It is not.

Three surfaces, different rules:

Cursor — stdio or HTTPS in .cursor/mcp.json
Claude — remote HTTPS connector from Anthropic cloud
ChatGPT — Developer Mode connector from OpenAI cloud

Chat products cannot hit localhost. Stdio-only servers are Cursor-only, not company-wide.

Org-ready = one HTTPS endpoint, same tools/list, setup docs for each client, one security allowlist row.

Try it with read-only Discovery: https://www.influzer.ai/mcp/discovery · setup tabs.

Full matrix + rollout checklist: One MCP connector, three surfaces.