Zephex MCP Server

Zephex — hosted MCP (Zed extension)

Zephex is a hosted MCP server for AI coding agents: one HTTPS endpoint, one API key, ten tools that read your repository instead of guessing from training data.

This repository is the Zed extension that connects Zed’s Agent Panel to that hosted server.
Product home: zephex.dev · Endpoint: https://zephex.dev/mcp

What Zephex is

Agents call tools on demand (project context, search, read, architecture, tests, packages, URL audit, memory, reasoning, playbooks). Local file access stays with the client process; tool requests go to the hosted API with your key.

Not a local Docker stack you have to babysit. Not a second “mystery” server URL — use https://zephex.dev/mcp.

Quick start in Zed

1. API key

1. Sign up at zephex.dev
2. Create a key at zephex.dev/dashboard/api-keys
3. Keys look like mcp_… (formats evolve — copy from the dashboard)

Free tier available. Current limits and paid plans: always check the dashboard / pricing on the site.

2. Install the extension

In Zed: command palette → zed: extensions → search Zephex → Install.

3. Settings

Open settings JSON (cmd-, / ctrl-,, then {}) and set:

{
  "context_servers": {
    "mcp-server-zephex": {
      "settings": {
        "zephex_api_key": "YOUR_KEY_FROM_DASHBOARD"
      }
    }
  }
}

4. Reload

Command palette → zed: reload context servers.
Open the Agent Panel — the ten Zephex tools should appear.

The 10 tools (current product)

These are the only tool names. Older docs sometimes listed removed names — ignore those.

Sensible call order

get_project_context → find_code → read_code → [edit] → check_test
         ↘ explain_architecture when the change spans modules

Removed / do not use: scope_task, inspect_url, audit_package, bare thinking
(Package upgrades → check_package with the upgrade/security task. Stuck debug → keep_thinking.)

Agent routing skill (any skill-aware agent setup):

npx skills add zephexMCP/agent-skills --skill zephex

MCP (hosted) in one glance

Generic HTTP shape (for clients that take a URL + header — not required for this Zed extension):

{
  "url": "https://zephex.dev/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}

This extension instead spawns the official zephex npm package over stdio with ZEPHEX_API_KEY set (Zed-managed Node).

Optional: terminal CLI (same account)

Same key and tools, different surface — human text, project cwd, deep --json for agents.

# Mac / Linux
curl -fsSL https://zephex.dev/cli/install.sh | bash

# Windows PowerShell
irm https://zephex.dev/install.ps1 | iex

cd /path/to/your-project
zephex login
zephex overview
zephex deep --json
zephex find "auth"
zephex test

Full command map: github.com/zephexMCP/zephex-cli · docs/cli-commands

Browser Mode 2 (no local install): dashboard/terminal · zephex-web-terminal

How this extension works

Thin Rust / Wasm extension for Zed that:

1. Reads zephex_api_key from Zed settings
2. Uses Zed’s bundled Node runtime to ensure the zephex package is available
3. Starts the MCP stdio server with your key as ZEPHEX_API_KEY
4. Tool calls are authenticated against the hosted API

No separate Docker container. No manual port. No system-wide Node required for the extension path.

Compatibility

• Zed 0.190+ (extension API as declared in extension.toml)
• macOS, Linux, Windows
• Zed-bundled Node for the MCP process

Troubleshooting

Related public pages

License

MIT for this extension repository.
The hosted Zephex service is a commercial product; see zephex.dev for terms and privacy.