Connect ChatGPT

Add AssetLab as a ChatGPT connector - OAuth setup, authorization with your API key, and what to expect once connected.

ChatGPT connects to the same AssetLab MCP server as Claude - https://mcp.assetlab.ca - through its connectors feature.

Step 0 - create an API key

In AssetLab, an Administrator creates a key under Settings → API Keys: name it ("ChatGPT - Alex"), pick scopes (start read-only; see Tools & scopes), copy the al_live_... value - it's shown once.

Add the connector

In ChatGPT, go to Settings → Apps & Connectors → Add new connector.
Enter a name (e.g. AssetLab) and the server URL: https://mcp.assetlab.ca
Set authentication to OAuth.
Click Create - ChatGPT auto-discovers the OAuth endpoints.
You're redirected to the AssetLab authorization page: paste your API key.
After authorization, AssetLab tools appear in your ChatGPT conversations.

First prompts

"List my sites and how many assets each has."
"What work orders are overdue, and who are they assigned to?"
"Summarize open work requests from the last two weeks."

Once write scopes are granted, ChatGPT can create and update records too - it will show you what it's about to do; review before confirming, as with any assistant. See Example workflows for proven recipes.

Troubleshooting

Symptom	Fix
Connector created but no tools	Reconnect - the authorization step may not have completed
`invalid_client` or auth errors on connect	Remove and re-add the connector; auto-discovery re-registers it
Tools error with permission messages	The key lacks the needed scope - check Settings → API Keys
Worked yesterday, fails today	The key may have expired or been revoked - keys carry an expiry date

Disconnecting

Revoking the API key in Settings → API Keys cuts access instantly - that's the action that matters. Deleting the connector in ChatGPT is cosmetic cleanup. Reconnecting later requires a fresh authorization (ChatGPT users occasionally see a reconnect prompt after AssetLab security updates - pasting the key again is all it takes).