Sandbox
Try the ChatDrift MCP server against a shared, read-only demo team — no account required.
Sandbox
ChatDrift publishes a shared sandbox team — a real team in the ChatDrift product, seeded with realistic (but fake) agents, contacts, conversations, and tickets — so that AI agents and developers can explore the MCP server before creating an account.
Note
The sandbox is read-only. Every tool call that would normally create, update, or delete
data (replying to a conversation, updating a ticket, editing an agent, and so on) returns a
sandbox_read_only error instead of making a change. Read/list tools work normally so you can
explore the shape of real data. This enforcement happens centrally for every mutating tool, not
on a route-by-route basis, so it applies uniformly across the MCP surface.
Why read-only
The sandbox team is shared by every visitor — there is no per-user isolation. Allowing writes would mean anonymous callers could edit or delete each other's test data, so every mutating action is blocked centrally and reports why:
{
"code": "sandbox_read_only",
"hint": "Sign up free at https://www.chatdrift.com to get your own team"
}
Fixture data is also re-seeded on a nightly schedule, so anything written to it directly in the database would not persist anyway.
Endpoint
The sandbox is reachable through the same team-level MCP server every ChatDrift team gets, authenticated with a published demo API key:
https://www.chatdrift.com/api/mcp/sse
| Field | Value |
|---|---|
| Transport | Server-Sent Events (SSE) |
| Authentication | nex_... API key (published demo key — see below), or OAuth |
The demo API key is not printed in this doc since this page is committed to source control. Fetch the current key, along with the rest of this brand's machine-readable discovery data, from:
/sandbox.md— the sandbox-specific discovery document: team name, MCP endpoint, and demo key./auth.md— the full auth discovery document (per the auth.md convention), which also links to the sandbox as the approved way to test authentication end-to-end.
Both are plain-text Markdown, meant to be fetched directly by an agent or a developer:
curl https://www.chatdrift.com/sandbox.md
What's seeded
The sandbox team ships with a handful of demo agents, contacts, conversations, and tickets — enough to explore list_agents, get_ticket_stats, search_contacts, and similar read tools without needing to generate your own test data first. Treat the specific records as illustrative and expect them to be reset nightly; do not build anything that depends on a particular fixture ID staying stable.
Rate limits
Sandbox traffic is rate-limited more aggressively than a real team's traffic, since it is shared across every anonymous caller. If you are building something that needs sustained or high-volume access, sign up for your own team instead — the sandbox is for a first look, not for load-bearing integrations.
Next steps
Once you're ready to move past the sandbox, create your own ChatDrift team at chatdrift.com and follow the Agent MCP Server or External Agents guide for the equivalent authenticated setup with your own data.