Endpoints
The read-only endpoint does not merely refuse write calls. The write tools are structurally absent
from it, so no scope, flag or bug can surface one there.
Authentication
Two ways to connect. API key. Issue a key with theassistant:read scope under Settings, then Integrations, then
API keys, and send it as a bearer token. Add assistant:write only if you want the client to be
able to act.
OAuth. Where your client supports it, connect through OAuth instead, which means each person’s
actions are attributed to them rather than to a shared key.
Read tools
ask_vorel is the thick one. The others return data for the client’s own model to reason over;
ask_vorel runs a full turn inside Vorel and returns a written answer.
The list and search tools accept a response_format of concise or detailed, and a
max_results. Concise is the default and costs roughly a third of the tokens. Where a cap trims
results, the response says so and tells the model how to narrow the query, instead of silently
truncating.
Write tools
Available only withassistant:write, and only when write actions are enabled for your workspace:
A tool whose policy requires approval is advertised as such at connection time, so a well-behaved
client can tell the user before it tries.
Prompts
Three ready-made workflows appear as slash commands in clients that support MCP prompts:- Morning triage, which walks the client through what needs attention
- Explain this agent reply, which pulls the retrieval and routing behind one answer
- Draft knowledge from gaps, which turns your ranked knowledge gaps into draft answers