Particles — Claude Code MCP server: features and setup
Particles gives agents read access to a history of claims with sources, dates, and confidence scores. Use it when you need to inspect the evidence behind an answer.
claude mcp add --env ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY> --env DATABASE_URL=<DATABASE_URL> --env PARTICLES_CONFIG=<PARTICLES_CONFIG> --transport stdio particles -- uvx linkedparticlesWhat Particles does
Particles stores claims as separate records, along with their sources, dates, confidence, and links to the original material. Records are not overwritten; they can be retracted, disputed, or superseded. The MCP server is read-only, so use the engine and its commands, such as particles deposit and particles extract, to populate the store.
The server can return answers that cite the claims behind them. Use --as-of to query the store’s belief history at a given time. Claim extraction and written answers call a language model. The setup example uses ANTHROPIC_API_KEY; OpenAI-compatible endpoints are supported too. Python 3.11 or later is required.
What it helps with
- store claims with their sources and dates
- inspect which records support an agent’s answer
- retrieve the store’s beliefs as of a given date
- find contradictions and stale records with
particles lint
Example prompts for the agent
- Answer using claims in the store and cite the supporting sources.
- Show what the store believed on
2000-01-01. - Check the store for contradictory or stale claims.
How to install Particles
Platform CLI
claude mcp add --env ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY> --env DATABASE_URL=<DATABASE_URL> --env PARTICLES_CONFIG=<PARTICLES_CONFIG> --transport stdio particles -- uvx linkedparticlesReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from linkedparticles <command>
Platform CLI
codex mcp add particles --env ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY> --env DATABASE_URL=<DATABASE_URL> --env PARTICLES_CONFIG=<PARTICLES_CONFIG> -- uvx linkedparticlesReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from linkedparticles <command>
Config file
{
"mcpServers": {
"particles": {
"command": "uvx",
"args": [
"linkedparticles"
],
"env": {
"ANTHROPIC_API_KEY": "<ANTHROPIC_API_KEY>",
"DATABASE_URL": "<DATABASE_URL>",
"PARTICLES_CONFIG": "<PARTICLES_CONFIG>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from linkedparticles <command>
Config file
{
"servers": {
"particles": {
"type": "stdio",
"command": "uvx",
"args": [
"linkedparticles"
],
"env": {
"ANTHROPIC_API_KEY": "<ANTHROPIC_API_KEY>",
"DATABASE_URL": "<DATABASE_URL>",
"PARTICLES_CONFIG": "<PARTICLES_CONFIG>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from linkedparticles <command>
Platform CLI
gemini mcp add -e ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY> -e DATABASE_URL=<DATABASE_URL> -e PARTICLES_CONFIG=<PARTICLES_CONFIG> particles uvx linkedparticlesReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from linkedparticles <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Particles
How do I install Particles in Claude Code?
Run claude mcp add particles -e ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY> -- uvx linkedparticles. Set ANTHROPIC_API_KEY for this setup.
What does Particles do?
It gives an agent read access to a store of claims with sources, dates, and confidence scores. Answers can cite the records they rely on.
Does Particles need an API key?
Claim extraction and written answers use a language model. The setup example uses ANTHROPIC_API_KEY, and OpenAI-compatible endpoints are also supported.
