API MCP Server

Terminal49 API

Terminal49 is a container and shipment tracking API. You send a bill of lading, booking, or container number, and Terminal49 returns shipment and container status, milestones, and ETAs, and sends webhook notifications when they change.

This repository holds the public developer docs, the OpenAPI spec, and the clients for the API: a TypeScript SDK, a CLI, and an MCP server for AI assistants.

What's in this repository

Quick starts

The API, SDK, and CLI quick starts need a Terminal49 API key. Create one in the developer portal.

Call the API

Send the key in the Authorization header with the Token prefix:

curl https://api.terminal49.com/v2/shipments \
  -H "Authorization: Token YOUR_API_KEY"

To track your first container, follow Start here.

Use the TypeScript SDK

npm install @terminal49/sdk

import { Terminal49Client } from '@terminal49/sdk';

const client = new Terminal49Client({ apiToken: process.env.T49_API_TOKEN! });
const container = await client.getContainer('container-uuid', ['shipment']);

See the SDK quickstart and the SDK README.

Use the CLI

npm install -g @terminal49/cli
export T49_API_TOKEN=YOUR_API_KEY
t49 track MSCU1234567

t49 track infers whether the number is a container, booking, or bill of lading, and creates a tracking request. Run t49 commands to list every command. See the CLI README.

Connect the MCP server

Point your MCP client at https://mcp.terminal49.com (Streamable HTTP). Use that root origin, with no extra path. It is the canonical OAuth resource identifier. The client signs you in with OAuth, so you do not need an API key. In Claude, add Terminal49 from the Claude Directory.

Clients that can't run a browser OAuth flow send Authorization: Token YOUR_API_KEY. For ChatGPT, Claude Code, Cursor, VS Code, and other clients, see the MCP server docs. To run the stdio server on your machine, follow Run it from this repository.

Develop in this repository

This is an npm workspaces monorepo that uses Vite+ (vp) as its toolchain. Use Node 24.22.1 or a newer Node 24 patch (.tool-versions pins 24.22.1).

vp install      # or: npm ci
vp run check    # format, lint, and type-check every workspace
vp run test     # run every package's tests
vp run build    # build the SDK, then the MCP server, then the CLI

To preview the docs site locally, run Mintlify through npx. Running it from the workspace install fails to parse the MDX pages.

cd docs && npx -y mintlify@latest dev

Some files are generated from docs/openapi.json or the SDK source. Do not edit them by hand. AGENTS.md lists each generated file and the command that regenerates it. The Commands section of the same file covers the rest of the toolchain, and WRITING_GUIDE.md sets the docs style.

Use conventional commit prefixes (docs:, feat:, fix:, chore:), and keep docs, code, and tooling changes in separate commits.

Security

This is a public repository. Never commit API keys, secrets, or customer data. Use placeholders such as Token YOUR_API_KEY in examples.

To report a security issue privately, see SECURITY.md.

License

Copyright (c) 2026 Terminal49, Inc.

• Code and the API spec: MIT. This covers everything outside docs/, including the SDK, CLI, MCP server, gateway, and tooling, plus the OpenAPI spec at docs/openapi.json and the Postman collection generated from it.
• Documentation: CC BY 4.0. This covers everything else in docs/, including the guides, reference pages, and images. When you reuse it, credit "Terminal49, Inc." and link to terminal49.com/docs.
• Not licensed: the Terminal49 name and logos, including docs/logos/ and public/store-icons/. Third-party material, such as map data shown in screenshots, keeps its own terms. Vendored code under tools/oxlint/anti-slop/ keeps its own license.

Contributions are accepted under the same terms: code under MIT, documentation under CC BY 4.0.