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

Codex CLI

Codex CLI uses TOML, not JSON. Add the native `mcp_servers.zephex` block to `~/.codex/config.toml`.

OVERVIEW

Codex CLI (@openai/codex) is OpenAI's terminal-based coding agent. Zephex should be configured through the native TOML MCP server block with `command`, `args`, and an `[mcp_servers.zephex.env]` table holding `ZEPHEX_API_KEY`.

CONFIG FILE LOCATION

~/.codex/config.toml — TOML format, not JSON or YAML.

PREREQUISITES
  1. Codex CLI installed: `npm i -g @openai/codex` or `brew install --cask codex`.
  2. A Zephex API key from your dashboard.
CONFIG

Append the TOML block below to `~/.codex/config.toml`.

Replace `mcp_sk_your_key_here` with your real Zephex API key.

~/.codex/config.toml
[mcp_servers.zephex]command = "npx"args = ["-y", "zephex"] [mcp_servers.zephex.env]ZEPHEX_API_KEY = "mcp_sk_your_key_here"
OR ADD VIA CLI INSTEAD

If you prefer, let Codex generate the server section first, then edit the generated env block with your key.

terminal
codex mcp add zephex -- npx -y zephex
SETUP

Codex CLI reads the TOML config directly. After saving the file, start a new Codex session so it reloads the MCP server list.

  1. Add the TOML block to ~/.codex/config.toml.
  2. Replace `mcp_sk_your_key_here` with your actual key.
  3. Start a new Codex CLI session.
  4. Run `codex mcp list` and confirm `zephex` appears.
VERIFY

Verify both the MCP connection and the live tool list before using Zephex in normal Codex sessions.

  1. Run `codex mcp list` — it should show "zephex".
  2. Start a session: `codex`.
  3. Ask: "what MCP tools are available?" — Codex should list all 10 Zephex tools.
COMMON ISSUES

`zephex` is missing from `codex mcp list`

Make sure the TOML block is appended to `~/.codex/config.toml` and restart the Codex CLI session after saving.

TOML format errors

The config uses TOML, not JSON. Keep the section headers exactly as shown: `[mcp_servers.zephex]` and `[mcp_servers.zephex.env]`.

Tools not loading

Try `codex mcp debug zephex` for detailed connection logs.

"unauthorized" on every call

Confirm the `ZEPHEX_API_KEY` value in `[mcp_servers.zephex.env]` is the real key from your dashboard.

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