Business operationsPublic source

Procurement MCP Server

AI-powered procurement engine for ADK-Rust Enterprise agents. Provides 37 MCP tools covering the full source-to-pay lifecycle — supplier management, purchase orders, RFQs, contracts, goods receipt, 3-way matching,…

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.

Source-to-pay lifecycle — from supplier onboarding through payment reconciliation.

AI-powered intelligence — 10 tools that no competitor offers: risk scoring, benchmarking, ESG, forecasting.

3-way matching — automatic PO vs receipt vs invoice reconciliation with tolerance.

ESG built-in — carbon footprint estimation and supplier diversity tracking.

Governance — multi-level approvals, budget checks, maverick spend detection.

Zero configuration — starts immediately with no external dependencies.

Architecture

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

→

Procurement MCP Server

Validates the request and owns 37 documented tool contracts.

→

Domain system

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

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

Procurement MCP Server architecture diagram from its official repository

Tool catalog

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

16 named tools shown from 37 documented tools

supplier_create

internal write

supplier_list

List suppliers

read only

supplier_get

Get supplier details

read only

supplier_rate

Rate a supplier

internal write

po_create

Create purchase order

internal write

po_list

List purchase orders

read only

po_get

Get PO details

read only

po_approve

Approve purchase order

internal write

po_send

Send PO to supplier

external write

po_cancel

Cancel purchase order

internal write

rfq_create

Create RFQ

internal write

rfq_respond

Submit supplier response

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.

9 internal write6 read only1 external write

Governance — multi-level approvals, budget checks, maverick spend detection.

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

MCP client configuration

{
  "mcpServers": {
    "procurement": { "command": "mcp-procurement" }
  }
}

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/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring