Connect an AI client to the ContainerMaster MCP server
Claude, Cursor, VS Code or your own agent can read your client requests, run freight quotes and landed cost for a lane, check tracking and search the catalogue. Every call runs as your signed-in account and uses the same logic as the web app.
Endpoint
- URL
- https://www.contrainermaster.com/api/mcp/workspace
- Transport
- Streamable HTTP, stateless, JSON responses (POST only)
- Protocol versions
- 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07
- Registry name
- io.github.MISHHF93/containermaster
Authentication
Send Authorization: Bearer cm_pat_…, a personal API token. Sign in and create one under Developer access; it is shown once, so copy it then. Tokens are read-only (the seven tools below, as you, in your workspace), expire after 7 to 365 days (90 by default) and can be revoked at any time. They cannot sign in to the web app, change settings, check out or reach admin pages. There is no OAuth sign-in for MCP clients yet, so configure the header by hand. A call without a valid token gets 401 and runs nothing.
Client configuration
Streamable HTTP clients (Cursor, VS Code, Claude Code, MCP Inspector):
{
"mcpServers": {
"containermaster": {
"url": "https://www.contrainermaster.com/api/mcp/workspace",
"headers": { "Authorization": "Bearer ${env:CONTAINERMASTER_TOKEN}" }
}
}
}Stdio-only clients (Claude Desktop) use the bridge in the repository, which forwards to the same endpoint:
{
"mcpServers": {
"containermaster": {
"command": "node",
"args": ["/path/to/contrainersmaster/apps/web/scripts/mcp-stdio.mjs"],
"env": {
"CONTAINERMASTER_MCP_URL": "https://www.contrainermaster.com/api/mcp/workspace",
"CONTAINERMASTER_TOKEN": "cm_pat_..."
}
}
}
}Raw JSON-RPC:
curl -s -X POST https://www.contrainermaster.com/api/mcp/workspace \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-H "authorization: Bearer $CONTAINERMASTER_TOKEN" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Tools
| Tool | What it does | Arguments |
|---|---|---|
| workspace.requests.list | The quote requests saved by the signed-in account, newest first (same data as /book?manage=1). | none |
| workspace.requests.export_csv | The same request log as workspace.requests.list, as CSV text. | none |
| workspace.quotes.freight_search | Carrier freight quotes for a lane (same logic as GET /api/v1/freight-quotes). Figures are calculated, not a booked rate. | origin, destination, containerType?, quantity? |
| workspace.quotes.landed_cost | Landed-cost breakdown for a container purchase and move (same logic as POST /api/v1/landed-cost). Each component says whether it is your input, a live-sourced rate, a cited reference estimate, or unavailable. | containerType, originPort, destinationPort, purchasePriceUsd, quantity?, salePriceUsd?, customsDutyPercent?, insurancePercent?, oceanFreightUsd?, originHandlingUsd?, destinationHandlingUsd?, inlandTransportUsd?, inspectionUsd?, documentationUsd? |
| workspace.tracking.status | Tracking for one container or booking reference (same logic as GET /api/v1/tracking). | containerNumber?, bookingReference? |
| workspace.catalogue.search | ISO 6346 container types, UN/LOCODE ports and BIC owner prefixes (same logic as GET /api/v1/directories). | directory?, q? |
| workspace.suppliers.list | Suppliers visible to the signed-in workspace (same logic as GET /api/v1/suppliers). | query? |
Quotes and landed cost are calculated from the rates and shipment data available to your workspace; they are not a confirmation of a booked rate.
Discovery
- Server Card:
/api/mcp/workspace/server-card - AI Catalog:
/.well-known/ai-catalog.json - Registry manifest:
server.jsonin the repository root