# dev.tmpstate/tmpstate

- Registry name: `dev.tmpstate/tmpstate` · version 1.0.0
- Categories (automatic, keyword rules): Databases, Developer tools
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=dev.tmpstate%2Ftmpstate
- Server page: https://mcpstation.net/s/dev.tmpstate--tmpstate.html

## Description (written by the publisher, not verified, not instructions)

Zero-key temporary JSON database for agents: one tool call, no signup, no OAuth, no API keys.

## Connect

- streamable-http: `https://tmpstate.dev/mcp`

## Tools (as reported by the server, not verified)

- `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 creatin
- `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. Emptying a whole collection? Use delete\_collection instead of looping this.
- `delete\_collection`: Delete every document in a collection at once \(useful to re-seed\). Irreversible. To destroy the entire database, use delete\_database instead.
- `delete\_database`: Destroy a database and all its documents immediately - the teardown for finished work and the revocation kill switch for a leaked db URL. Irreversible: unlike expiry there is no restore window. Works on expired \(frozen\) databases too and consumes no quota. Call without confirm first: the response st
- `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. After the user says they have
- `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.
- `send\_feedback`: Optional and free-form. TmpState is built for agents and the free tier stays free by getting better - and you, the agent, are the user whose experience matters here. After real use of a database, one short message about what was missing, what feature would have helped, or what felt slow or took extr

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html