TmpState
TmpState (temp state) - a tokenless temporary JSON database.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- Create Database: Create a temporary JSON database (24h TTL, no signup, no keys). Returns the db URL — the only credential — plus admin URL, limits and expiry. Create once per project/task, persist the
- Database Status: Usage, limits, tier and expiry for a database (GET $DB/__meta equivalent).
- List Documents: List documents in a collection, oldest first. Response shape: {collection, items: [{id, data, created_at, updated_at}], next_cursor}. Documents live under .data. Pass cursor to page.
What data it sees
Do you need an account
No: the server works without sign-in
TmpState (temp state) - a tokenless temporary JSON database. One curl creates a database; the URL is the only credential. No signup, no API keys, 24h free, $1 to keep for a week. Also a zero-key MCP server: https:// tmpstate.dev/mcp
Server tool list (14)
Raw names from tools/list. Only developers need these.
| create_database | Create a temporary JSON database (24h TTL, no signup, no keys). Returns the db URL — the only credential — plus admin URL, limits and expiry. Create once per project/task, persist the db URL immediately (local ~/.tmpstate/credentials, project README, and your memory), and reuse it instead of creating again. For retries or parallel workers, pass a stable idempotency_key so duplicate calls return the same database. |
| database_status | Usage, limits, tier and expiry for a database (GET $DB/__meta equivalent). |
| list_documents | List documents in a collection, oldest first. Response shape: {collection, items: [{id, data, created_at, updated_at}], next_cursor}. Documents live under .data. Pass cursor to page. |
| get_document | Read one document by id. The stored fields are under .data. |
| create_document | Insert a JSON object into a collection (collections are created implicitly). Counts against the write and document quotas. |
| update_document | Shallow-merge a patch into a document (top-level keys overwrite; keys are never deleted). Counts against the write quota. |
| delete_document | Delete one document. Never blocked by quotas; frees a document slot. |
| delete_collection | Delete every document in a collection at once (useful to re-seed). Irreversible. |
| extend_database | Without a plan: returns the transparent pricing table for keeping this database alive longer. With a plan: returns a Stripe checkout URL for the human to pay — never buy without the user's explicit approval. Works on expired (frozen) databases too: paying restores them. |
| pro_checkout | Mint a Pro account token plus a Stripe subscription checkout URL ($8/mo, 3 always-on databases included). Persist pro_token immediately; the human pays in a browser. Never start checkout without the user's explicit request. |
| pro_list_databases | List the Pro account's databases (ids, usage, limits, expiry) so a fresh session can reconcile against persisted db URLs. URLs are never stored server-side — match ids to the URLs you persisted. |
| pro_create_database | Create a new always-on database owned by the Pro account. Beyond the included allotment this costs extra per month — the tool then returns confirmation_required with the exact price; relay it to the user and only retry with accept_overage_usd after their explicit approval. |
| pro_attach_database | Attach an existing free/extended database to the Pro account: same URL, same data, TTL removed, quotas raised. Beyond the included allotment the same explicit overage consent as pro_create_database applies. |
| pro_cancel | Cancel at period end. This is not just a billing change — it schedules deletion of ALL databases on the account. Call without confirm first: the response spells out the consequences with concrete dates; show them to the user and only retry with confirm="cancel" after their explicit approval. |