tmpstate

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.

{
  "type": "object",
  "properties": {
    "idempotency_key": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Stable retry key. Reusing it from the same client returns the same database."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

{
  "type": "object",
  "properties": {
    "db": {
      "type": "string",
      "description": "The database URL returned at creation (or its bare s-... capability)."
    }
  },
  "required": [
    "db"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {
    "db": {
      "type": "string",
      "description": "The database URL returned at creation (or its bare s-... capability)."
    },
    "collection": {
      "type": "string",
      "description": "Collection name (created implicitly on first write)."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    },
    "cursor": {
      "type": "string",
      "description": "next_cursor from the previous page."
    }
  },
  "required": [
    "db",
    "collection"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

{
  "type": "object",
  "properties": {
    "db": {
      "type": "string",
      "description": "The database URL returned at creation (or its bare s-... capability)."
    },
    "collection": {
      "type": "string",
      "description": "Collection name (created implicitly on first write)."
    },
    "id": {
      "type": "string",
      "description": "Document id (doc_...)."
    }
  },
  "required": [
    "db",
    "collection",
    "id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

{
  "type": "object",
  "properties": {
    "db": {
      "type": "string",
      "description": "The database URL returned at creation (or its bare s-... capability)."
    },
    "collection": {
      "type": "string",
      "description": "Collection name (created implicitly on first write)."
    },
    "data": {
      "type": "object",
      "additionalProperties": {},
      "description": "The document: a JSON object."
    }
  },
  "required": [
    "db",
    "collection",
    "data"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

{
  "type": "object",
  "properties": {
    "db": {
      "type": "string",
      "description": "The database URL returned at creation (or its bare s-... capability)."
    },
    "collection": {
      "type": "string",
      "description": "Collection name (created implicitly on first write)."
    },
    "id": {
      "type": "string",
      "description": "Document id (doc_...)."
    },
    "patch": {
      "type": "object",
      "additionalProperties": {},
      "description": "Top-level fields to merge."
    }
  },
  "required": [
    "db",
    "collection",
    "id",
    "patch"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

{
  "type": "object",
  "properties": {
    "db": {
      "type": "string",
      "description": "The database URL returned at creation (or its bare s-... capability)."
    },
    "collection": {
      "type": "string",
      "description": "Collection name (created implicitly on first write)."
    },
    "id": {
      "type": "string",
      "description": "Document id (doc_...)."
    }
  },
  "required": [
    "db",
    "collection",
    "id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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

{
  "type": "object",
  "properties": {
    "db": {
      "type": "string",
      "description": "The database URL returned at creation (or its bare s-... capability)."
    },
    "collection": {
      "type": "string",
      "description": "Collection name (created implicitly on first write)."
    }
  },
  "required": [
    "db",
    "collection"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {
    "db": {
      "type": "string",
      "description": "The database URL returned at creation (or its bare s-... capability)."
    },
    "confirm": {
      "type": "string",
      "const": "true",
      "description": "Pass \"true\" only after the user has seen that deletion is immediate and irreversible and approved."
    }
  },
  "required": [
    "db"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {
    "db": {
      "type": "string",
      "description": "The database URL returned at creation (or its bare s-... capability)."
    },
    "plan": {
      "type": "string",
      "enum": [
        "week",
        "month",
        "quarter"
      ]
    }
  },
  "required": [
    "db"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {
    "pro_token": {
      "type": "string",
      "description": "Pro account token (pt_...). Optional if the MCP connection already sends Authorization: Bearer pt_..."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {
    "pro_token": {
      "type": "string",
      "description": "Pro account token (pt_...). Optional if the MCP connection already sends Authorization: Bearer pt_..."
    },
    "accept_overage_usd": {
      "type": "string",
      "description": "Explicit overage consent, e.g. \"1.50\", only after the user approved."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {
    "pro_token": {
      "type": "string",
      "description": "Pro account token (pt_...). Optional if the MCP connection already sends Authorization: Bearer pt_..."
    },
    "db": {
      "type": "string",
      "description": "The database URL returned at creation (or its bare s-... capability)."
    },
    "accept_overage_usd": {
      "type": "string"
    }
  },
  "required": [
    "db"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {
    "pro_token": {
      "type": "string",
      "description": "Pro account token (pt_...). Optional if the MCP connection already sends Authorization: Bearer pt_..."
    },
    "confirm": {
      "type": "string",
      "const": "cancel",
      "description": "Pass \"cancel\" only after the user has seen the consequences and approved."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {
    "message": {
      "type": "string",
      "minLength": 1,
      "maxLength": 4000,
      "description": "What was missing, confusing, or slow - or what worked well. Plain text, one short message."
    },
    "category": {
      "type": "string",
      "enum": [
        "missing_feature",
        "friction",
        "docs",
        "performance",
        "bug",
        "praise",
        "other"
      ],
      "description": "Optional bucket for triage."
    }
  },
  "required": [
    "message"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}