MCP vs REST - Zevari Docs
One engine, two front doors. Use MCP inside an agent client; use the REST API from your own code. Same capabilities and the same approval gate.
Two doors, one engine
Zevari is reachable over MCP and over a REST API. They expose the same method contract, the same capabilities, and the same approval gate. The REST API is a thin router over the same methods the MCP server exposes.
Use MCP when
Your agent runs in an MCP client (Claude, Claude Code, Codex, ChatGPT). The agent discovers Zevari's tools and orchestrates them; you talk to the agent.
Use REST when
You write your own code, run a cron job, or use a non-MCP runtime (OpenClaw, Hermes Agent, or custom). Authenticate with a zvr_api_ bearer token against https://api.zevari.ai.
You can mix
They are interchangeable per operation. Run MCP inside your agent and REST in a backend job against the same workspace.
Same approval gate
Either door, writes are approval-gated. See the Approvals contract.