Skip to main content

Tecan Cavro Syringe Pump — MCP Server

Let an AI agent initialize, aspirate and dispense microlitre volumes at set flow rates, switch valve ports and stop Tecan Cavro OEM syringe pumps through the documented Cavro Data Terminal (DT) protocol.

Package labmcp-cavro
Instruments Cavro XLP 6000, Cavro XMP 6000, Cavro XCalibur (with 3-port, 4-port or distribution valves, or valveless)
Interfaces RS-232, RS-485 (with an RS-485 adapter), serial-to-Ethernet adapters
Protocol Cavro DT protocol (XLP 6000 Operating Manual, 734237-C, chapter 3 and appendix G); step resolution per Tecan XCalibur / XMP 6000 specifications
Status 🧪 simulated: tested against a wire-level simulator, not yet verified on hardware. Report a hardware test

Try it without hardware

uvx labmcp-cavro --simulate --check

The simulator is an XLP 6000 with a 1 mL syringe and a 3-port valve. Moves take real time; add --option sim_speed=10 to speed it up.

Connect your pump

  1. Pump setup: set the address switch (switch 0 is DT address 1, switch 1 is 2, … switch 8 is 9, switches 9–E are : ; < = > ?). The pump detects DT versus OEM protocol from the first message after power-up. The default is 9600 baud, 8N1; 38400 baud is selected with the U47 configuration command.
  2. Tell the server what is installed. The pump cannot report its syringe, so these options are required on real hardware:
    • --option syringe_ul=1000: syringe volume in µL.
    • --option model=xlp6000 (or xmp6000, 6000 increments per stroke; xcalibur, 3000). For another DT-compatible pump, give --option steps_per_stroke=<increments per full stroke in standard mode> instead.
    • Optional: --option resolution=fine (N1, 8× finer volume steps; applied by initialize) and --option pump_address=2.
  3. Find the port: uvx labmcp ports
  4. Test the connection:
    uvx labmcp-cavro --address /dev/ttyUSB0 --option syringe_ul=1000 --option model=xcalibur --check
    uvx labmcp-cavro --address COM3 --option syringe_ul=500 --option model=xlp6000 --check
    
    Non-default baud rates go in the address: serial://COM3?baudrate=38400.

Add to your MCP client

Claude Code

claude mcp add cavro -- uvx labmcp-cavro --address /dev/ttyUSB0 --option syringe_ul=1000 --option model=xcalibur

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

{
  "mcpServers": {
    "cavro": {
      "command": "uvx",
      "args": ["labmcp-cavro", "--address", "/dev/ttyUSB0",
               "--option", "syringe_ul=1000", "--option", "model=xcalibur"]
    }
  }
}

Add --read-only to allow status reads but block every move.

Tools

Tool Kind Description
aspirate_ul ⚠️ hazard Draw volume_ul into the syringe at flow_ul_s through the current (or given) valve port, and wait until the move has finished. The pump must be initialized and have room for the volume.
dispense_ul ⚠️ hazard Push volume_ul out of the syringe at flow_ul_s through the current (or given) valve port, and wait until the move has finished. The syringe must contain at least that volume.
get_command_log 👁 read Return the most recent raw commands sent to / replies received from the instrument (newest last). Useful for debugging and for recording what was done.
get_connection_info 👁 read Report which instrument is connected (identity, address, simulated or real), whether the server is read-only, and the active safety limits. Call this first.
get_status 👁 read Report whether the pump is ready or busy, any error (decoded), the plunger position as the volume in the syringe, the valve position, resolution mode and current top speed.
initialize ⚠️ hazard Initialize the pump: drive the plunger to the top of the syringe (expelling its contents through the valve), set that as position 0 and home the valve. Needed after power-up, a plunger overload or terminate. Route the valve output to waste first. Takes a few seconds.
reconnect 🛑 safety Close and re-open the connection to the instrument (e.g. after it was power cycled or a cable was re-plugged).
set_valve ⚠️ hazard Turn the valve to a named position (3/4-port valves) or to a numbered port (distribution valves). In bypass the plunger cannot move. Returns the new status.
terminate 🛑 safety Stop any plunger move, loop or delay immediately (DT command T). A valve move in progress still completes. Re-initialize afterwards: the plunger may have lost steps.

Safety limits

Limit Default Meaning
max_volume_ul 5000 µL Largest volume one aspirate_ul/dispense_ul may move
max_flow_ul_s 500 µL/s Highest plunger flow rate an agent may use

Override at launch: --limit max_flow_ul_s=50. Independently of the limits, the server refuses moves that would overfill or over-empty the syringe, and flows the pump cannot produce with the installed syringe (top speed 5–6000 pulses/s).

Example prompts

  • "Initialize the pump, then prime it: aspirate 1 mL from the input port and dispense it to the output port, three times."
  • "Aspirate 150 µL of sample slowly (20 µL/s) from port 3 and dispense 50 µL into port 5."
  • "How much liquid is in the syringe right now and which port is the valve on?"
  • "The pump reported a plunger overload. What does that mean and what should I check?"
  • "Stop the pump now."

Notes

  • Conversion. Steps = volume × steps-per-stroke ÷ syringe volume, where steps-per-stroke is 6000 (XLP/XMP) or 3000 (XCalibur) in standard mode and 8× that in fine-positioning mode (N1). The mode is read from the pump (?28) before every move. Top speed V = flow × 6000 ÷ syringe volume: on all three models a full stroke is 6000 speed pulses in N0/N1. For the XCalibur this is derived from Tecan's published 1.2 s–20 min per stroke, not from its operating manual; please confirm on hardware.
  • Busy/ready is read only from Q, as the manual requires. Invalid commands are reported immediately; invalid operands (e.g. a move past the end of the syringe) are reported by the next Q, and the server turns both into clear errors.
  • Initialization force is chosen from the syringe size (full ≥ 1 mL, half for 250/500 µL, third for 50/100 µL; manual table 3-6) unless you pick one.
  • terminate sends T without R: in the DT command set R resumes a terminated string. T does not stop a valve move in progress. Re-initialize after terminating.
  • The server does not use microstep mode (N2), the OEM protocol (checksums, sequence numbers) or CAN.
  • Cavro Centris has a different resolution (181,490 increments per stroke) and volume-based firmware commands that we could not verify, so it is not supported. XE 1000 and older XL/XP 3000 pumps may work with --option steps_per_stroke=…, but they are untested.

Hardware verification

Model Firmware Interface Verified by Date
none yet: be the first

Release files for labmcp-cavro 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for labmcp-cavro 0.1.0
File Size Uploaded
labmcp_cavro-0.1.0.tar.gz 17.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for labmcp-cavro 0.1.0
File Interpreter ABI Platform
labmcp_cavro-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 35.4 kB

Release files / labmcp_cavro-0.1.0.tar.gz

Download URL labmcp_cavro-0.1.0.tar.gz
Size 17.7 kB
Tags Source
SHA-256 checksum
How to use checksums
5fe898647792bd327febffa31a165f00930404742a54a0e8daa21403b7b9808b
BLAKE2b-256 checksum
How to use checksums
56f83021d89bd6fe058fe85df6bf4b04738eda31052d2e1f6a9ca831a93938df
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release files / labmcp_cavro-0.1.0-py3-none-any.whl

Download URL labmcp_cavro-0.1.0-py3-none-any.whl
Size 17.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ad614c074eba91c63b347a076743ce7ebed8bf8e82a0cd0410fd5ac3269142e7
BLAKE2b-256 checksum
How to use checksums
ab2defdd8359c272c381c74804dcd42c9fe16850220269c8fdadfe97a9e8e40e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page