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

OpenCode

OpenCode uses its own local MCP config shape. Use `type: local`, a single `command` array, and `environment` instead of `env`.

OVERVIEW

OpenCode is an open-source terminal AI coding agent built by the SST team. For Zephex, the reliable setup is the local MCP entry above: `type: local`, `command` as an array, and `environment` holding `ZEPHEX_API_KEY`.

CONFIG FILE LOCATION

Use `<project>/opencode.json` for a project-local setup, or `~/.config/opencode/opencode.json` for a global one.

PREREQUISITES
  1. OpenCode installed from https://opencode.ai or via `npm install -g opencode`.
  2. A Zephex API key from your dashboard.
CONFIG

Paste the JSON exactly as shown. Keep the server name as `zephex`.

Replace `mcp_sk_your_key_here` with your real Zephex API key before saving.

~/.config/opencode/opencode.json
{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "zephex": {      "type": "local",      "command": ["npx", "-y", "zephex"],      "enabled": true,      "environment": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" }    }  }}
SETUP
  1. Save the config file.
  2. Restart OpenCode or reopen the workspace.
  3. Open the MCP panel.
  4. Confirm `zephex` is connected.
VERIFY

Verify the server from inside an OpenCode session before relying on it in normal prompts.

  1. Run `/mcp` inside OpenCode.
  2. You should see "zephex" listed as connected.
  3. Ask OpenCode: "what tools are available from zephex?" You should see all 10 tools listed.
COMMON ISSUES

`zephex` does not appear

Make sure the file is named `opencode.json` in the project root or saved to `~/.config/opencode/opencode.json` for the global setup.

OpenCode rejects the config keys

Use `environment`, not `env`, and keep `command` as a single array instead of separate `command` and `args` fields.

`npx` is not found

Install Node.js so OpenCode can launch `npx`, or switch to absolute paths if your environment does not inherit PATH correctly.

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