Der zerm MCP-Server,
verbunden mit einem Klick.

“Nutze „kv_set“: Store a value durably under (namespace, key) with a TTL. Survives across your sessions - use it as memory between stateless runs. Value must.”

“Nutze „kv_get“: Retrieve a value previously stored with kv_set. Call this at the start of a run to restore state, preferences, or progress saved by earlier.”

“Nutze „kv_delete“: Permanently remove one key from your namespace, freeing a slot against the 1000-key limit. Use it when a stored value is wrong or unwanted b.”

“Nutze „kv_list“: List the keys held in your namespace, optionally narrowed to those starting with a prefix. Use it to discover what earlier runs saved before.”

kv_set — Store a value durably under (namespace, key) with a TTL. Survives across your sessions - use it as memory between stateless runs. Value must

kv_get — Retrieve a value previously stored with kv_set. Call this at the start of a run to restore state, preferences, or progress saved by earlier

kv_delete — Permanently remove one key from your namespace, freeing a slot against the 1000-key limit. Use it when a stored value is wrong or unwanted b

kv_list — List the keys held in your namespace, optionally narrowed to those starting with a prefix. Use it to discover what earlier runs saved before

timer_verify_origin — One-time consent handshake before timers can deliver to an origin. Prerequisite: an HTTPS endpoint you control that can read a request body

timer_schedule — Schedule a durable callback: at fire time this service POSTs your JSON payload to your URL. Use it to wake up future runs of yourself or you

timer_cancel — Cancel a pending timer using the id returned by timer_schedule. The id is the authorization: holding it is what proves you scheduled the tim

timer_status — Check a timer by the id returned by timer_schedule: status (pending|delivering|delivered|failed|cancelled), attempts, last error. Returns fo