Set up the Terminal49 connector for your organization in Claude and ChatGPT
Last updated: October 12, 2026
If your company uses Claude Team or Enterprise, or ChatGPT Business, Enterprise or Edu, an admin can add the Terminal49 connector once so it shows up for everyone in your organization. Each person then connects with their own Terminal49 login, so Claude or ChatGPT can only see what that person's account can see.
Quick Links
Before you start
In Terminal49: everyone who will use the connector needs their own Terminal49 login. There is nothing to configure on the Terminal49 side. If a teammate doesn't have a login yet, someone with Account Manager permissions can invite them.
In Claude: an Owner or Primary Owner adds the connector for the organization. On Enterprise plans, a custom role that includes Manage access to Libraries can also add custom connectors.
In ChatGPT: a workspace owner or admin decides which plugins are available in the workspace.
Server URL:
https://mcp.terminal49.com, exactly as written with no path after it. You only need it if you add Terminal49 as a custom connector.Sign-in: people connect by signing in to Terminal49 in a browser window that Claude or ChatGPT opens. No API key is needed.
Note: Terminal49 is listed in Claude's connector directory and in the ChatGPT Plugins Directory, so you can add it without entering a server URL. Use the custom connector steps only if your organization requires custom connectors or blocks directory plugins.
For Claude Team and Enterprise
Add Terminal49 from the directory (recommended)
In Claude, go to Organization settings → Connectors.
Select Browse connectors at the bottom of the page.
Select Terminal49 from the list, then select Add to your team.
Adding the connector makes it available to your team, but it doesn't connect anyone. Each person still signs in on their own.
Note: You can't change a custom connector's sign-in settings after you add it. To change them, remove the connector and add it again, and your members will need to reconnect.
Optional: limit what the connector can do
Owners can set each Terminal49 tool to Always allow, Needs approval or Blocked for the whole organization from Customize → Connectors → Terminal49 → Tool permissions. For example, you could set track_container, the one tool that starts a new tracking request, to Needs approval.
For ChatGPT Business, Enterprise and Edu
ChatGPT Team is now called ChatGPT Business, and what ChatGPT used to call connectors, and then apps, it now calls plugins. Some admin screens still use the word apps.
Enable Terminal49 from the Plugins Directory (recommended)
Open Admin → Plugins (chatgpt.com/admin/plugins).
Under Public, find Terminal49.
Enable it and set its audience to the people or roles who need it. Available lets those people install it themselves; Installed installs it for them.
In Workspace apps (chatgpt.com/admin/ca), check that the Terminal49 connection is turned on for the same roles.
Or add it as a custom MCP server
In ChatGPT on the web, go to Plugins (chatgpt.com/plugins).
Select the plus button, then Add custom MCP server.
Enter
Terminal49as the name. Under Connection, enterhttps://mcp.terminal49.comas the Server URL.Set authentication to OAuth.
Review the risk warning, select I understand and want to continue, then select Create as a plugin.
Make the plugin available to your workspace.
How each teammate connects
Once your admin has added Terminal49, each person connects once with their own Terminal49 login.
In Claude
Watch: Connect Your Terminal49 Account to Claude
Go to Customize → Connectors.
Find Terminal49 in the list. If your admin added it as a custom connector, it may have a Custom label.
Select Connect, then sign in with your Terminal49 account in the window that opens and approve access.
In a chat, select + → Connectors and turn on Terminal49.
In ChatGPT
Open Plugins in the ChatGPT sidebar and search for
Terminal49.Select Install plugin. If your admin already installed it for you, skip this step.
When ChatGPT asks you to connect, sign in with your Terminal49 account and approve access. [NEEDS VERIFICATION: confirm the label of the connect prompt; OpenAI's readable docs don't name it.]
In a chat, select Terminal49 from the tools menu or type
@Terminal49.
To check it works, ask: "Using Terminal49, search for container [one of your container numbers] and summarize its status."
Note: ChatGPT asks you to confirm before a tool makes a change by default, so you'll see a confirmation before Terminal49 starts tracking a new container.
For your IT team: Claude and ChatGPT reach the Terminal49 server from their own cloud, not from your team's computers.
What the Terminal49 connector can do today
Every tool only reads your data, except track_container, which starts a new tracking request. If the container is already in your account, it returns that container instead.
Tool | What it does |
|---|---|
| Finds containers by container number, BL, booking or your own reference. |
| Starts tracking a new container. The only tool that changes anything. |
| Container status, availability, holds, fees and Last Free Day, with optional shipment, terminal and custom field details. |
| The full event timeline for a container's journey. |
| Shipment routing, BL and the containers on it. |
| Carriers Terminal49 supports and their SCAC codes. |
| Multi-leg routing and vessel itinerary. This is a paid feature. |
| Lists shipments with filters, up to 25 per page. |
| Lists containers by status, port, holds, fees, arrival or Last Free Day, up to 25 per page. |
| Counts containers grouped by terminal, status, shipping line, hold type or date. |
| Finds the customers, shippers, consignees, brokers, forwarders and dray carriers on your shipments. |
| Lists tracking requests and their status. |
By default, lists and counts include only actively tracked containers and shipments, the same as your dashboard. The connector can't edit shipments, reference numbers or tags, stop or resume tracking, refresh a container, or set up webhooks today. Those are available through the Terminal49 API.
What this is not
Not a way to change your data. Outside of starting a new tracking request, it only reads what's already in Terminal49. It can read custom fields such as a PO number, but it can't change them.
Not something you set up with an API key. claude.ai and the Claude apps always connect through the Terminal49 sign-in, and ChatGPT can't send a custom API key.
Not a shared login. Adding Terminal49 for your organization doesn't give everyone a shared account. Each person signs in with their own.
Not the developer path. Connecting Claude Code, the coding tool, is a different setup. See Claude Code setup.
Troubleshooting
What you see | What to do |
|---|---|
Claude says Couldn't reach the MCP server | Check the URL is exactly |
Claude says Authorization with the MCP server failed | Check the URL is exactly |
The sign-in window never opens | Your browser blocked the pop-up. Allow pop-ups for claude.ai or chatgpt.com and try again. |
| Disconnect and reconnect Terminal49 to refresh your sign-in. |
| Your sign-in worked, but Terminal49 hasn't enabled this access for your account. Contact us using the details below. |
| The connector shares the Terminal49 API limit of 100 requests per minute per account. Wait for the time given in the |
Terminal49 isn't selectable in a Claude chat | Turn it on from the chat's tools menu. On Team and Enterprise plans, ask an Owner to add it for the organization. |
ChatGPT's Install plugin button is greyed out or says it's disabled by your admin | Ask your workspace admin to enable Terminal49 under Plugins in the admin settings. |
Route details aren't available | Routing is a paid feature. You can still see a container's movements through its transport events. |
See related article: Terminal49 connector for Claude
If you need help or have any other questions, the fastest way to get assistance is through our in-app chat. You can also reach us at support@terminal49.com.