zephex
⌘K
Get StartedPricingMCP ToolsDocs
←Back×Sign in
Get StartedPricingMCP ToolsDocs

Documentation

Start with the endpoint and API key flow, then branch into editor setup or tool reference.

GET STARTED

What is MCP?IntroductionQuickstartAPI ReferenceUniversal RequirementsZephex vs Local MCPBest PracticesToken EfficiencyCLAUDE.md TemplateAGENTS.md TemplateMCP EcosystemMarkdown Access

EDITORS

OpenCodeOAuthVS CodeClaude CodeCursorWindsurfJetBrainsKiro CLIOAuthZedOAuthGemini CLIOAuthClineOAuthGooseCodex CLIOAuthFactory AIOAuth

OPERATING SYSTEMS

macOSWindowsLinux

TOOLS

get_project_contextread_codefind_codecheck_packageaudit_packageexplain_architectureZephex_dev_infoscope_taskaudit_headersthinking

SUPPORT

PlansPro & Max GuideUsage & AnalyticsConnection IssuesRate LimitsBillingSecurityFAQChangelog

Windsurf

Windsurf reads MCP settings from a dedicated global config file, so one Zephex entry can cover every repo you open on that machine.

OVERVIEW

Windsurf differs from repo-local editors because the MCP config is global. For Zephex, the reliable setup is the stdio block below running `npx -y zephex` with `ZEPHEX_API_KEY` in the env block.

CONFIG FILE LOCATION

Create this file: ~/.codeium/windsurf/mcp_config.json. Create the parent folders first if they do not exist.

PREREQUISITES
  1. Windsurf installed.
  2. An active Zephex account and API key.
  3. Access to the ~/.codeium/windsurf directory on the current machine.
CONFIG

Paste the JSON into the global Windsurf config file.

Replace `mcp_sk_your_key_here` with the real key from Dashboard -> API Keys.

~/.codeium/windsurf/mcp_config.json
{  "mcpServers": {    "zephex": {      "command": "npx",      "args": ["-y", "zephex"],      "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" }    }  }}
RESTART
  1. Save ~/.codeium/windsurf/mcp_config.json.
  2. Fully quit Windsurf.
  3. Reopen Windsurf.
  4. Open a fresh Cascade or chat session after the restart.
VERIFY

Check the Windsurf MCP UI before asking for code changes so you know the server itself loaded correctly.

  1. Open the MCP or Cascade tools view.
  2. You should see "zephex" connected.
  3. You should see 10 tools listed for that server.
COMMON ISSUES

"zephex" shows 0 tools

Windsurf often still has the old process in memory. Fully quit the app, reopen it, and start a new session instead of reusing the old one.

Connection failed

Double-check that the config uses `command`, `args`, and `env` exactly as shown instead of the older HTTP fields.

JSON syntax error

Validate ~/.codeium/windsurf/mcp_config.json. Trailing commas and comments are common causes, especially when copying from a formatted example.

"zephex" does not appear in the tools list

Confirm the config file is at ~/.codeium/windsurf/mcp_config.json on the same machine running Windsurf. A file in the repo root or a different user home directory will be ignored.

If the editor still does not connect, return to Quickstart or check Connection Issues.