Store one entry in the bridge for later retrieval or coordination.

Use this tool when you want to persist a compact memory record or write a signal that another workflow can poll later. Write durable knowledge as kind="memory" and transient coordination events as kind="signal".

Returns the stored entry identifier, timestamp, and duplicate information. Repeated memory writes may deduplicate; signal writes are intended to remain append-like.

Recall matching entries or poll for new signals from the bridge.

Use this tool to search durable memory, filter by metadata, or poll for fresh coordination signals. For issue-like work, prefer project and domain recall before external search. For workflow polling, pass since, an empty query, and kind="signal".

Empty-query Signal recall returns a next_since cursor for the next polling cycle; other recall modes return next_since=null. The cursor tracks later insertions, not status changes to older Signals.

Browse recent items when you do not yet know what to search for.

Use this tool to inspect a namespace by filters alone. It is useful when you want to see recent memory, scan a domain bucket, or confirm that signals are flowing before writing a more specific recall query.

Return a quick health summary for one namespace.

Use this tool when you want to inspect what is in the bridge without opening SQLite directly. It returns total item count, a kind breakdown, top domains, and the oldest and newest entry timestamps for the namespace.

Delete one stored entry by id.

Use this tool to remove a bad memory, an accidental write, or a signal that should no longer exist. The response tells you whether anything was deleted and returns the removed item metadata when a match is found.

Record structured retrieval feedback for one recalled memory result.

Evidence is append-only/shadow-only. Provenance is caller-declared and not authenticated. This tool does not mutate memory records, recall results, or ranking behavior.

Manually promote one stored memory to a stronger durable record type.

Use this tool when you know a record should be treated as a learn, gotcha, or domain note even if the reflex layer has not promoted it yet. Promotion keeps the same id and updates the stored title, tags, and structured content in place.

Explicitly enrich one durable memory without pretending the write was a new fact.

Use this after store reports duplicate_with_new_metadata. The original content remains unchanged; title/tag changes and additional provenance are written to an auditable annotation record.

Create a new durable memory that explicitly supersedes an older record.

The predecessor remains available for audit. The bridge adds an exact supersedes edge and records the revision receipt instead of silently mutating content in place.

Export bridge content into a readable or portable format.

Use this tool when you want to inspect a namespace outside the MCP client, create a human-readable snapshot, or move memory into another system without opening the database directly.

Start one explicit, stateless run and return server-minted run/work-item IDs.

The bridge does not retain an implicit current run. Callers must pass the returned handles to later event, read, and completion calls. Idempotent retries return the same handles and reject conflicting payloads.

Append one structured event to a run's durable authority ledger.

Sequence allocation, event persistence, child work-item creation, and projection updates occur in one transaction. This tool never sets an implicit current run.

Read current run/work-item projections plus append-only events for reconnect or compaction recovery.

Append or correct a run outcome without changing memory ranking or policy.

On new runs, verified_success requires a matching current server-minted governed receipt. Outcome corrections form an append-only supersession chain.

Claim one signal with a short lease for lightweight work coordination.

Use this when a worker should take ownership of a pending signal before it acts. If signal_id is omitted, the bridge claims the next eligible signal in the namespace that matches the optional filters, with a small fairness bias inside the oldest pending window so one polling consumer does not keep winning by accident.

Extend the active lease on one claimed signal.

Use this when a worker still owns a signal but needs more time before another consumer can reclaim it. Expired leases cannot be extended; those signals must be reclaimed instead. Hard signal expiry still takes precedence over lease renewal.

Acknowledge one claimed or pending signal so downstream polling can stop treating it as active work.