Lake Shore Temperature Controller — MCP Server

Let an AI agent read every sensor on your cryostat, check heater status, set setpoints, ramps, heater ranges and PID values, wait for the temperature to settle, and switch all heaters off on Lake Shore Cryotronics Model 335, 336 and 350 temperature controllers.

Try it without hardware

uvx labmcp-lakeshore --simulate --check
uvx labmcp-lakeshore --simulate --option sim_model=350 --option sim_speed=20 --check

The simulator models a small cryostat at 4.2 K: a stage (inputs A diode and C Cernox-like, heated by output 1) and a sample (input B Pt-100, heated by output 2), with Lake Shore's PID law and setpoint ramping. sim_speed makes simulated time run faster than real time.

Connect your controller

The model is detected from *IDN?; other Lake Shore models (325, 331, 340, 372, ...) are refused.

1. Pick the interface in the controller's Interface menu (only one remote interface is active at a time).
2. USB: install the Lake Shore USB driver (Windows Update, or lakeshore.com). The port runs at a fixed 57600 baud, 7 data bits, odd parity, 1 stop bit; the server sets this automatically.
3. Ethernet (336, 350): configure the IP address on the front panel; the command port is TCP 7777 (two connections at most).
4. Test the connection:

   uvx labmcp-lakeshore --address /dev/ttyACM0 --check          # Linux
   uvx labmcp-lakeshore --address /dev/tty.usbmodemXXXX --check # macOS
   uvx labmcp-lakeshore --address COM5 --check                  # Windows
   uvx labmcp-lakeshore --address tcp://192.168.1.40:7777 --check
   uvx labmcp-lakeshore --address GPIB0::12::INSTR --check
   

Add to your MCP client

Claude Code

claude mcp add cryostat -- uvx labmcp-lakeshore --address tcp://192.168.1.40:7777

Claude Desktop / Cursor / Windsurf (claude_desktop_config.json, .cursor/mcp.json, …)

{
  "mcpServers": {
    "cryostat": {
      "command": "uvx",
      "args": ["labmcp-lakeshore", "--address", "tcp://192.168.1.40:7777"]
    }
  }
}

Add --read-only to allow reading temperatures and heater status but block setpoint, ramp, range and PID changes (all_heaters_off stays available). For other clients, generate the snippet with uvx labmcp config lakeshore --address tcp://192.168.1.40:7777 --client vscode (also cursor, codex, claude-code).

Tools

get_connection_info, get_command_log and reconnect are built into every LabMCP server.

Safety limits

Override at launch: --limit max_setpoint_k=420 --limit max_heater_range=2.

Example prompts

• "Read all the temperatures and tell me if any sensor has an error."
• "Ramp output 1 to 77 K at 2 K/min on the medium range, then wait until input A has been within 50 mK for 5 minutes."
• "Step the sample from 10 K to 300 K in 10 K steps and tell me when each step is stable." (with max_setpoint_k high enough)
• "What are the PID settings on loop 1? Reduce P to 30 and keep I and D."
• "Something's wrong - turn all heaters off."

Notes

• Setting a setpoint does not start heating; the heater range does. With a range above 0 an output heats as its PID loop demands (closed loop) or at the manual output (open loop). Output modes and control inputs are configured on the front panel; the server does not change them, since pointing a loop at the wrong sensor can cause a thermal runaway.
• Setpoints are always given in kelvin. SETP uses the preferred units of the loop's control input: the server converts for Celsius and refuses when the input is set to sensor units.
• Every command is followed by *ESR?; command (CME) and execution (EXE) errors are reported instead of being ignored. The server leaves at least 50 ms between messages, as the manuals require (--option min_interval_s=).
• get_heater_status reads HTRST?, which clears a latched heater open/short error on the controller.
• wait_for_stable_temperature needs the setpoint to have stopped ramping (RAMPST?) as well as the temperature to be in tolerance. all_heaters_off stops a running wait.
• all_heaters_off sends RANGE n,0 to every output and reads it back, like the front-panel All Off key. Every output is tried even if another fails; all_off is true only when every output read back as off. It does not change setpoints or output modes. Consider also setting a hardware temperature limit (TLIMIT, front panel) as a last line of defence.
• The 3062 scanner option (inputs D1-D5), zone tables, autotune, curves, alarms and relays are not exposed. The Model 372 AC resistance bridge was not verified and is refused at connect time.

Hardware verification