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

Factory AI (Droid)

Factory AI's Droid agent reads `.factory/mcp.json` from your project root automatically. Use the stdio config below instead of the older HTTP URL-only entry.

OVERVIEW

Factory AI's Droid is an autonomous AI software engineer that operates on your codebase. For Zephex, the reliable setup is the stdio MCP config in `.factory/mcp.json` or `~/.factory/mcp.json`, running `npx -y zephex` with your key in the env block.

CONFIG FILE LOCATION

.factory/mcp.json in the project root, or ~/.factory/mcp.json for a user-level config.

PREREQUISITES
  1. Factory AI Droid installed and set up from factory.ai.
  2. A Zephex API key from your dashboard.
CONFIG

Create a `.factory/` directory in your project root and add `mcp.json` with the content shown.

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

.factory/mcp.json
{  "mcpServers": {    "zephex": {      "type": "stdio",      "command": "npx",      "args": ["-y", "zephex"],      "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" }    }  }}
SETUP
  1. Open your project folder in Droid (`droid` in your terminal from the project root).
  2. Run `/mcp` inside the Droid session.
  3. Confirm `zephex` appears in the server list.
  4. Use the tools normally after the server is running.
VERIFY

Confirm the server is connected inside a Droid session before relying on Zephex tools.

  1. Run `/mcp` inside Droid — zephex should show as available.
  2. Ask Droid: "what tools are available?" You should see all Zephex tools listed.
  3. CLI alternative: `droid mcp add zephex "npx -y zephex" --env ZEPHEX_API_KEY=mcp_sk_your_key_here`.
COMMON ISSUES

zephex does not appear in /mcp

Make sure `.factory/mcp.json` is in the project root (not a subdirectory) and that Droid was started from that same root directory. The file path is case-sensitive on Linux.

`npx` is not found

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

Connection fails immediately

Check that the config uses `type: stdio`, `command: npx`, and `args: ["-y", "zephex"]` exactly as shown.

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