Business operationsPublic source

Supplier MCP Server

A Supplier Relationship Management (SRM) platform for ADK-Rust Enterprise procurement and supply-chain agents. 34 MCP tools spanning the full supply base lifecycle: suppliers & contacts, certifications & qualification,…

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.

Suppliers — lifecycle status (prospect → active → on-hold/suspended/disqualified) and qualification (unqualified → in-qualification → qualified/conditional/expired). Qualification controls…

Contacts & certifications — supplier contacts; ISO 9001 / IATF 16949 / ISO 22000 / HACCP certs with expiry tracking and a cross-supplier expiry watchlist.

Catalog & multi-source pricing — internal items with per-supplier offers (price, MOQ, lead time, availability). find_item_sources ranks sources by price/availability/lead time.

Purchase orders — issue, receive (partial/full), cancel. A PO cannot be issued to a supplier that isn't approved.

RFQ / sourcing — open RFQs, collect quotes, compare cheapest-first, award.

Quality — audits with auto-scoring and pass/conditional/fail; failed audits auto-raise a SCAR; SCAR lifecycle; quality/delivery events feeding the scorecard.

Scorecards — on-time delivery, quality rate, defect PPM, open-SCAR penalty, latest audit score → composite rating (A–D).

Architecture

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

→

Supplier MCP Server

Validates the request and owns 34 documented tool contracts.

→

Domain system

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

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

Supplier MCP Server architecture diagram from its official repository

Tool catalog

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

34 named tools

create_supplier

internal write

get_supplier

Get a supplier by id

read only

list_suppliers

List suppliers by category/status

read only

set_supplier_status

Set supplier lifecycle status (suspend/disqualify revokes PO approval)

internal write

set_qualification

Set qualification status (qualifying approves the supplier for POs)

internal write

add_contact

Add a contact to a supplier

internal write

list_contacts

List a supplier's contacts

read only

add_certification

Add a certification (ISO 9001, IATF 16949, ISO 22000, ...)

internal write

list_certifications

List a supplier's certifications

read only

expiring_certifications

Certifications expiring within N days (compliance watchlist)

read only

create_item

Create a catalog item / internal SKU

internal write

list_items

List catalog items by category

read only

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 write16 read only2 external write

High-impact writes are gated (requires_approval): create_po and cancel_po (classed external_write — they commit spend with a supplier), plus set_supplier_status, set_qualification, and…
The PO gate has teeth — create_po refuses any supplier not approved for POs (wrong status or qualification), so an agent cannot accidentally buy from an unqualified or suspended source.
Everything is audited — every state change appends to an audit trail (audit_log).
Reads are read_only — sourcing, scorecards, risk profiles, and watchlists never mutate state.
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-supplier

ADK-Rust connection shape

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