Full lifecycle — from goods receipt through storage, picking, packing, shipping, and returns.
Inventory & Warehouse MCP Server
Complete inventory and warehouse management for ADK-Rust Enterprise agents. Provides 38 MCP tools covering the full warehouse lifecycle — stock management, serialized tracking, RFID, QR codes, pick/pack/ship, wave…
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.
Serialized tracking — individual unit tracking with full chain of custody history.
RFID-ready — register tags, process bulk reader scans, detect missing inventory.
QR code generation — encode serial, SKU, location, and shipment data for mobile scanning.
Space-aware — locations have capacity limits (units, weight, volume) with utilization reporting.
Wave planning — batch multiple pick orders for efficient warehouse operations.
Zero configuration — starts immediately with no external dependencies or API keys.
Architecture
How Inventory & Warehouse 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.
Inventory & Warehouse MCP Server
Validates the request and owns 38 documented tool contracts.
Domain system
Keeps the API, data, credentials, and business rules behind the server.
This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.
Tool catalog
What can an agent ask Inventory & Warehouse 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.
15 named tools shown from 38 documented tools
item_upsertAdd/update inventory item
internal writeitem_listList inventory items
read onlylocation_createCreate warehouse/bin location
internal writelocation_listList locations
read onlystock_receiveReceive stock into location
internal writestock_issueIssue stock from location
internal writestock_transferTransfer between locations
internal writestock_adjustAdjust stock (cycle count)
internal writestock_checkCheck stock level
read onlyreorder_alertsItems below reorder point
read onlystock_reserveReserve stock for order
internal writestock_releaseRelease reservation
internal writeGovernance
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.
- The registry manifest declares internal write, read only tool risk classes.
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.
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.
cargo install mcp-inventory{
"mcpServers": {
"inventory": { "command": "mcp-inventory" }
}
}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.
Keep exploring
More in business operations.
Source record
Release and repository metadata for this catalog entry.
- Version
- 1.4.0
- License
- Apache-2.0
- Tools
- 38
- Revision
- f724d17bfd68
- Updated
- May 27, 2026