Particles MCP server

linkedparticles

linkedparticles.org · docs.linkedparticles.org · PyPI · Apache-2.0

<!-- Ownership proof for the official Model Context Protocol registry: the registry matches this token against the server name in server.json before it will accept a listing for the linkedparticles PyPI package. Keep it byte-identical to server.json's name. --> <!-- mcp-name: org.linkedparticles/particles -->

Particles is shared memory for humans and AI agents. Each particle is one

claim, plus what you need to judge it: who said it, where, when, and how

confident they were. Facts, opinions, and memories are all claims, recorded

the same way as particles. Particles are not edited or deleted. Particles are

superseded, retracted, or disputed in the open. How much to trust it is a

perspective applied at query time, never baked into the record.

linkedparticles is the Engine of the Particles reference implementation — the package you install to actually run a belief store. Give it documents, pages, chat logs, or an agent's own session notes; get back claim-granularity beliefs, each carrying calibrated confidence, an uncertainty kind, a resolved subject, and provenance back to the exact source bytes. Ask a question and the answer cites the beliefs it was built from. Nothing is ever overwritten, so you can ask the store what it believed a year ago and why it stopped.

When your agent is wrong, you can see exactly why, and fix it at the source.

The Engine is a library first. The HTTP API, the CLI, the read-only MCP server, and the resident daemon are all surfaces over it.

Install

pip install linkedparticles

Python 3.11+. linkedparticles-core — the store-free Client layer — is pulled in automatically.

Sixty seconds

export ANTHROPIC_API_KEY=sk-ant-...
particles db init

# Deposit a source — file, URL, or literal text — into the append-only corpus
particles deposit https://en.wikipedia.org/wiki/Pluto

# Extract claim-granularity beliefs with confidence, subjects, and provenance
particles extract --all-pending

# Ask in natural language; the answer cites the particles behind it
particles query "Why is Pluto not a planet?"

# Health-check the store: contradictions, staleness, orphaned links
particles lint

Because nothing is overwritten, the store can replay its own history. --as-of is the assertion-time lens — what did the store believe at T, and why did it stop — not what was true of the world at T:

particles query "How many planets are in the Solar System?" --as-of 2000-01-01
# → the belief as it stood then, and why it no longer stands: SUPERSEDED,
#   retired 2006-08-24, superseded by "Pluto is a dwarf planet."

There is a clickable version of that belief history on the front door. Step by step: getting started, then as-of time travel.

Wiring it into an agent

particles mcp serve                 # read-only MCP server (stdio), any MCP client
particles init claude-code          # session-start digest, session-end harvest
particles engine serve              # HTTP API, for a shared or remote engine
particles export obsidian ./vault   # also: anki, wiki, logseq, notion, graph, jsonl

It can also stand in for the reference memory server, and it plugs into LangChain as a retriever and a tool set — see Claude Code memory, swapping in for the reference memory server, and using from LangChain.

Does it hold up?

Shortened. The full README is on GitHub.