AgentHubAgentHub

EPICS Channel Access MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.K-Dense-AI/labmcp-epics · v0.1.2

MCP server for EPICS Channel Access: read, monitor and guarded writes of process variables.

View on MCP Registry ↗Repository ↗

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

MCP server for EPICS Channel Access: read, monitor and guarded writes of process variables. EPICS Channel Access is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

Code review & GitHubCursor essentials

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "labmcp-epics": {
      "command": "uvx",
      "args": [
        "labmcp-epics"
      ]
    }
  }
}

Setup tutorial

  1. Open the EPICS Channel Access page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add labmcp-epics -- uvx labmcp-epics

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "labmcp-epics": {
      "command": "uvx",
      "args": [
        "labmcp-epics"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "labmcp-epics": {
      "command": "uvx",
      "args": [
        "labmcp-epics"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "labmcp-epics": {
      "command": "uvx",
      "args": [
        "labmcp-epics"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "labmcp-epics": {
      "command": "uvx",
      "args": [
        "labmcp-epics"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "labmcp-epics": {
      "command": "uvx",
      "args": [
        "labmcp-epics"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "labmcp-epics": {
      "command": "uvx",
      "args": [
        "labmcp-epics"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "labmcp-epics": {
      "command": "uvx",
      "args": [
        "labmcp-epics"
      ]
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "labmcp-epics": {
      "command": "uvx",
      "args": [
        "labmcp-epics"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "labmcp-epics": {
      "command": "uvx",
      "args": [
        "labmcp-epics"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for EPICS Channel Access

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for EPICS Channel Access?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

EPICS Channel Access requires environment variables (LABMCP_ADDRESS、LABMCP_SIMULATE、LABMCP_READ_ONLY、LABMCP_LIMITS). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "API_KEY": "your_actual_key_here"
  }
}
Still not connecting? Read the MCP troubleshooting guide →

Tool Mock Playground

Sandbox

EPICS Channel Access Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: labmcp_epicsExecute the core tool interface of EPICS Channel Access
Request ArgumentsJSON Schema
{
  "target": "EPICS Channel Access",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

EPICS Channel Access + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Browse more like thisSearch similarPick by scenarioPrompt playbooksMCP hands-onReviews & comparisons

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: EPICS Channel Access
HTML
<a href="https://myagenthub.cn/p/io.github.K-Dense-AI/labmcp-epics" title="Listed on AgentHub: EPICS Channel Access" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.K-Dense-AI/labmcp-epics?lang=en" alt="Listed on AgentHub: EPICS Channel Access" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: EPICS Channel Access](https://myagenthub.cn/badge/io.github.K-Dense-AI/labmcp-epics?lang=en)](https://myagenthub.cn/p/io.github.K-Dense-AI/labmcp-epics)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.K-Dense-AI/labmcp-epics",
  "type": "mcp-server",
  "version": "0.1.2",
  "displayName": "EPICS Channel Access",
  "description": "MCP server for EPICS Channel Access: read, monitor and guarded writes of process variables.",
  "repository": {
    "url": "https://github.com/K-Dense-AI/lab-instrument-mcps",
    "source": "github",
    "subfolder": "servers/protocols/epics"
  },
  "homepage": "https://github.com/K-Dense-AI/lab-instrument-mcps/tree/main/servers/protocols/epics",
  "distribution": {
    "packages": [
      {
        "registryType": "pypi",
        "identifier": "labmcp-epics",
        "version": "0.1.2",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "LABMCP_ADDRESS",
            "description": "Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025"
          },
          {
            "name": "LABMCP_SIMULATE",
            "description": "Set to 1 to use the built-in simulator (no hardware)"
          },
          {
            "name": "LABMCP_READ_ONLY",
            "description": "Set to 1 to disable all state-changing tools"
          },
          {
            "name": "LABMCP_LIMITS",
            "description": "Safety limit overrides, e.g. max_temperature_c=80"
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.K-Dense-AI/labmcp-epics",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.K-Dense-AI%2Flabmcp-epics/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}
EPICS Channel Access MCP Setup & Guide - AgentHub