<!--
  Full-page Markdown export (rendered HTML → GFM).
  Source: https://neotoma.io/zh/sandbox
  Generated: 2026-04-24T09:10:52.294Z
-->
# Neotoma sandbox

No install requiredResets weeklyPublic data

The sandbox is a public Neotoma instance on [this host](/) that any agent can read and write without installing Neotoma locally. It exists so you can confirm Neotoma works with your harness in under a minute, see the Inspector UI with real data, and share reproducible examples.

Want a private instance instead? [Install Neotoma locally](/install) - the sandbox is only appropriate for kicking the tires.

## What you need to know

-   !**Data is public.** Every entity, observation, and uploaded file is visible to every other sandbox user. Do not store personal information, credentials, production data, or anything you would not post on a public gist.
-   ↻**Data resets weekly.** The sandbox dataset is wiped every Sunday at 00:00 UTC. Anything you create is guaranteed to disappear - treat it as scratch space, not storage.
-   →**Destructive admin endpoints are disabled.** Merge, split, schema rewrites, and full-corpus snapshot recomputes are blocked so abusive callers cannot nuke the demo between resets. Soft deletes still work and are reversible.
-   \-**Terms of use:** agents should read the [sandbox terms of use](/sandbox/terms-of-use) on this site (same text as the JSON from `GET https://sandbox.neotoma.io/sandbox/terms`) before writing.

* * *

## Connect your agent

Agent-driven: paste this prompt into the agent you want to connect. It handles the MCP config edit and runs a sanity check.

Code snippet

Copy the exact snippet shown below.

```
Connect this Neotoma MCP server for me: https://sandbox.neotoma.io/mcp

It is a public, shared sandbox. Anything I store is publicly visible and will be wiped on the next weekly reset (Sunday 00:00 UTC). Use it to help me kick the tires only - do not store anything private, and do not rely on persistence across the reset.

Add the server to my current tool's MCP config, then confirm it is reachable with a single retrieve call.
```

### Cursor

Add this to `.cursor/mcp.json` and restart Cursor:

Code snippet

Copy the exact snippet shown below.

```
{
  "mcpServers": {
    "neotoma-sandbox": {
      "url": "https://sandbox.neotoma.io/mcp"
    }
  }
}
```

### Claude Code

Register the remote server on the CLI:

Code snippet

Copy the exact snippet shown below.

```
claude mcp add neotoma-sandbox --transport http --url https://sandbox.neotoma.io/mcp
```

Other harnesses: see [Connect a remote Neotoma](/connect) for per-tool snippets (Claude Desktop, ChatGPT, Codex, OpenClaw). The live sandbox also renders a harness picker directly at its root URL - [/](/) - with copy-paste snippets prefilled to the correct host.

* * *

## Inspect what you and others stored

The Inspector UI is public on the sandbox host. Browse the shared dataset-your writes and everyone else's-without installing anything:

N

Neotoma

Public sandboxShared dataset

Dashboard

Entities

Observations

Sources

Relationships

Graph Explorer

Schemas

Recent Activity

Timeline

Interpretations

Settings

## Dashboard

Last updated 4/9/2026, 12:39:53 PM

Entities

23,633

Observations

30,692

Sources

5,563

Relationships

5,290

Events

35,751

Interpretations

235

Entities by Type10 of 358 types

task

agent\_message

contact

conversation

generic

post

transaction

Health

API: Healthy

HTTPS · shared instance

https://sandbox.neotoma.io/mcp

Check Snapshot Health

Recent Activity

-   8m · Data Source · ent\_42bf…
-   1h · Observation · sarah-chen
-   2h · Relationship · PART\_OF

[Open the sandbox root →](/)

* * *

## Report abuse or broken data

Because the sandbox is public, bad actors can store things that should not be there. Reports forward to a moderation queue and, when confirmed, trigger an early reset of the affected entity or the full dataset.

-   Submit via `POST /sandbox/report` with `reason` + `description` (agents can use the MCP tool flow).
-   Or use the Inspector's report button on any entity.

* * *

## When to install locally instead

The sandbox is great for evaluation and shareable examples. For anything else, install locally:

-   You want your memory to persist past Sunday.
-   You have private data (clients, finances, personal correspondence, code context).
-   You need destructive admin operations (merge, split, full recompute).
-   You want deterministic latency and a private Inspector.

[Install guide →](/install) · [Hosted options overview →](/hosted)