Zephex MCP Server

Connect Zephex to VS Code agent mode so your AI can read your open project — not guess from one file.

Install the extension, sign in once, enable Zephex in the MCP tools list. Free tier available at zephex.dev.

Works in VS Code 1.101+ (also loads in Cursor and Windsurf when they support VS Code extensions).

Install

Extensions → search Zephex → Zephex MCP Server

Or Ctrl/Cmd+P:

ext install zephex.zephex-mcp

Setup

1. Zephex: Sign In — opens zephex.dev in the browser; your API key is saved in the OS keychain (VS Code SecretStorage).
2. Agent/chat → MCP tools → enable Zephex.
3. Ask something about the folder you have open, for example:
   • “What’s in this repo — stack, main folders, entry points?”
   • “Before I change auth, which files should I read?”
   • “Is it safe to bump react from 18 to 19?”

No need to hand-edit .vscode/mcp.json if you use this extension.

How it works

Zephex is an MCP server. When agent mode is on, VS Code starts npx -y zephex locally with your API key. Tools run against files on disk in your workspace.

Sign-in uses the same flow as npx zephex setup. Keys stay in SecretStorage — not in mcp.json or settings sync.

Docs: zephex.dev/docs/editors/vscode-extension

Tools worth knowing

The agent calls these automatically; you can also name them in chat.

get_project_context

Reads the repo and returns a short brief: backend/frontend stack, frameworks, package manager, important folders, entry points, and config paths. Useful as the first call when you open an unfamiliar project.

scope_task

You describe a task in plain English (“add rate limiting to the upload route”). It returns a small set of files to read first, utilities you can reuse, and code that would break if you change a symbol — so the agent does not read the whole tree.

check_package

Checks an npm (or other registry) package name before install: does it exist, what’s the latest version, any postinstall script risk, basic advisory signal. Run this before adding a dependency.

audit_package

Goes deeper on a package you already use or plan to upgrade: CVEs with severity, breaking changes between versions, migration notes from release logs. Pairs with check_package when you are upgrading, not when you only need “does this name exist?”.

Others on the same connection

find_code and read_code for search and symbol bodies. explain_architecture for how auth, billing, or data flow through the repo. keep_thinking for longer debugging chains. Full list: zephex.dev/docs/connect-mcp

Optional: agent skill

If your agent keeps picking the wrong built-in search instead of Zephex, install the public skill pack:

npx skills add zephexMCP/agent-skills

Repo: github.com/zephexMCP/agent-skills

Commands

Without this extension

npx -y zephex setup --vscode
npx zephex doctor

Connect Zephex MCP · CLI docs

If something fails

• View → Output → Zephex (keys are not logged there)
• Zephex: Sign Out, then sign in again
• Terminal: npx zephex doctor
• Node.js 18+ on your PATH

Help: zephex.dev/support

Copyright © 2026 Zephex. Proprietary.