Three Perplexity surfaces exist — do not mix them up. This guide covers Perplexity Computer (web) Custom Remote Connectors at perplexity.ai/account/connectors and the curated Computer Connectors directory. For the macOS Desktop app (API key only), see Perplexity Desktop docs.
Official Perplexity Computer MCP documentation: Perplexity Custom Remote Connectors
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
Custom Remote Connector is self-serve today. The curated Computer Connectors grid (Developer category, alongside Supabase/Vercel) requires a Perplexity partner listing — see Partner listing below.
Perplexity OAuth callback (already registered on Zephex): https://www.perplexity.ai/rest/connections/oauth_callback — Enterprise orgs use https://enterprise.perplexity.ai/rest/connections/oauth_callback
Paste this URL into the Custom connector form. OAuth discovers endpoints automatically; API Key mode uses the same URL.
https://zephex.dev/mcpTip
If OAuth fails with “did not return a client_secret”, switch to API Key auth — Perplexity has an intermittent public-DCR bug (community thread #5172). API Key hits https://zephex.dev/mcp directly.
Note
Last verified: July 2026 — Perplexity Computer Connectors directory listing is partner-only (no self-serve form). Custom Remote Connector is the supported integration path today.
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 Computer does not show Zephex tools — indexed for docs search.
How do I connect Zephex to perplexity-computer?
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-computer MCP config?
Run npx -y zephex@latest list — it prints every config path on this machine that references Zephex.
perplexity-computer 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-computer?
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 Computer: use check_package on a trending npm library from this research thread.”
Custom remote connector returns registry intel beside web answers.
“get_project_context on github:vercel/next.js — stack and scripts.”
Hosted MCP adds repo facts without cloning locally.
“audit_headers on a URL I am citing in this Computer workflow.”
Objective TLS/header grade for published analysis.
“check_package task=security on lodash before recommending it.”
CVE and typosquat signals in the same Perplexity thread.
“explain_architecture for github:supabase/supabase — auth vs API layers.”
Mermaid diagram grounds follow-up Computer steps.
“Zephex_dev_info: JWT vs session cookies for a B2B SaaS architecture question.”
Vetted dev KB 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:
Dynamic client registration did not return a client_secret
Known Perplexity bug with RFC 7591 public clients. Use API Key auth instead, or retry OAuth later. Do not paste a fake client_secret.
invalid_redirect_uri during OAuth
Ensure you use Custom Remote Connector (not Desktop). Callback must be https://www.perplexity.ai/rest/connections/oauth_callback. Contact support@zephex.dev if registration still returns 400 after deploy.
Connector verifies but tools never run
Enable the connector in Sources for the thread. Say explicitly “use the Zephex MCP tool check_package”. Add github:owner/repo for repo tools.
API Key mode — no traffic on our server
Re-save the connector with the full key. Confirm Transport = Streamable HTTP and URL = https://zephex.dev/mcp. Test with curl: curl -H "Authorization: Bearer YOUR_KEY" -X POST https://zephex.dev/mcp -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'.
CORS or stream failed errors in browser console
Usually transient Perplexity UI issues. Retry after a minute. Confirm perplexity.ai origin is allowed (zephex.dev CORS updated July 2026).
Perplexity Computer Custom Remote Connector 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.