Physical & geospatialPublic source

Parts MCP Server

A parts & spares platform for ADK-Rust Enterprise automotive and manufacturing agents. 27 MCP tools covering a parts catalog, multi-location inventory with reorder points, bill-of-materials & where-used, supersession…

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.

Catalog — parts with part number, category, unit, cost, preferred supplier, and lead time; lifecycle status (active/superseded/obsolete).

Multi-location inventory — stock per part per location with on-hand, reserved, and a reorder policy (point + qty). stock_for_part totals availability across locations.

Stock movements — receive_stock, issue_stock, transfer_stock, adjust_stock, each recorded immutably. Issue/transfer/reserve refuse to oversell available stock; adjustments can't drive…

Reservations — commit available stock against a work order/asset without removing on-hand; cancel to release.

BOM & where-used — bill-of-materials with recursive explosion (qty-multiplied) and cycle prevention; reverse where_used lookup.

Supersession — old→new replacement chains; resolve_supersession follows the chain to the current active part.

Reorder & forecasting — reorder_suggestions flags stock at/below its reorder point; forecast_demand derives average daily usage from history, projects demand, recommends a reorder point…

Architecture

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

→

Parts 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

Parts MCP Server architecture diagram from its official repository

Tool catalog

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

create_part

Create a part in the catalog

internal write

get_part

Get a part by id or part number

read only

list_parts

List parts by category/status

read only

create_location

Create a stocking location

internal write

list_locations

List stocking locations

read only

create_supplier

Create a supplier

internal write

list_suppliers

List suppliers

read only

set_stock_policy

Set reorder point + reorder qty for a part at a location

internal write

get_stock

Get stock of a part at a location

read only

stock_for_part

Stock across locations + total available

read only

receive_stock

Receive stock into a location

internal write

issue_stock

Issue/consume stock (physical) — gated

external 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 only11 internal write2 external write

Two writes consume physical stock and are gated (requires_approval, external_write): issue_stock (parts consumed/installed — also records usage) and adjust_stock (overrides recorded…
Movement integrity — oversell and negative-stock guards on every movement; every movement and adjustment is on the audit trail (audit_log).
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-parts

ADK-Rust connection shape

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