MCP server for EPICS: live PV values, connection diagnosis, and cross-plane provenance
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"epics-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# EPICS MCP [](https://github.com/epicDirk/EPICS-MCP/actions/workflows/ci.yml) [](https://pypi.org/project/epics-mcp/) [](https://github.com/epicDirk/EPICS-MCP/blob/main/LICENSE) [](https://www.python.org/) Ask an AI assistant about your EPICS control system. What is this PV reading right now? Why is it disconnected? Which operator screens and trends show this device, and is it archived and alarm-configured? The server exposes your EPICS layer as **Model Context Protocol (MCP)** tools over [p4p](https://mdavidsaver.github.io/p4p/), so an assistant can answer those the way an operator would, instead of you clicking through CS-Studio, the Archiver Appliance UI and ChannelFinder by hand. **Read-only by default.** `set_pv_value` is triple-gated: an env switch, a required regex allowlist, and a rate limit. A value outside the record's own drive limits is refused after those three have admitted the write, which is a further refusal and not a fourth gate. Logbook writes sit behind their own separate gate, of six checks. The fullest statement of the posture, including what leaves your machine, is [Safety and network posture](https://github.com/epicDirk/EPICS-MCP/blob/main/docs/safety.md). > **Project status.** Pre-1.0 and under active development. Tools and APIs may still change > between minor versions, so pin one if you depend on it. ## Where to start **I want to try it, and I have no control system.** Install it (below), then follow the [quick start](https://github.com/epicDirk/EPICS-MCP/blob/main/docs/quick-start.md): three commands, and `epics-testpv` serves the PV for you, so there is nothing else to obtain. No facility, no IOC, no EPICS Base, no ChannelFinder, no archiver. **I want to point it at…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.