zephex
CLIGet StartedPricingMCP ToolsCommunityGuidesDocs
←BackSign in
CLIGet StartedPricingMCP ToolsCommunityGuidesDocs
Get started freeSign in
DocsAPIToolsEditorsChangelogHelp

GET STARTED

WelcomeQuickstartSetup videoMCP Q&A (learn)BlogWhat is MCP?Who is Zephex for?Plans & PricingZ-GASAB benchmarkBenchmark chart (live)Changelog

INSTALLATION

Web Terminal tools (plain English)Terminal tools (complete)Connect MCPVS Code Marketplace extensionCLI (no AI agent)CLI init (first run)CLI account & logoutNPX (Recommended)Test Pulse (check test)Test Pulse commandsProject MemorySupply Pulse (supply)Supply Pulse commandsTerminal CLI referenceSlash commands (37 palette)Web Terminal (dashboard)Command CompassCLI commandsCLI in DockerCLI: All editors (one command)CLI: Crush, Hermes, ChatGPT, KiloOAuth & HTTP setupInstall overviewHTTP APISetup WalkthroughHTTP vs stdio

API & KEYS

API Key ManagementKey Naming & FormatAuthenticationKey Dashboard

CONFIGURATION

Universal RequirementsSupported EditorsHow It WorksArchitectureCLAUDE.md TemplateAGENTS.md Template

EDITORS28 guides

Supported EditorsVS CodeVS Code extension (Marketplace)Claude CodeCursorWindsurfJetBrains

PLATFORM

macOSWindowsLinux

TOOLS10 tools

Capabilities OverviewTools OverviewTool FilteringTool Workflowsget_project_contextread_codefind_codecheck_packageexplain_architectureZephex_dev_infocheck_testaudit_headerskeep_thinkingproject_memory

GUIDES

Best PracticesToken EfficiencyUse CasesZephex vs Local MCPZephex vs Context7Zephex vs GitHub MCPZephex vs SmitheryMCP EcosystemMarkdown Access

SUPPORT

Help CenterMCP troubleshootingTeam rolloutFAQConnection IssuesRate LimitsDowntime & ErrorsBillingTier GuidePro & Max guideUsage LimitsUsage Analytics

LEGAL

System StatusTerms (summary)Privacy (summary)Data UseSecurityAuthenticationSecurityData HandlingPrivacy PolicyTerms of Service

Quick Links

API Reference

Complete API documentation

Troubleshooting

Common issues and solutions

Community

Join our Discord community

Plugins

Editor and CLI integrations

Pricing

Free, Pro, and Max plans

Enter
Zephex_devzephex-devzephexzephexhello@zephex.dev
© 2026 Zephex. All systems operational.
Docs/Claude.ai

Connect Zephex to Claude.ai

One OAuth login adds Zephex's ten developer tools to Claude.ai — works on web, Desktop, mobile, and Cowork on the free plan (one custom connector). No API key. No terminal.

Connect opens Zephex sign-in — not the zephex.dev homepage

When you click Connect, Claude opens zephex.dev/cli/auth in your browser — the same sign-in page as npx zephex setup (Google, GitHub, or email). After you sign in, you are sent back to Claude automatically. You should not land on zephex.us.auth0.com anymore.

Zephex uses lazy authentication: adding the URL lists tools first; sign-in happens on Connect or first tool use — not when you click Add.

The public Connectors Directory submission portal (claude.ai/admin-settings/directory/…) requires a paid Team or Enterprise org. Free and Pro accounts use custom connectors below instead.

What you get

  • • Project context detection (any GitHub repo or local project)
  • • AST-based code reading and search
  • • Architecture mapping with Mermaid diagrams
  • • Task scoping — minimal file set + reusable utilities + risk analysis
  • • Package safety checks across npm, PyPI, Cargo, Go, Maven, and 7 more registries
  • • Deep package CVE auditing
  • • HTTP security header / TLS / cookie audits with framework-specific fix snippets
  • • Structured multi-step reasoning
  • • Curated developer knowledge base

Add Zephex as a custom connector

  1. 1. Open Claude

    On Claude.ai web and Claude Desktop: click the gear icon → Settings → Connectors.
    On mobile: open the side menu → Settings → Connectors.

  2. 2. Click "Add custom connector"

    Enter the server URL exactly (no trailing slash):

    https://zephex.dev/mcp

    Click Add. Claude should list ten Zephex tools. You may not see a login screen yet — that is expected.

  3. 3. Enable Zephex in a chat

    Start a new conversation → + (lower left) → Connectors → turn on Zephex.

  4. 4. Trigger sign-in (first tool use)

    Ask Claude to run a cloud tool, for example: "Use check_package to verify the npm package express" or "Use audit_headers on https://example.com". Claude shows a Connect card or opens zephex.us.auth0.com for sign-in (Google or email — same address as your Zephex account if you have one).

  5. 5. Approve and retry

    Complete Auth0 login and consent. Claude retries the tool automatically. You should see package or header results in the reply.

For Anthropic Connectors Directory reviewers

See /docs/reviewer for step-by-step test instructions, including the pre-provisioned reviewer test account and what to expect from each tool.

Connecting from other AI editors

For Cursor, Claude Code, VS Code, Windsurf, JetBrains, and 14 other MCP-compatible editors, use the one-command installer:

npx zephex setup

See /install for full instructions.

Pricing

Free tier includes 555 requests/month — enough to evaluate every tool. Pro is $7/mo (3,500 requests), Max is $19/mo (10,000 requests). See /pricing.

Troubleshooting

"Couldn't reach the MCP server"

Make sure the URL is exactly https://zephex.dev/mcp (no trailing slash). If your network blocks Auth0, the OAuth flow won't complete — try from a different network.

"It never asked me to sign in"

Listing tools after Add does not require login. Sign-in only happens when Claude calls a tool. Enable the connector in a chat and ask Claude to use check_package or audit_headers. If you still never see Connect, remove the connector, wait five minutes, and add https://zephex.dev/mcp again.

"You don't have access to organization settings"

That page is the public Connectors Directory (Team / Enterprise only). Free accounts should use claude.ai/customize/connectors → Add custom connector — not the admin directory URL.

"Couldn't register with zephex's sign-in service"

Remove the connector, wait five minutes, and add https://zephex.dev/mcp again — then click Connect. If it still fails, open the connector's Advanced settings and paste this OAuth Client ID (skips dynamic registration): 2JrCMEKyOdY1YDZxInqTamSGNSCX9DaS. Leave Client Secret blank. Save, then Connect again.

Accepted Auth0 but Claude still says "not connected"

After Accept on the Auth0 screen, you must land back on claude.ai (Claude closes the login tab automatically). Switch to the Claude tab and refresh the Connectors page. If it still shows disconnected, click Connect once more — your session is usually saved and the second click completes without another login. Do not close the Auth0 tab before Accept finishes redirecting.

"Authorization with the MCP server failed"

Settings → Connectors → disconnect Zephex, wait five minutes, re-add the URL, then run a tool in chat again. Use Google or email on Auth0 (not GitHub — Claude OAuth uses Auth0 directly).

"Tool returns no result"

For tools that need a project (get_project_context, check_test, read_code, find_code, explain_architecture), pass either a GitHub URL like github:owner/repo or paste relevant files via Claude's file upload. Cloud-runnable tools (audit_headers, check_package, project_memory, keep_thinking, Zephex_dev_info) don't need any setup.

Need help? support@zephex.dev — we respond within one business day.