Environments

The MCP server uses the same two-mode model as the rest of Veil: sandbox and live. All reads and writes are scoped to the active mode. See Sandbox vs. production for context.

Switching modes

Your initial mode is set from your account: individuals start in live; developers start in sandbox until they go live. To switch, ask the assistant in natural language — it calls veil_set_mode on your behalf. Check your current mode any time with veil_get_session_status (see Checking the current mode), or see Sandbox vs. production for who can use which mode. Switch to live:

You: Switch to live mode.
[calls veil_set_mode with mode="live"]
→ status: "switched", activeMode: "live"
Assistant: Done. You are now in live mode. Real funds will move on your next offramp.

Switch back to sandbox:

You: Switch back to sandbox.
[calls veil_set_mode with mode="sandbox"]
→ status: "switched", activeMode: "sandbox"
Assistant: Done. You are now in sandbox mode.

Mode switching affects only this installation. The dashboard and other paired devices are not changed. Use the dashboard’s mode toggle to change all surfaces at once.

Checking the current mode

veil_get_session_status returns user.activeMode — either sandbox or live. The assistant reads this at the start of most workflows.

You: What mode am I in?
[calls veil_get_session_status]
→ status: "authenticated", user.activeMode: "sandbox"
Assistant: You are in sandbox mode.

Get Started

Concepts

For Individuals

For Developers

MCP

CLI

Environments

Switching modes

Checking the current mode

See also

​Switching modes

​Checking the current mode

​See also

Switching modes

Checking the current mode

See also