To connect ChatGPT, Claude or Gemini to ISO Mate, add the MCP server URL https://api.isomate.io/api/mcp as a custom connector in your assistant, sign in to ISO Mate when your browser opens, choose one account and pick the access for each area. There is no API token to create, copy or store, and you can revoke the connection at any time from Connected apps.
What you need
- An ISO Mate user with access to the account you want to connect.
- A verified email address on your ISO Mate user.
- An AI assistant that supports custom MCP connectors (remote MCP servers) with OAuth sign in.
- The ISO Mate MCP server URL:
https://api.isomate.io/api/mcp
How to add ISO Mate to your assistant
Every assistant names its menus a little differently, and the menus change over time. The steps are the same everywhere:
- Open the connectors or integrations settings of your assistant.
- Choose to add a custom connector (sometimes called a custom app or an MCP server).
- Enter a name such as ISO Mate and paste the MCP server URL
https://api.isomate.io/api/mcp. - Keep OAuth as the authentication method. You do not need a client ID or a client secret.
- Save and connect. Your assistant opens ISO Mate in your browser so you can sign in and approve the connection.
Claude
In Claude, use the Add custom connector dialog and paste the MCP server URL. If Claude asks how it should identify itself, keep the recommended option. ISO Mate supports it, so you do not enter a client ID or secret. On Claude Team and Enterprise plans, an Owner adds the connector for the organization, and each member then connects with their own ISO Mate sign in.
ChatGPT
ChatGPT adds custom MCP connectors through developer mode, which you turn on in the advanced settings of ChatGPT. On business and enterprise workspaces, an administrator may need to allow developer mode before members can add a connector. Follow the current OpenAI help article for the exact menu path, then paste the MCP server URL and choose OAuth.
Gemini
In Gemini CLI, add ISO Mate as an HTTP server in your settings file (~/.gemini/settings.json), for example "mcpServers": { "iso-mate": { "httpUrl": "https://api.isomate.io/api/mcp" } }. Then run /mcp auth iso-mate in Gemini CLI to open the ISO Mate sign in, and /mcp list to confirm the connection. Other Gemini apps that support custom MCP servers use the same URL in their connector settings.
How to sign in and choose one account
When your assistant sends you to ISO Mate, sign in as usual, including two factor authentication if it is turned on for you. ISO Mate then shows a consent screen that names the app, shows what kind of app it is, and tells you where you will return after approving.
- One account per connection: choose the account the assistant may reach. The connection can never see data in your other accounts.
- More than one account: to use the assistant with another account, connect again and choose that account. Each connection has its own access.
- Accounts you cannot choose: an account is listed but cannot be chosen when it is disabled or when an administrator has turned connections off for it.
How to choose the access per area
The consent screen lists the areas of ISO Mate, such as DevOps and projects, Quality assurance, Compliance, Incidents, Custom objects and workflows, Tasks, notes and diagrams, Help desk, Sales, Reports and Account. For each area you choose one level:
- None: the assistant cannot use this area.
- Read: the assistant can view records in this area.
- Read and write: the assistant can also create, update and delete records in this area, as far as you could yourself.
Some areas, such as Reports and Account, are read only. When you click Allow, ISO Mate sends you back to your assistant and sends you a notification and an email about the new connection.
Why access starts at Read
ISO Mate preselects Read for the areas the assistant asked for and never preselects write access. Most questions only need Read. When the assistant later needs to change something, ISO Mate tells it which access is missing, and the assistant asks you to approve the connection again with more access. You review that request on the same consent screen.
How your role caps access
An assistant can never do more than you can. Options your role does not allow are disabled and marked Your role in this account does not allow this. ISO Mate also checks your role on every request, so if an administrator later reduces your role, the connection loses that access straight away.
Troubleshooting
Request no longer valid
A connection request is only valid for a short time and only once. If the consent screen says the request expired or is no longer valid, return to your assistant and start the connection again.
Unverified app warning
ISO Mate shows this warning when it cannot confirm who publishes the app that sent you. Only continue if you trust the app and started the connection yourself.
Command line assistants show extra warnings
Command line assistants such as Gemini CLI run on your own computer and return to a local address after sign in. ISO Mate cannot verify which program is listening there, so the consent screen shows the This app runs on your own device warning and usually the unverified app warning. Only continue if you started the connection yourself.
Your role does not allow this
The access level is above what your role allows in the chosen account. Choose a lower level, or ask an administrator to change your role, then connect again.
Connecting the same assistant a second time
Connecting the same assistant to the same account again replaces the first connection, and the consent screen tells you so before you approve.
The assistant cannot create workflows or sign attestations
By design, assistants can never create or change workflows and can never sign policy attestations, even with Read and write access. With write access they can view and run existing workflows. Create or edit workflows and sign attestations in ISO Mate yourself.
Request blocked
If you see a message that the request was blocked, try again. If it keeps happening, contact support with the time of the attempt and the assistant you used.
The assistant lost access
A connection stops working when you or an administrator revoke it, when connections are turned off for the account, when you leave the account, or when it has not been used for a long time. Connect the assistant again to continue.
Related articles
Feature
Want your AI assistant to work with your ISO Mate data? Start your 14-day free trial.