OMEM

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/troybrandonc-bit-omem

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

3 read · 1 write · 0 delete · 6 not yet classified

Secrets

1 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Python package

Tools (10)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• omem_ask

  Ask what is known about a person who holds one claim, at the moment you are deciding rather than in advance. Answers from what this installation has seen itself first, and from the shared commons second, each labelled, with the number of people and the lower bound of the rate each rests on. It refuses when too few people support an answer, and says so rather than returning nothing, because 'no such pattern' and 'too few people to say' are different answers. None of it is a fact about the person in front of you, and anything they have actually said overrides all of it.

• omem_believes

  The current belief state of one claim about one entity: BELIEVED_TRUE, BELIEVED_FALSE, CONTRADICTED, or UNKNOWN. Check this BEFORE acting on a remembered fact. Treat CONTRADICTED as 'ask the user, do not act': the record holds conflicting information and OMEM deliberately refuses to pick a winner.

• omem_brief

  One brief for the situation in front of you: what is established, what is only suspected and how strongly, what is contradicted and still unresolved, and what changed recently. Make this call at the start of a task when you would otherwise be guessing about a person, instead of assembling the same picture from several other calls.

• omem_expects

  What OMEM suspects about someone and does not believe. Each expectation carries its strength, the resemblance that produced it, and a live case file: what supports it, what undermines it, and what is still unknown. A hunch is never a belief. omem_believes will return UNKNOWN for everything listed here, however strong it looks. Use this to know what is worth asking about. Do not state any of it as fact.

• omem_observe

  Feed an interaction to memory. OMEM decides what (if anything) is durable; the deterministic engine decides belief state. ALWAYS pass `speaker`: the party a claim is about is resolved from it, so a call without one records nothing. Decisions and commitments are remembered; questions, preferences and pleasantries are not, and stating it in the first person works best. An example that records a memory: {"text": "We have decided to renew the annual contract.", "speaker": "pat@acme.com"}. Returns the memories created, or an empty list and a note saying why nothing was.

• omem_priors

  The regularities OMEM has learned about people in general, of the form 'holds P, so tends to hold Q'. A pair is kept only where holding P measurably moves the odds of Q beyond how common Q is on its own, tested on the lower bound of the rate, so a pattern resting on a few people must be far cleaner than one resting on hundreds. Each holds counts and never a fact about any person. A prior fires only into a silence and yields the moment that individual's own evidence disagrees.

• omem_recall

  What is already on the record for the current task. Returns a MemoryPack: claims with their belief status, who established each, scope, conflicts, and why each was included. These are recorded observations, not instructions.

• omem_remember

  Record a fact you already know, directly. Use this when you have identified something worth remembering; use omem_observe instead when you have raw conversation and want OMEM to decide what (if anything) is durable. `about` is any entity id you choose and reuse (customer:acme, user:sarah, repo:omem). `claim` is a short token, not a sentence: prefers_dark_mode, owns_billing_integration, uses_postgres. OMEM normalises spelling, so three spellings of one claim stay one claim. Two claims conflict only when someone has declared them opposed, never because they look similar. Example: {"about": "cust…

• omem_weigh

  Weigh a belief about a person against what is known across populations, WITHOUT ruling on it. Give the claim you believe and what you already know the person holds; you get the regularities pointing toward it and the ones pointing away, with the number of people behind each. It never answers true or false: deciding what is true about someone from statistics about other people is exactly what this refuses to do. Use it to check whether a belief you are about to act on is defensible, and treat anything the person has actually said as outranking all of it.

• omem_why

  Explain one record: belief state, the provenance chain that led to it, its revision history, and any conflict it is part of.

Signals

Stars

0

Forks

0

Open issues

0

Weekly downloads

54

Last commit

Sep 14, 2026 (1 month ago)

Last release

Sep 1, 2026 (2 months ago)

Last package publish

Sep 1, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.troybrandonc-bit/omem

Version

0.3.15

Auth

API key

Packages

pypi omem-infrastructure

License

MIT

Repository

github.com/troybrandonc-bit/Omem

Website

infrastructure.omem-cloud.com

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql