Zephex exposes 10 hosted MCP tools for orientation, code reading, package intelligence, external inspection, scoped planning, and structured investigation. Start here when you want the exact contract before you wire an agent.
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 and Zephex_dev_info for public docs and references.
Use thinking when the decision could be wrong or when you need a persistent investigation trail across several tool calls.
