zephex
⌘K
Get StartedPricingMCP ToolsDocs
←Back×Sign in
Get StartedPricingMCP ToolsDocs

Documentation

Start with the endpoint and API key flow, then branch into editor setup or tool reference.

GET STARTED

What is MCP?IntroductionQuickstartAPI ReferenceUniversal RequirementsZephex vs Local MCPBest PracticesToken EfficiencyCLAUDE.md TemplateAGENTS.md TemplateMCP EcosystemMarkdown Access

EDITORS

OpenCodeOAuthVS CodeClaude CodeCursorWindsurfJetBrainsKiro CLIOAuthZedOAuthGemini CLIOAuthClineOAuthGooseCodex CLIOAuthFactory AIOAuth

OPERATING SYSTEMS

macOSWindowsLinux

TOOLS

get_project_contextread_codefind_codecheck_packageaudit_packageexplain_architectureZephex_dev_infoscope_taskaudit_headersthinking

SUPPORT

PlansPro & Max GuideUsage & AnalyticsConnection IssuesRate LimitsBillingSecurityFAQChangelog

explain_architecture

Explains how requests, auth, persistence, and integrations connect across the codebase.

DESCRIPTION

Reach for this when the risk is in the flow, not in one symbol. It is the tool for understanding how a request enters the system, what middleware runs, what services get called, and where data or side effects land.

WHEN TO USE

GOOD FIT

  • Before changing auth, billing, request routing, or database flows.
  • When debugging a lifecycle problem that spans multiple layers.
  • When onboarding to a service with several integrations.
  • Before refactoring a critical request path.

AVOID IT WHEN

  • You only need a compact repo overview; use get_project_context.
  • You need the exact implementation of one function; use read_code.
  • You need a search result list; use find_code.
PARAMETERS
NameTypeRequiredDescription
pathstringNoAbsolute project path. If omitted, the current project is analyzed.
DETAILS

PATH PARAMETER

About the path parameter

Use the absolute path to the project root on the machine where the code is available. In Cursor, VS Code, or Windsurf that usually means the workspace root you already have open. On a remote dev box, pass the absolute path on that remote machine. If the path does not exist or the service cannot access it, the tool returns an explicit error instead of guessing. Results are best when the folder is a real project root with .git or package.json. Private GitHub repos are not fetched automatically.

BEST FOR

Use this before you touch critical flows

This tool is most valuable when a change crosses trust boundaries or external systems. It is especially useful for understanding auth, billing, usage metering, webhook handling, and other high-risk paths where changing one file without understanding the flow causes regressions.

EXAMPLE
tools-call.json
{  "jsonrpc": "2.0",  "id": 6,  "method": "tools/call",  "params": {    "name": "explain_architecture",    "arguments": {      "path": "/Users/name/projects/zephex"    }  }}
OUTPUT
response.txt
Entry: dashboard/src/app/api/mcp/route.tsAuth flow: Authorization header -> validateApiKey -> user + tier lookupRate limits: endpoint limiter before tool dispatch, tool-specific limiters for heavy toolsPersistence: usage and telemetry written through Supabase, Redis used for fast limit checksIntegrations: Stripe for billing, Upstash Redis for throttling, Sentry for error monitoring

TOKEN EFFICIENCY

Architecture summaries usually land in the 700 to 1,400 token range. Tracing the same request path manually across middleware, services, handlers, and data layers often costs 12,000 to 30,000 tokens of file reading.