Connect Sensos to ChatGPT and Codex

Instead of opening Sync, filtering a list, and exporting it, ask:
"Which shipments to Frankfurt went over temperature last month?"
ChatGPT runs the lookups it needs, combines them, and answers in one pass.

The connection is read-only and sees only what your Sensos permissions allow, checked on every request.
For what it can do, the full tool list, and the security model, see Sensos MCP server.

Using Claude instead? See Connect Sensos to Claude.

Before you begin

You need:

a ChatGPT account on a plan with developer mode (Pro, Plus, Business, Enterprise, or Education), or a ChatGPT account that can use Codex;
Codex 0.151.0 or later, if you connect from Codex;
an active Sensos user account that can sign in at sync.sensos.io;
membership of at least one Sensos tenant containing the data you want to ask about; and
approval from your ChatGPT workspace administrator, if your workspace restricts developer mode or which apps members may add.

You do not need an API key, and you do not need Sensos to register anything for you.
ChatGPT and Codex identify themselves to Sensos automatically and are already on the Sensos allow-list, so there are no credentials to enter.

Connect from ChatGPT (web)

Developer mode, which lets you add your own MCP servers, is available in ChatGPT on the web.

In ChatGPT, open Settings.
Select Security and login and turn on Developer mode.
Go to chatgpt.com/plugins and select the plus button.
Enter a name, such as Sensos, and a short description.
Under Connection, enter https://mcp.sensos.io/mcp as the MCP server URL.
Choose OAuth as the authentication method. Leave any client ID and client secret fields empty, and if ChatGPT asks how it should identify itself, keep Client ID Metadata Document (CIMD) rather than dynamic client registration.
Create the connection and review the tools ChatGPT discovered. The app appears under Drafts in your app settings.
Start a new conversation, choose Developer mode from the plus menu in the composer, and select Sensos.
When ChatGPT sends you to Sensos, sign in with your Sensos credentials, review the requested access, and approve it. Sensos asks for one read permission and nothing else.

There is no tenant or account to choose while connecting, and no configuration step afterwards.
Every tenant and account you belong to is reachable from the one connection; ask "Which Sensos tenants and accounts can I reach?" to see them.

In Business, Enterprise, and Education workspaces, an administrator may first need to allow developer mode and app creation for your role under Workspace apps and Permissions & roles in the admin settings.

Connect from Codex

Codex CLI, Codex in the ChatGPT desktop app, and the Codex IDE extension share one configuration file, so you add Sensos once and it is available in all three.

Add this to ~/.codex/config.toml:
```
[mcp_servers.sensos]
url = "https://mcp.sensos.io/mcp"
scopes = ["read", "offline_access"]
```
The scopes line is required.
Without it, Codex requests only sign-in scopes, so Sensos accepts the connection but shows no tools.
Sign in.
In Codex CLI, run codex mcp login sensos.
In the desktop app or the IDE extension, open Settings (the gear menu in the IDE extension), select MCP servers, select Restart (or Restart extension), and then select Authenticate next to Sensos.
Complete the sign-in in your browser, review the requested access, and approve it.
Start a new Codex session and ask a question.
In Codex CLI, type /mcp to see connected servers; Sensos should list its tools rather than show 0 tools.

Try it

"Show in-transit shipments in [ACCOUNT NAME] with open temperature alerts, and tell me which ones need attention first."
"Give me the full picture for shipment [SHIPMENT NAME OR ID]: where it is, every alert that fired and why, its milestones, and the latest notes."
"Show shipment completions by week for the last 90 days in [ACCOUNT NAME], and flag any week that looks unusual."

More prompts, including a full excursion-investigation workflow, are on Sensos MCP server.

Troubleshooting

Sign-in fails with "Unknown client"

Sensos only lets allow-listed clients start a sign-in, and this message means the client identified itself in a way Sensos does not know.

Codex is too old. Codex versions before 0.151.0 identify themselves with a per-server document that Sensos has not allow-listed. Update Codex (codex --version shows the CLI version) and log in again.
The ChatGPT app uses dynamic client registration. Sensos does not support it. Delete the app at chatgpt.com/plugins and create it again, keeping CIMD, which is the default.
Codex has a client ID configured for Sensos. If ~/.codex/config.toml has an [mcp_servers.sensos.oauth] section with a client_id, Codex uses that instead of identifying itself. Remove the section unless Sensos gave you that ID.

I cannot turn on developer mode

Developer mode is available on the web, on the Pro, Plus, Business, Enterprise, and Education plans.
In a workspace, your administrator may need to allow it for your role.

Signing in or approving access fails

Confirm your Sensos credentials work directly at sync.sensos.io.
Confirm your user belongs to at least one Sensos tenant. Sensos refuses a connection with no tenant membership at all.
Try another browser, or clear cookies for the Sensos sign-in domain.
If the connection has expired, sign in again: in Codex CLI run codex mcp login sensos; in the desktop app or IDE extension select Authenticate under MCP servers; in ChatGPT open the app at chatgpt.com/plugins and reconnect.

Codex shows Sensos as connected with 0 tools

The Sensos entry in ~/.codex/config.toml is missing the scopes line.
Codex then requests only sign-in scopes, and Sensos hides its tools from a connection without the read scope.
Add the line shown in Connect from Codex, run codex mcp logout sensos and then codex mcp login sensos, and start a new Codex session.
A running Codex session does not pick up a new sign-in.
Installing Sensos as a plugin in the ChatGPT desktop app has the same effect: a plugin's server definition cannot carry scopes, so its sign-in gets a token without read.
Use the config entry above instead of a plugin, then sign in again.

ChatGPT connects but shows no Sensos tools

Open the app at chatgpt.com/plugins, select Refresh, and make sure the app is selected under Developer mode in the conversation.

ChatGPT or Codex cannot find data you expect to be there

Ask "Which Sensos tenants and accounts can I reach?" and check the account is the one you meant. Similar account names across tenants are the most common cause.
Confirm you can see the same record in Sensos Sync as the same user. If you cannot see it there, the connection cannot see it either. That is working as intended.
Add the account name, an identifier, and a date range to your question.
For Low Battery or Connectivity alerts on one shipment or asset, ask for an alert search rather than for the shipment or asset itself.

An answer looks wrong

Ask ChatGPT or Codex to show which tools it called and what came back, then check the same record in Sensos Sync.
If Sync and the assistant genuinely disagree, contact support with the details in Get help.
That is a bug worth knowing about.

Privacy in ChatGPT and Codex

Your questions and the returned data become part of your ChatGPT or Codex conversation, handled by OpenAI under the terms and privacy commitments that apply to your ChatGPT account or workspace.
See OpenAI's Privacy Policy.

Codex works inside your project, so Sensos data it retrieves can end up in files or commands it writes there.
Treat those files as you would any other export of Sensos data.

The connection does not request access to your ChatGPT memory, chat history, conversation summaries, or files.

Connect Sensos only to a ChatGPT account and workspace approved to receive your Sensos data.
If you are not sure whether yours is, ask your administrator first.

How Sensos handles authentication, data, and retention is covered on Sensos MCP server and in the Sensos privacy policy.

Disconnect

In ChatGPT, open the Sensos app at chatgpt.com/plugins and delete it.
In Codex CLI, run codex mcp logout sensos to drop the stored sign-in and codex mcp remove sensos to remove the server.
In the desktop app or IDE extension, remove Sensos under Settings > MCP servers.
No further requests can be made from that connection.

Data already returned into a conversation stays in that conversation, governed by the retention and deletion controls of your ChatGPT account or workspace.
Delete the conversation if you need the content gone.

Removing a user's Sensos access stops their connection from their very next request, because permissions are re-checked on every request.
There is nothing separate to revoke on the Sensos side.