Industry solutionsPublic source

LIMS MCP Server

A Laboratory Information Management System (LIMS) for ADK-Rust Enterprise food-beverage and pharmaceutical agents. 27 MCP tools covering samples & chain of custody, tests/assays with specifications, results with…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Samples & chain of custody — accessioned samples with an append-only custody log and status (received → in_testing → completed → disposed).

Tests & specifications — methods with numeric (min/max), count (max), or qualitative (expected value) specs.

Results & OOS — entering a result auto-evaluates it against the method spec (pass / oos / pending).

Data integrity (ALCOA+) — amend_result requires a mandatory reason and appends an immutable amendment (the original value is never overwritten); amendments invalidate a prior review.…

Batches & release gating — evaluate_batch rolls up all results across a batch's samples; set_disposition refuses to release unless every result passes spec and is reviewed.

HACCP — critical control points with limits; record_ccp_reading flags deviations outside critical limits.

Instruments — calibration tracking with a due/overdue watchlist.

Architecture

How LIMS MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

LIMS MCP Server

Validates the request and owns 27 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

LIMS MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask LIMS MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

27 named tools

register_sample

internal write

get_sample

Get a sample with its chain of custody

read only

list_samples

List samples by batch/status

read only

add_custody_event

Append a chain-of-custody event to a sample

internal write

create_method

Define a test method/assay with specification

internal write

list_methods

List test methods and specifications

read only

enter_result

Enter a result; auto-evaluates spec (pass/oos/pending)

internal write

get_result

Get a result with amendment history

read only

results_for_sample

List a sample's results

read only

amend_result

ALCOA+ amend a result with mandatory reason (gated)

internal write

review_result

Second-person reviewer sign-off on a result

internal write

create_batch

Create a batch/lot (quarantine)

internal write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

14 read only12 internal write1 external write

Two writes are gated (requires_approval): set_disposition (batch release/reject of physical product — classed external_write) and amend_result (changing a lab record of record).
Release has teeth — a batch cannot be released while any result is OOS, pending, or un-reviewed (verified in tests and live).
ALCOA+ by construction — Attributable, Legible, Contemporaneous, Original, Accurate: amendments preserve the original, capture who/when/why, and every data action is on the audit trail.
Reads are read_only. Sample data is fictitious.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-lims

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-lims",
    ["mcp-lims"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring

LIMS MCP Server

A purpose-built capability behind one MCP connection.

How LIMS MCP Server fits into an agent system.

ADK-Rust agent

MCP client

LIMS MCP Server

Domain system

The server’s published architecture

What can an agent ask LIMS MCP Server to do?

Understand the effect of every tool.

What the current documentation declares.

Follow the project’s documented starting point.

Continue with the project maintainers’ source of truth.

More in industry solutions.