Freight MCP Server

Freight MCP server exists for a simple reason — assistants are far more useful when they can act on Freight directly instead of describing what you should do. Ocean freight spot rate & FBX container shipping trend: should I book ocean freight now?.

What you get

A single freight API returns one vendor's number with no second opinion and stops at the rate. freight-pulse goes the whole distance an importer needs:

• Cross-validated rates. — Reads Drewry's World Container Index (WCI) and the Freightos
• The whole decision, not just the price. — Landed cost with HS-code duty, all-in door-to-door,
• Its own accumulating history. — Every lane queried is cached with a timestamp; trend tools
• Public, non-sensitive inputs. — Ports, HS codes, declared values — nothing secret. Safe for

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Freight is connected, these are the calls the assistant has available:

• Area — Tools
• Decision — ship_decision, simulate_scenario, compare_modes (air vs ocean), sourcing_analysis (China+1 / nearshoring)
• Procurement — procurement_strategy, build_tender, evaluate_bids, select_provider (forwarder/3PL), record_performance
• Sustainability — carbon_footprint (GLEC/ISO 14083), decarbonization_roadmap, reverse_logistics
• Monitoring — create_watch, check_watches, market_report, special_cargo

Configuration and credentials

You will need 2 environment variables: FREIGHT_PULSE_KEY, SEARATES_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the freight mcp server does with a few real requests.

Choosing this one

Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Freight's toolset — Area, Decision, Procurement and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Baneado98; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.