Was this page helpful?
Tools
Zephex exposes 10 hosted MCP tools for orientation, code reading, package intelligence, expert knowledge (Zephex_dev_info), production URL audits (audit_headers), scoped planning, and structured reasoning. Start here when you want the exact contract before you wire an agent.
Project snapshot: stack, scripts, entry points, env vars, monorepo layout, and dependency health from manifests — without reading the whole repo.
→ View docsEnd-to-end request, auth, and data-flow tracing.
→ View docsReturns the minimal file set to read before a coding task.
→ View docsStart here on any new task or unfamiliar codebase. Follow the arrows. Never guess files.
Start with get_project_context for orientation. Use explain_architecture before touching auth, billing, or database code.
Call scope_task first with a plain-English task description. It returns the minimum files to read, utilities to reuse, and which callers are at risk before you open a single source file.
Use find_code to locate where something lives, then use read_code to read the exact function or module with focused context.
Use check_package before you install or recommend a dependency. Escalate to audit_package for CVEs and migration guidance. Use audit_headers on deployed URLs. Use Zephex_dev_info for vetted auth, database, and security patterns (search, then get by slug).
Use keep_thinking when the decision could be wrong or when you need a persistent investigation trail across several tool calls.