Tmpstate

dev.tmpstatePublished by tmpstate.devOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDatabasesProductivity & Workflow

Overview

AI-generated overview

A remote zero-key temporary JSON database for agents: create a database in one call and read, write, extend or delete documents through tools.

What you can do
Create and manage temporary JSON databases, check usage, limits and expiry, and extend or destroy them, including paying for more time via a checkout link the user approves. List, read, create, update and delete documents in implicitly created collections, with cursor paging. Delete whole collections or databases at once. Manage a Pro account: start a subscription checkout, list and create always-on databases, attach existing databases, and cancel. Optionally send free-form feedback about the experience.
When to use it
Useful when an assistant needs a small throwaway JSON store for a project or task without signup, keys or OAuth, and wants it to expire automatically after about a day unless extended or upgraded.
Requirements
A remote endpoint at tmpstate.dev over streamable HTTP; no packages, environment variables or headers declared. The database URL returned by create_database acts as the only credential and must be persisted by the client. Paying for extensions or Pro requires a browser and a Stripe checkout.
Before you install
The database URL is the sole credential, so anyone holding it can read and write the data; persist it carefully and use delete_database to revoke a leaked URL. Deletions of documents, collections and databases are irreversible, and cancelling Pro schedules deletion of all databases on the account. Extending and Pro checkout involve real payments via Stripe and should only proceed with the user's explicit approval; overage beyond the included allotment costs extra.

Installation

In SourceWeft

  1. Open Tmpstate in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.tmpstate%2Ftmpstate/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tmpstate": {
      "type": "http",
      "url": "https://tmpstate.dev/mcp"
    }
  }
}

Tools

16

create_database

Create a temporary 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.

Parametersidempotency_key

database_status

Database status

Usage, limits, tier and expiry for a database (GET $DB/__meta equivalent).

Parametersdbrequired

list_documents

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.

Parametersdbrequiredlimitcursorcollectionrequired

get_document

Get a document

Read one document by id. The stored fields are under .data.

Parametersdbrequiredidrequiredcollectionrequired

create_document

Create a document

Insert a JSON object into a collection (collections are created implicitly). Counts against the write and document quotas.

Parametersdbrequireddatarequiredcollectionrequired

update_document

Update a document

Shallow-merge a patch into a document (top-level keys overwrite; keys are never deleted). Counts against the write quota.

Parametersdbrequiredidrequiredpatchrequiredcollectionrequired

delete_document

Delete a document

Delete one document. Never blocked by quotas; frees a document slot. Emptying a whole collection? Use delete_collection instead of looping this.

Parametersdbrequiredidrequiredcollectionrequired

delete_collection

Delete a collection

Delete every document in a collection at once (useful to re-seed). Irreversible. To destroy the entire database, use delete_database instead.

Parametersdbrequiredcollectionrequired

delete_database

Delete the whole 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 states the consequences; show them to the user and only retry with confirm="true" after their explicit approval. Afterwards remove the db URL from wherever you persisted it.

Parametersdbrequiredconfirm

extend_database

Extend a database (one-time payment)

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 paid, call database_status: the new expiry and tier confirm the extension.

Parametersdbrequiredplan

pro_checkout

Start a Pro subscription

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.

Takes no parameters.

pro_list_databases

List Pro 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.

Parameterspro_token

pro_create_database

Create a Pro 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.

Parameterspro_tokenaccept_overage_usd

pro_attach_database

Upgrade a database to Pro (in place)

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.

Parametersdbrequiredpro_tokenaccept_overage_usd

pro_cancel

Cancel the Pro subscription

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.

Parametersconfirmpro_token

send_feedback

Send feedback to the TmpState team

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 extra requests is genuinely useful. This is about your own experience, so no human approval is needed; if your user volunteers feedback too, relay it and say it came from them. Never include database URLs, capabilities, or Pro tokens - capability-shaped strings are redacted server-side.

Parametersmessagerequiredcategory

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.