Was this page helpful?
Configuration
Zephex works with any editor or CLI tool that supports the Model Context Protocol. 27 editors are documented — same endpoint https://zephex.dev/mcp, same 10 tools.
Every editor below connects to the same hosted endpoint and gets the same 10 tools. The only difference is where the config file lives and whether the editor uses stdio or HTTP transport.
Config: Settings → Connectors → MCP
Transport: HTTP/OAuth
Config: claude_desktop_config.json
Transport: stdio
Config: Developer Mode → Create App
Transport: HTTP/OAuth
Config: Settings → MCP
Transport: HTTP
Config: .gemini/antigravity/mcp_config.json
Transport: HTTP
Config: .cursor/mcp.json
Transport: HTTP
Config: ~/.claude.json
Transport: HTTP
Config: .vscode/mcp.json
Transport: HTTP
Config: ~/.codeium/windsurf/mcp_config.json
Transport: HTTP
Config: AI Assistant Settings UI
Transport: Streamable HTTP
Config: settings.json (context_servers)
Transport: HTTP
Config: cline_mcp_settings.json
Transport: Streamable HTTP
Config: ~/.config/goose/config.yaml
Transport: Streamable HTTP
Config: ~/.warp/.mcp.json
Transport: HTTP / SSE
Config: ~/.gemini/settings.json
Transport: HTTP
Config: ~/.codex/config.toml
Transport: HTTP
Config: .continue/mcpServers/ YAML
Transport: Streamable HTTP
Config: .roo/mcp.json
Transport: Streamable HTTP
Config: Trae MCP JSON
Transport: HTTP
Config: .factory/mcp.json
Transport: HTTP
Config: opencode.json
Transport: HTTP (remote)
Config: ~/.copilot/mcp-config.json
Transport: HTTP
Config: Kiro MCP JSON
Transport: HTTP
Config: ~/.kiro/settings/mcp.json
Transport: HTTP
Config: crush.json (mcp.http)
Transport: HTTP
Config: ~/.hermes/config.yaml
Transport: HTTP
Config: .kilocode/mcp.json
Transport: HTTP
Any MCP-compatible client that supports stdio or HTTP transport will work with Zephex. If your editor is not listed above, use the universal config from the Quickstart guide and adapt the file path for your editor.