LC-MS Worklist Builder — Claude Code MCP server: install
Builds and checks LC-MS sample queues, then writes files for import into vendor software. Use it to prepare a run list without starting an acquisition.
claude mcp add --env LABMCP_ADDRESS=<LABMCP_ADDRESS> --env LABMCP_SIMULATE=<LABMCP_SIMULATE> --env LABMCP_READ_ONLY=<LABMCP_READ_ONLY> --env LABMCP_LIMITS=<LABMCP_LIMITS> --transport stdio ms-worklist -- uvx labmcp-ms-worklistWhat LC-MS Worklist Builder does
The server creates a draft from sample details and settings such as methods, injection volume, tray positions, and data-file naming. You can add samples, place blanks and QC injections, shuffle run order with a saved seed, validate the draft, and export an import file for MassLynx, SCIEX OS, MassHunter, or Xcalibur. It can also read an existing file from the output folder so you can edit it or export it for another vendor format.
Validation checks required fields, file names, tray positions, injection volume, and method extensions. Errors stop export; warnings do not. The server handles files only. It does not control the mass spectrometer or begin data acquisition, so a person imports the exported file into the vendor software.
You need uvx and an output folder; the default is ./worklists. Copy existing worklists or vendor templates into that folder before editing them. Files are not replaced unless overwrite=true is passed, and --read-only restricts the available tools to inspection and validation.
What it helps with
- Create an LC-MS sample queue
- Place blanks and QC injections in a run list
- Check tray positions and worklist fields
- Convert a worklist between vendor formats
- Write an import file for acquisition software
Example prompts for the agent
- Build an LC-MS worklist for these samples and export it for MassLynx.
- Add blanks and QC injections, shuffle the run order, then validate the draft.
- Read the worklist from the output folder and prepare it for SCIEX OS.
How to install LC-MS Worklist Builder
Platform CLI
claude mcp add --env LABMCP_ADDRESS=<LABMCP_ADDRESS> --env LABMCP_SIMULATE=<LABMCP_SIMULATE> --env LABMCP_READ_ONLY=<LABMCP_READ_ONLY> --env LABMCP_LIMITS=<LABMCP_LIMITS> --transport stdio ms-worklist -- uvx labmcp-ms-worklistReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from labmcp-ms-worklist <command>
Platform CLI
codex mcp add ms-worklist --env LABMCP_ADDRESS=<LABMCP_ADDRESS> --env LABMCP_SIMULATE=<LABMCP_SIMULATE> --env LABMCP_READ_ONLY=<LABMCP_READ_ONLY> --env LABMCP_LIMITS=<LABMCP_LIMITS> -- uvx labmcp-ms-worklistReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from labmcp-ms-worklist <command>
Config file
{
"mcpServers": {
"ms-worklist": {
"command": "uvx",
"args": [
"labmcp-ms-worklist"
],
"env": {
"LABMCP_ADDRESS": "<LABMCP_ADDRESS>",
"LABMCP_SIMULATE": "<LABMCP_SIMULATE>",
"LABMCP_READ_ONLY": "<LABMCP_READ_ONLY>",
"LABMCP_LIMITS": "<LABMCP_LIMITS>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from labmcp-ms-worklist <command>
Config file
{
"servers": {
"ms-worklist": {
"type": "stdio",
"command": "uvx",
"args": [
"labmcp-ms-worklist"
],
"env": {
"LABMCP_ADDRESS": "<LABMCP_ADDRESS>",
"LABMCP_SIMULATE": "<LABMCP_SIMULATE>",
"LABMCP_READ_ONLY": "<LABMCP_READ_ONLY>",
"LABMCP_LIMITS": "<LABMCP_LIMITS>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from labmcp-ms-worklist <command>
Platform CLI
gemini mcp add -e LABMCP_ADDRESS=<LABMCP_ADDRESS> -e LABMCP_SIMULATE=<LABMCP_SIMULATE> -e LABMCP_READ_ONLY=<LABMCP_READ_ONLY> -e LABMCP_LIMITS=<LABMCP_LIMITS> ms-worklist uvx labmcp-ms-worklistReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from labmcp-ms-worklist <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about LC-MS Worklist Builder
How do I install LC-MS Worklist Builder in Claude Code?
Run claude mcp add labmcp-ms-worklist -- uvx labmcp-ms-worklist.
What does LC-MS Worklist Builder do?
It creates and validates LC-MS sample lists, then writes import files for MassLynx, SCIEX OS, MassHunter, or Xcalibur. It does not start an acquisition.
Does it need a mass spectrometer connection?
No. The server writes files to an output folder; a person imports them into the vendor software.
