AI Assistant Connectors

Automation

Connect ChatGPT, Claude or Gemini to ISO Mate in about a minute and let your AI assistant work with your real projects, tickets, tasks and compliance records. You decide exactly what it can see and do, and you can switch it off at any time.

The challenge it solves

Your team already asks AI assistants for help, but the assistant cannot see your work. People copy issues, tickets and policies into chat windows, paste the answers back by hand, and lose track of what was shared. Connecting a tool properly usually means creating API tokens, storing them somewhere safe and hoping they never leak, so most teams never get past the copy and paste stage.

What you can do

Connect in a minute, without tokens

  • Paste one address: add https://api.isomate.io/api/mcp as a custom connector in ChatGPT, Claude or Gemini, sign in to ISO Mate and click Allow.
  • Nothing to copy or store: the connection uses a secure OAuth sign in, so there is no API token to create, share or rotate.
  • Works with the assistants your team already uses: ChatGPT, Claude, Gemini and other assistants that support remote MCP servers connect the same way.

Put your assistant to work on live data

  • Get answers from your real records: ask which incidents are still open, what is left in the current sprint or which help desk tickets are waiting on your team, and the answer comes from ISO Mate, not from a stale export.
  • Hand over the busywork: with write access, the assistant can create tasks from meeting notes, update issues, add calendar events and keep sales records current.
  • Cover the whole platform: DevOps and projects, quality assurance, tasks and notes, compliance, incidents, custom objects, help desk, sales, communication and reports are all available.

Stay in control of every connection

  • Choose the access per area: pick None, Read, or Read and write for each area on a clear consent screen. Read is the starting point, and write access is always your choice.
  • Keep accounts separate: each connection reaches exactly one account, so an assistant connected to one organisation can never see another.
  • Never exceed your role: an assistant can only do what you can do, and ISO Mate checks your role on every request, so a role change applies to your connections straight away.
  • Keep sensitive actions human: assistants can never manage users, roles, API tokens or billing, never create or change workflows, and never sign policy attestations.
  • See and revoke connections: the Connected apps page lists every assistant you have connected, with its access and when it was last used. Revoking takes effect immediately.
  • Govern the whole account: administrators see every connection in the account, can revoke any of them and can turn AI assistant connections off for the account with one switch.
  • Know who is connecting: the consent screen labels each app as recognised, registered by your organisation, external or unverified, and you get a notification and an email whenever a new app is connected.

Popular use cases

  • Morning planning: ask for your overdue tasks and today’s calendar events before the first meeting of the day.
  • Sales pipeline review: list open deals by stage and update leads and opportunities straight after a call.
  • Support triage: summarise new help desk tickets and see which ones need attention first.
  • Sprint check ins: review what is left in the sprint and turn meeting notes into issues on the backlog.
  • Audit preparation: find controls that still need evidence and policies that are due for review.
  • Test progress updates: check how a test cycle is going and which executions failed, without opening a dashboard.

Works with the rest of ISO Mate

AI Assistant Connectors run on the ISO Mate MCP server, so every request goes through the same permissions and account isolation as the console. A change an assistant makes is an ordinary ISO Mate change: it is saved to the same records your team uses, it can start your Workflow Automation rules, and it shows up in Reporting and Analytics. Developers can still connect IDE tools and scripts to the same MCP server with scoped API tokens.

Key benefits at a glance

  • Fast setup: one address and one sign in, with no tokens to manage.
  • Least privilege by default: Read first, write only when you choose it, and never more than your role allows.
  • Full visibility: every connection is listed, notified and revocable at any time.
  • Open standards: built on the Model Context Protocol and OAuth 2.1, so it works with the assistants your team prefers.