MCP.so
Sign In

EPICS-MCP-Server

@Jacky1-Jiang

About EPICS-MCP-Server

No overview available yet

Basic information

Category

Other

License

MIT

Runtime

python

Transports

stdio

Publisher

Jacky1-Jiang

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is EPICS-MCP-Server?

EPICS-MCP-Server is a Python-based server that integrates with EPICS (Experimental Physics and Industrial Control System) to interact with process variables (PVs). It provides tools for retrieving and setting PV values and fetching detailed PV information, and communicates over stdio using the mcp framework.

How to use EPICS-MCP-Server?

Install dependencies with pip install -r requirements.txt. Ensure EPICS is installed locally and an IOC is running with caget, caput, and cainfo working. Use with Langchain by configuring StdioServerParameters with command="python" and the path to the server script.

Key features of EPICS-MCP-Server

  • Retrieve the current value of any EPICS PV via get_pv_value
  • Set a new value for any EPICS PV via set_pv_value
  • Fetch detailed information about any EPICS PV via get_pv_info
  • Returns JSON status objects for each operation (success or error)
  • Built on the mcp framework for easy integration

Use cases of EPICS-MCP-Server

  • Monitoring hardware parameters in accelerator or experimental control systems
  • Controlling software or hardware parameters by setting PV values remotely
  • Integrating EPICS PV access into AI‑powered workflows via tools like Langchain

FAQ from EPICS-MCP-Server

What are the runtime dependencies?

EPICS base must be installed locally, and the Python dependencies listed in requirements.txt must be installed. The server requires a running EPICS IOC with PVs accessible via caget, caput, and cainfo.

How does the server communicate?

It communicates over stdio using the mcp (Model Context Protocol) framework. This makes it suitable for local subprocess usage in tools like Langchain.

Do I need an EPICS IOC running?

Yes, before using the server you must have an IOC started that serves the process variables you intend to query or modify. The standard EPICS shell commands (caget, caput, cainfo) must work correctly.

What transport or authentication is used?

No authentication is implemented. The server uses stdio transport and is intended for local integration, not remote network access.

Comments

More Other MCP servers