Claude Terminal49 connectorWhat Claude can do in your Terminal49 account.
The Claude Terminal49 connector exposes 10 tools. 9 only read your shipment data, 1 opens a new tracking request. Below: what Claude can look up, the single thing it can change, what the route data needs, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What it changes for a logistics team
Instead of copying a container number into the Terminal49 dashboard, you ask Claude in plain words. It looks the box up, reads its status, its route or its event history, and answers in the conversation. The only thing it can create is a new tracking request.
Answer a customer in one message. Someone asks where their goods are. search_container finds the box from a booking or PO reference, and get_container brings back its status and details.
Explain a delay. get_container_transport_events lays out the whole journey, and get_container_route adds the legs and vessels when your account includes route data.
Start following a new shipment. track_container opens the tracking request for you, after checking the box is not already there.
What it will not do: nothing runs on its own. No tool wakes up when a container arrives or a hold appears; Claude only calls them while it answers you. For alerts that fire in the background, you need an automation tool, which is a different job; the Integrations hub gathers that side. And by default the listing exposes only one write: no editing or deleting of shipments, containers or requests. Claude also sees nothing your own Terminal49 login does not already show you, since the sign-in happens on Terminal49's page with your credentials.
The vocabulary in one minute
Five words you will meet while plugging Terminal49 in.
- Connector
- The link you set up once between Claude and an account you already have, so it can work there while it answers you.
- Tool
- One named action the connector opens to Claude. Claude picks the ones it needs by itself; the directory lists them by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Given once per person, and revocable.
- Approval
- The confirmation Claude waits for before finishing something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service.
Plug Terminal49 into Claude in three steps
- 01
Find Terminal49 in Claude
In Claude's settings, open Customize, then Connectors, and look for Terminal49 in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first so each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Terminal49 in the window that Terminal49 opens itself. If the link breaks later, use Disconnect and connect again.
- 03
Read the authorization screen
Check the authorization screen before accepting. It belongs to Terminal49, not to Claude, and it decides what the access covers. You can also withdraw that access later from your Terminal49 account.
The 10 tools, sorted by what they do
Terminal49 gives Claude 10 tools: 9 that read your account, 1 that change something in it.
Two groups: what Claude reads and what it creates. Tool names stay as Claude shows them, in English.
- 9 read
- 1 write
What Claude reads (9)
9 toolsNine tools that consult containers, shipments and requests without touching them.
get_container
Pulls the full record of one container. Terminal49 lets Claude choose which extra data to load for your question, your own custom fields among them, instead of fetching everything every time.
get_container_route
Returns the multi-leg route of a container together with the vessel itinerary, so you can see the legs of the trip and which ship is planned on each.
get_container_transport_events
Gives Claude the complete timeline of a container's journey, event after event, from the first milestone to the latest one recorded.
get_shipment_details
Reads a shipment as a whole: its routing, the bill of lading reference, and every container attached to it, in one answer.
get_supported_shipping_lines
Lists the carriers Terminal49 supports, each shown with its SCAC code, the standard code a shipping line is known by. Claude reads that list and tells you whether a given line is in it.
list_containers
Browses the containers already in your Terminal49 account, page by page, with optional filters to narrow the list.
list_shipments
Walks through the shipments in your account, with optional filters and page by page, so Claude can pick out the file you are after.
list_tracking_requests
Shows the tracking requests opened on your account, with optional filters. Terminal49 names one use in particular: bringing out the requests that failed.
search_container
Finds containers from whatever reference you have at hand: container number, bill of lading, booking, or your internal reference. Terminal49 calls it the quickest way in.
What Claude creates (1)
1 toolOne tool that adds a tracking request to your account. No source details its confirmation: the general rule below applies.
track_container
Approval: see the ruleOpens a new tracking request in Terminal49 for a container number, then sends back the container details. A box already in your account comes back as is, with no new request.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request shows up in the chat, right when it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also cap what a connector may do for the whole organization, keeping reading open and closing writing, for instance. That setting applies to everyone and nobody overrides it from their own account. Last point: Claude works with your rights and nothing more. A shipment you cannot open in Terminal49 stays closed to it too.
Which plans it is available on
Out of the 819 sheets in the official directory, none shows availability per plan. The per-connector answer is published nowhere: that is a real gap in the catalogue.
The general rule is public: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can sign in. For the current state, check the connector's sheet in the official directory. Note that Terminal49 is documented only by its publisher: neither Claude's help center nor Anthropic's developer docs have a page on it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a container lands, gets held, or misses its ETA.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The partner badge in the directory is not a security audit either, and Anthropic says so on every sheet: it does not pick the tools a publisher exposes and does not guarantee they behave as announced. Only plug in what comes from a publisher you trust. Other pages in this family, such as the Claude airtable connector, are built on the same pattern if you want to compare.
Need help connecting Terminal49 to Claude?
A person reads every message.
