Machship MCP

Machship MCP Server: freight quotes, bookings and labels for AI agents

Machship MCP server connects Claude Desktop, Claude Code, Cursor, VS Code and any other MCP client to the Machship freight platform API. It has 125 tools for live rates, quotes, consignments, labels, manifests, tracking and invoices. It runs with npx over stdio, or as an HTTP endpoint.

Quickstart

You need Node.js 22 or later and a Machship API token. In Machship, go to Settings > API and generate a token.

# Read the token without echo, so it stays out of shell history

read -rs MACHSHIP_API_TOKEN claude mcp add --scope local machship -e MACHSHIP_API_TOKEN="$MACHSHIP_API_TOKEN" -- npx -y @devkind/machship-mcp

Then ask your agent: *"Ping the Machship API"*. A successful reply confirms the token.

Install in your client

Requirements:

• Node.js 22 or later
• A Machship API token
• Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Goose, LM Studio, Warp, or another MCP client

Standard config works in most MCP clients:

{

"mcpServers": { "machship": { "command": "npx", "args": ["-y", "@devkind/machship-mcp"], "env": { "MACHSHIP_API_TOKEN": "your-token-here" } } } }

Keep the token in your user-level client config. Do not put it in a project .mcp.json that you commit.

Claude Desktop

Open Settings > Developer > Edit Config, or edit the file directly:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the standard config above and restart Claude Desktop.

Claude Code

Use the Quickstart command above. --scope local stores the token in ~/.claude.json, outside the repository. You can also install the Claude Code plugin.

Cursor

Or go to Cursor Settings > MCP > Add new MCP Server. Use type command, the command npx -y @devkind/machship-mcp, and set MACHSHIP_API_TOKEN.

VS Code

code --add-mcp '{"name":"machship","command":"npx","args":["-y","@devkind/machship-mcp"],"env":{"MACHSHIP_API_TOKEN":"your-token-here"}}'

Or follow the VS Code MCP setup guide with the standard config above.

Windsurf

Follow the Windsurf MCP documentation and add the standard config above.

Goose

Go to Advanced settings > Extensions > Add custom extension. Use type STDIO, the command npx -y @devkind/machship-mcp, and set MACHSHIP_API_TOKEN.

LM Studio

Go to Program in the right sidebar > Install > Edit mcp.json and add the standard config above.

Warp

Go to Settings > AI > Manage MCP Servers > + Add, or type /add-mcp in the Warp prompt. Paste the standard config above.

Docker

No image is published to a registry. Build the image from this repo:

docker build -t devkind/machship-mcp .

Stdio config for an MCP client:

{

"mcpServers": { "machship": { "command": "docker", "args": ["run", "--rm", "-i", "-e", "MACHSHIP_API_TOKEN", "devkind/machship-mcp"], "env": { "MACHSHIP_API_TOKEN": "your-token-here" } } } }

HTTP mode on port 3000. The image sets MCP_HOST=0.0.0.0, so the published port accepts outside connections:

docker run --rm -e MACHSHIP_API_TOKEN -e TRANSPORT=http -p 3000:3000 devkind/machship-mcp

The server is also listed on Smithery.

Tools

The server has 125 tools in 21 modules. Every tool name starts with machship_.

A typical flow: machship_get_companies for the company ID, machship_search_locations for suburbs and postcodes, machship_get_routes for live rates, machship_create_consignment to book, a label tool, then machship_manifest_consignments to send the booking to the carrier. machship_get_consignment_statuses tracks it.

Tool text output stops at 25,000 characters. The full response is in structuredContent.

Example

{

"tool": "machship_get_routes", "arguments": { "request": { "companyId": 1790, "fromLocation": { "suburb": "Melbourne", "postcode": "3000", "state": "VIC", "country": "AU" }, "toLocation": { "suburb": "Sydney", "postcode": "2000", "state": "NSW", "country": "AU" }, "items": [{ "weight": 10, "length": 30, "width": 30, "height": 30, "name": "Parcel", "quantity": 1 }] } } }

Illustrative output:

{

"object": { "routes": [ { "carrier": { "name": "Example Express" }, "carrierService": { "name": "Road Express" }, "consignmentTotal": { "totalSellPrice": 24.5 }, "despatchOptions": [{ "etaLocal": "2026-11-05T17:00:00" }] } ] }, "errors": null }

Configuration

Network access and data

• The plugin starts the server with npx, so npx downloads the pinned @devkind/machship-mcp package from the npm registry.
• The server sends requests only to MACHSHIP_API_URL (default https://live.machship.com). Each request carries your API token and the tool arguments, such as addresses, items, consignment IDs and the invoice files you upload.
• Labels and other documents come back in the tool result as base64. The server writes no files.
• The server sends no telemetry and stores no data. It writes errors to stderr only.
• In HTTP mode the server also accepts requests on MCP_HOST and PORT. See HTTP mode.

Claude Code plugin

The repo root is a Claude Code plugin. It adds the Machship MCP server, pinned to a release version of @devkind/machship-mcp (.mcp.json). When you enable the plugin, Claude Code asks for your API token and stores it as a sensitive value. You can also change the API URL.

The plugin also ships the machship-freight skill. The skill teaches Claude the freight workflow with exact tool names: rates, consignment, labels, manifest and tracking. It also tells Claude to ask you before it books, manifests or deletes.

Install it from this repo's marketplace (Claude Code 2.1.275 or later):

/plugin install machship --marketplace devkindhq/machship-mcp

The plugin will also be in the Claude plugin directory once it is listed. On older Claude Code versions, use the claude mcp add command in the Quickstart.

HTTP mode

MACHSHIP_API_TOKEN=your-token TRANSPORT=http npx -y @devkind/machship-mcp

• MCP endpoint: POST http://localhost:3000/mcp (Streamable HTTP, stateless, JSON responses)
• Health check: GET http://localhost:3000/health

By default the server listens on 127.0.0.1 only. It rejects requests whose Host header is not localhost, 127.0.0.1 or ::1, which blocks DNS rebinding attacks from web pages. Set MCP_HOST=0.0.0.0 to listen on all interfaces, for example in a container.

Warning: HTTP mode has no authentication, and every request uses the server's Machship token. If you set MCP_HOST to anything other than a loopback address, put an authenticating proxy in front of the server.

Security notes

• HTTP mode has no authentication. See HTTP mode before you set MCP_HOST.
• Tools can create, edit and delete live consignments, identities and organisation links. Tool annotations mark the delete and remove tools as destructive, so a client can ask you to confirm them. machship_update_identity sets omitted fields to null.
• Use a token with the smallest Machship permissions that your work needs.

Development

This repo uses Yarn 1 (yarn.lock). Do not use npm install.

git clone https://github.com/devkindhq/machship-mcp.git

cd machship-mcp yarn install yarn lint && yarn build MACHSHIP_API_TOKEN=your-token yarn start

See CONTRIBUTING.md for the checks, commit style and release flow.

Built by

Built by Devkind. Maintained by the Devkind team.

License

ISC. See CONTRIBUTING.md and SECURITY.md.

Automating freight for your store?

If you ship with Machship, Devkind can connect it to the rest of your stack. We build on Shopify, Swell and headless commerce stacks, and build custom MCP servers and AI agent workflows. Talk to Devkind or email hello@devkind.com.au.