Business operationsPublic source

MES MCP Server

A Manufacturing Execution System for ADK-Rust Enterprise electronics, food & beverage, and manufacturing agents. 24 MCP tools spanning work orders & routing, scheduling, shop-floor execution, OEE, factory test yield,…

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 mes capabilities through a typed MCP contract.

Architecture

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

→

MES MCP Server

Validates the request and owns 24 documented tool contracts.

→

Domain system

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

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

MES MCP Server architecture diagram from its official repository

Tool catalog

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

24 named tools

create_work_center

internal write

get_work_center

Get a work center

read only

list_work_centers

List work centers (optionally by line)

read only

set_work_center_status

Set a work center status (running/idle/setup/down/maintenance)

internal write

create_work_order

Create a work order with a routing of operations

internal write

get_work_order

Get a work order with routing, output, and audit trail

read only

search_work_orders

Search work orders by domain/status/line

read only

schedule_work_order

Schedule a work order to a line and time window

internal write

release_work_order

Release a scheduled work order to the floor (gated on routing/work centers)

internal write

start_operation

Start a routing operation by sequence

internal write

complete_operation

Complete a routing operation

internal write

record_output

Record good/scrap output against a work order

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.

16 internal write8 read only

Gated floor-control writes — work order release/close/cancel and work center status changes require approval in production; reports and traces are read_only.
Interlocked lifecycle — release and close rules prevent invalid state transitions.
Work order audit trail — every state change is recorded.
Integration scaffold — the in-memory store is for development; back it with your real MES 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-mes

ADK-Rust connection shape

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