Add Zephex in Perplexity Desktop Settings under MCP (or Integrations). macOS desktop app only — not Comet browser, not Perplexity’s npm MCP package for Cursor/VS Code. Zephex is hosted at https://zephex.dev/mcp and needs internet.
Official Perplexity Desktop MCP documentation: Perplexity help center
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: Run npx -y zephex@latest list
Full comparison: HTTP vs stdio · npx zephex reference
Perplexity’s public docs often describe their own MCP server for other editors — you are adding Zephex as a custom remote server inside the Desktop app.
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.
If the app has a JSON editor, paste this block. If it only has form fields, copy url and Authorization from it.
{ "mcpServers": { "zephex": { "url": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer mcp_sk_your_key_here" } } }}Note
Last verified: July 2026 — Desktop ≠ Perplexity Computer (web). For perplexity.ai/account/connectors OAuth or API key, see /docs/editors/perplexity-computer.
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 Perplexity Desktop does not show Zephex tools — indexed for docs search.
How do I connect Zephex to perplexity-desktop?
Fastest: npx -y zephex setup (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 perplexity-desktop MCP config?
Run npx -y zephex@latest list — it prints every config path on this machine that references Zephex.
perplexity-desktop 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 perplexity-desktop?
mcpcli disconnect --all or remove the zephex block manually from your config file.
You do not call tools yourself — ask your agent in plain language. Try these once Zephex is connected:
“Perplexity Desktop: check_package on a trending npm library mentioned in this thread.”
Fact-check install risk beside web search results.
“get_project_context on github:facebook/react-native — framework summary.”
Hosted MCP complements Perplexity’s web answers with repo facts.
“audit_headers on a URL I am researching for a security write-up.”
Objective header/TLS grade for published analysis.
“explain_architecture for a sample repo I linked — auth vs API layers.”
Diagram grounds follow-up answers in real structure.
“check_test: add dark mode to an open-source dashboard — which files matter?”
Task-focused file list for research-backed recommendations.
“Zephex_dev_info: compare session cookies vs JWT for a B2B SaaS.”
Architecture guidance without uploading proprietary code.
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:
401 Unauthorized
Use Bearer + space + full mcp_sk_ key. Regenerate key if unsure. No quotes around the key in a dedicated API key field.
UI labels do not match this guide
Map Server URL → https://zephex.dev/mcp and Secret/Token → your key. Screenshot Settings → MCP and compare to the JSON block.
Connected but project tools empty
Add github:owner/repo or /Users/you/project in the prompt — Desktop does not auto-detect open folders like an IDE.
Cannot find MCP in Settings
Update Perplexity Desktop to the latest build; MCP is app-specific and may roll out gradually.
Perplexity Desktop remote MCP exposes the full Zephex tool catalog:
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.