Business operationsPublic source

Logistics MCP Server

Unified logistics MCP server with 16 tools across 3 backends — ShipEngine (FedEx/UPS/DHL/USPS), Shippo, and Google Maps route optimization. Shipments, rates, tracking, labels, address validation, and delivery route…

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.

Multi-carrier — compare rates across FedEx, UPS, DHL, USPS via ShipEngine or Shippo

Route optimization — Google Maps for multi-stop delivery planning and ETAs

Full lifecycle — create shipment → get rates → book → track → deliver

No credential exposure — API keys stay in env vars

Single binary — no Node.js, no Python

Architecture

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

→

Logistics MCP Server

Validates the request and owns 16 documented tool contracts.

→

Domain system

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

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

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

create_shipment

Create a new shipment with origin, destination, and parcels

external write

list_shipments

List shipments with optional status filter

read only

get_shipment

Get shipment details by ID

read only

cancel_shipment

Cancel a shipment

external write

get_rates

Get shipping rates for a shipment from multiple carriers

read only

compare_rates

Compare rates across carriers sorted by price or speed

read only

list_carriers

List available carriers

read only

book_rate

Book a specific rate and purchase a shipping label

financial action

track_shipment

Get real-time tracking status for a shipment

read only

get_tracking_events

Get full tracking event history for a shipment

read only

generate_label

Generate a shipping label for a booked shipment

internal write

get_label

Get an existing label by shipment ID

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.

12 read only2 external write1 financial action1 internal write

The registry manifest declares external write, read only, financial action, internal write 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.

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-logistics --features all-backends

MCP client configuration

export SHIPENGINE_API_KEY="TEST_xxx"

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

Keep exploring

More in business operations.

Browse all servers →

Ads MCP ServerA digital advertising platform for ADK-Rust Enterprise sales & marketing agents. 19 MCP tools covering campaigns, ad groups, ads/creatives, budgets and bids, audiences, daily performance metrics with derived KPIs…19 tools Analytics MCP ServerGoverned analytics platform for AI agents — metrics, dashboards, funnels, cohorts, anomaly detection, forecasting, and policy enforcement. 28 tools with full audit trail.28 tools Banking MCP ServerUnified banking MCP server with 15 tools across 3 backends — Plaid (US/Canada/EU), Mono (Africa), and Open Banking (UK/EU PSD2). Accounts, transactions, balances, payments, identity, and statements.15 tools

Source record

Release and repository metadata for this catalog entry.

View public repository ↗

Version: 1.1.1
License: Apache-2.0
Tools: 16
Revision: 85f3a05c4fce
Updated: May 27, 2026

Transportsstdio