dev.tmpstate/tmpstate

Where it sits in the directory's order

What can be seen from outside, weighed as the directory publishes.

Where it answers

• https://tmpstate.dev/mcpstreamable-http

The tools it lists (16, as of 2 days ago)

The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.

• 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. 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.