Industry solutionsPublic source

QMS MCP Server

A Quality Management System for ADK-Rust Enterprise food & beverage and manufacturing agents. 31 MCP tools spanning suppliers, batches & QC release, inspections, nonconformances, CAPA, complaints, and HACCP monitoring —…

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.

Provides qms capabilities through a typed MCP contract.

Architecture

How QMS 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.

→

QMS MCP Server

Validates the request and owns 31 documented tool contracts.

→

Domain system

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

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

QMS MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask QMS 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.

31 named tools

create_supplier

internal write

get_supplier

Get a supplier scorecard

read only

list_suppliers

List suppliers (worst score first)

read only

set_supplier_status

Set supplier approval status

internal write

create_batch

Create a production batch/lot

internal write

get_batch

Get a batch with QC tests and disposition

read only

list_batches

List batches, optionally by status

read only

add_qc_test

Record a QC test result (failing test auto-holds the batch)

internal write

set_batch_disposition

Set batch disposition; release is gated on passing tests and no open NCR

internal write

create_inspection

Record an inspection with a checklist

internal write

get_inspection

Get an inspection record

read only

raise_ncr

Raise a nonconformance

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.

19 internal write12 read only

Gated quality-critical writes — batch release, supplier status, NCR closure, CAPA closure, and complaint escalation require approval in production; reads are read_only.
Defensible records — NCRs and CAPAs carry an immutable audit trail.
Interlocked workflow — the release/closure rules prevent unsafe state transitions by construction.
Integration scaffold — the in-memory store is for development; back it with a durable, validated QMS of record and bind actors to authenticated identities in production.

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-qms

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-qms",
    ["mcp-qms"],
).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

QMS MCP Server

A purpose-built capability behind one MCP connection.

How QMS MCP Server fits into an agent system.

ADK-Rust agent

MCP client

QMS MCP Server

Domain system

The server’s published architecture

What can an agent ask QMS 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.