A Model Context Protocol server that lets Claude Desktop, IDEs, and other MCP clients look up particle properties and decay modes.
ParticlePhysics MCP server exists for a simple reason — assistants are far more useful when they can act on ParticlePhysics directly instead of describing what you should do. A Model Context Protocol server that lets Claude Desktop, IDEs, and other MCP clients look up particle properties and decay modes.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Once ParticlePhysics is connected, these are the calls the assistant has available:
search_particle — 1. mu Name: mu+ PDG ID: -13 PDG Review ID: S004/2025 Mass: 105.6583755 MeV (0.1056583755 GeV) Spin (J): 1/2 Charge: 1 Color: singlet Quantum numberslist_decays — Same identifier formats as search_particle. Tries exclusive_branching_fractions → branching_fractions → inclusive_branching_fractions and reportsAmong the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. ParticlePhysics's toolset — search_particle, list_decays — is a fair guide to whether it matches your workflow. It is maintained by uzerone; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search_particle | 1. mu Name: mu+ PDG ID: -13 PDG Review ID: S004/2025 Mass: 105.6583755 MeV (0.1056583755 GeV) Spin (J): 1/2 Charge: 1 Color: singlet Quantum numbers: J=1/2 Lifetime: 2.196981148893498e-06 |
| list_decays | Same identifier formats as search_particle. Tries exclusive_branching_fractions → branching_fractions → inclusive_branching_fractions and reports which source it used. Returns an empty decay list with stable=true for sta |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.