Add Zephex to Cline’s Remote MCP configuration (cline_mcp_settings.json or the Cline MCP panel). Zephex is hosted at https://zephex.dev/mcp — use streamableHttp with url + Bearer headers, not npx stdio.
Official Cline MCP documentation: Cline MCP docs
Without MCP, your agent guesses project layout and misses supply-chain risk. Zephex connects one hosted endpoint so every session gets the same ten tools — no per-machine npm installs, no version drift across the team.
HTTP and stdio setups both need a key from your Zephex dashboard. OAuth-only flows (ChatGPT, Claude.ai web) sign you in in the browser instead — skip this section for those.
Matches the published CLI (mcp-proxy/src/commands/setup.ts). One command signs you in, writes the correct transport, and verifies 10 tools.
Account teardown: logout vs disconnect · Connect MCP walkthrough
Search docs for “where is my MCP file” — the answer is always: run list first, then open the path it prints.
Documented paths: Cline globalStorage …/cline_mcp_settings.json
Cline wizard writes stdio for local FS tools.
Runs the same code as mcp-proxy/src/commands/setup.ts — OAuth in browser, creates a CLI key, writes your editor config, verifies tools.
npx -y zephex setup --clineSkip browser OAuth — paste a key from zephex.dev/dashboard/keys. Must start with mcp_prod_, mcp_dev_, or mcp_sk_.
npx -y zephex setup --cline --api-key mcp_prod_your-key-hereIf you edit by hand after setup: Transport: stdio (see Cline globalStorage …/cline_mcp_settings.json).
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" } } }}After CLI install, fully restart the app if tools do not appear. Manual JSON/TOML blocks below are equivalent — use them when CLI commands are unavailable.
Full comparison: HTTP vs stdio · npx zephex reference
Use Cline’s Remote Servers tab — hosted Zephex matches Cline’s streamableHttp shape.
Replace mcp_sk_your_key_here with your key from Dashboard → API Keys. Copy the full key once at creation — paste into Authorization: Bearer … for HTTP configs, or into ZEPHEX_API_KEY for stdio/npx configs.
Uses "type": "streamableHttp" and url — remove any old command/npx zephex block.
{ "mcpServers": { "zephex": { "url": "https://zephex.dev/mcp", "type": "streamableHttp", "headers": { "Authorization": "Bearer mcp_sk_your_key_here" } } }}Tip
If you previously used stdio (npx -y zephex), delete that entry so only the remote block remains.
Note
Cline also has a marketplace install path — this page documents manual remote HTTP only.
Run these in a terminal when the editor UI is unclear — catches stale npm, wrong transport, and project shadows.
npx -y zephex@latest listnpx -y zephex@latest doctornpx -y zephex@latest repair# Fully quit the editor (Cmd+Q / Alt+F4), reopen, start a new agent sessionAfter saving your config, confirm Zephex is connected before you rely on it in real work.
Questions people ask when Cline does not show Zephex tools — indexed for docs search.
How do I connect Zephex to cline?
Fastest: npx -y zephex setup --cline (browser sign-in, writes config, verifies 10 tools). Or paste manual config on this page, save, fully quit the app, reopen.
Where did setup save my cline MCP config?
Run npx -y zephex@latest list — it prints every config path on this machine that references Zephex.
cline works in terminal but not in the editor
GUI apps often lack nvm/fnm PATH. Run npx -y zephex@latest repair, ensure Node is on system PATH, fully quit the editor.
How do I disconnect Zephex from cline?
mcpcli disconnect --cline — revokes key and strips config.
You do not call tools yourself — ask your agent in plain language. Try these once Zephex is connected:
“Cline task: before npm install, check_package on the dependency name from the ticket.”
Registry review inside the Cline MCP panel workflow.
“get_project_context on the VS Code workspace Cline is attached to.”
Confirms stack for the saoudrizwan.claude-dev extension root.
“find_code where API routes register webhooks — then read_code that registrar.”
Two-step navigation for Express/Fastify apps.
“check_test: replace console logging with pino across the backend.”
File list and risks before Cline applies multi-file diffs.
“explain_architecture for our frontend ↔ BFF ↔ services setup.”
Mermaid for cross-layer reasoning.
“Zephex_dev_info for Supabase RLS policies — then suggest SQL changes.”
Expert DB patterns paired with your schema context.
You do not pick tools from a menu — ask your agent in normal sentences. Half of the tools only need a package name or URL; the other half need to know which codebase you mean (your Mac/Windows project folder or a GitHub repo).
These situations usually mean the setup cannot work until you fix the underlying issue:
zephex not in MCP list
Top-level key must be mcpServers. Save via Cline’s MCP editor, not a random file.
Connected but 0 tools
Confirm streamableHttp type and https://zephex.dev/mcp URL. Reconnect from MCP panel.
JSON parse error
Valid JSON only — no comments or trailing commas.
Still launches npx
Remove stdio block entirely; keep only remote url config.
Tools work in terminal, not Cline
PATH issues affect stdio only — remote HTTP needs Bearer + internet, not npx.
Cline Remote MCP (streamableHttp) attaches ten Zephex tools to each task:
get_project_context
Reads your project structure, dependencies, scripts, env vars, and framework markers in one call. Replaces manually opening package.json, tsconfig, and multiple config files at the start of every session.
read_code
AST-based code extraction: pass a symbol name and get the implementation without reading entire files. Supports symbol lookup, batched file reads, and structural outlines for large files.
find_code
Ranked search across the repo for definitions, usages, and patterns. Faster than blind grep when the agent does not know where a symbol lives.
check_package
Live registry lookup for npm, PyPI, Cargo, and Go modules. Surfaces typosquat risk, maintainer changes, and suspicious version jumps before you run install.
explain_architecture
Generates Mermaid diagrams for auth flows, service boundaries, and module dependencies so the agent reasons about structure instead of guessing.
check_test
Turns a task description into the smallest file set to read or edit, with risk ratings and caller impact notes.
audit_headers
Grades a deployed URL for CSP, HSTS, TLS, cookies, and redirects. Returns fix snippets for common hosts (Vercel, Cloudflare, Nginx).
keep_thinking
Structured multi-step debugging: tracks hypotheses and conclusions so long investigations do not loop.
Zephex_dev_info
Expert patterns for authentication, databases, frontend frameworks, deployment, and mobile stacks when the agent needs vetted guidance.
project_memory
Persists decisions, gotchas, and conventions per project in ~/.zephex/memory (SQLite FTS5). recall before unfamiliar areas; remember after discoveries. Local stdio only on npx zephex.