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

Goose

Goose should be configured interactively as a command-line extension. Use the values below instead of the older YAML remote-extension flow.

OVERVIEW

Goose is an open-source AI agent from Block. For Zephex, the current setup is the interactive command-line extension flow: `ID` and `Name` set to `zephex`, `Command` set to `npx -y zephex`, `Timeout` set to `300`, and an env var of `ZEPHEX_API_KEY=...`.

CONFIG FILE LOCATION

Run `goose configure` and add a Command-line Extension.

PREREQUISITES
  1. Goose installed from https://goose-docs.ai or via `brew install goose` (macOS) / `pip install goose-ai` (Python).
  2. A Zephex API key from your dashboard.
CONFIG

Use the values exactly as shown above.

Replace `mcp_sk_your_key_here` with your Zephex API key from the dashboard.

goose configure
goose configure→ Add Extension→ Command-line Extension→ ID: zephex→ Name: zephex→ Command: npx -y zephex→ Timeout: 300→ Env var: ZEPHEX_API_KEY=mcp_sk_your_key_here
SETUP

Goose should launch `npx -y zephex` as a command-line extension with `ZEPHEX_API_KEY` in the env var field.

  1. Run `goose configure`.
  2. Choose `Add Extension`.
  3. Choose `Command-line Extension`.
  4. Enter the values shown above exactly.
  5. Start Goose: run `goose session` in your terminal or open the Goose desktop app.
VERIFY

Verify both the extension registration and a live Goose session before you rely on Zephex tools.

  1. Run `goose info -v` — it should list "zephex" as an extension.
  2. Start a session: `goose session`.
  3. Ask: "what tools do you have?" — Goose should list all 10 Zephex tools.
COMMON ISSUES

`zephex` does not appear

Run `goose configure` again and make sure you added a `Command-line Extension`, not a remote extension.

"extension not found" error

Check that the extension `ID` is exactly `zephex` and the `Command` is exactly `npx -y zephex`.

Tools not appearing

Check that `Timeout` is set to `300` and that the `Env var` field contains `ZEPHEX_API_KEY=...`.

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