ISMS Copilot

Where ISMS Copilot plugs into your work

ISMS Copilot integrates in four live ways: coding agents consult it over MCP, your code calls the OpenAI-compatible Model API, your website runs an embedded assistant, and your team asks it from Slack. You can turn any chat reply into a Word, PDF, Excel or Markdown file.

What connects today

Each of these is live in production and documented. Pick the one that matches where the compliance question starts.

  • Coding agents over MCP

    Claude Code, Cursor, Codex, OpenCode or Grok consult ISMS Copilot and have compliance work checked. Your agent does the work; ISMS Copilot answers and you sign. Connect by sign-in or a personal access token (pat-isms-).

    Account MCP
  • Model API

    OpenAI-compatible chat completions for your own scripts and pipelines. Curated framework knowledge is added when a framework is detected in the request, or pinned by you. Prepaid credits, zero data retention.

    sk-isms-
  • Website assistant

    A compliance assistant on your own site from a console-generated snippet, limited to the domains you allow.

    Embed
  • Slack

    Ask ISMS Copilot from your Slack workspace by mention or direct message. Paid plans; an organization owner connects it.

  • Document files

    Turn a chat reply into a Word, PDF, Excel or Markdown file and take it into your document system.

  • Sign-in

    Email, Google or Microsoft accounts.

Which integration fits

IntegrationBest forCredential and billing
Account MCPA person working in a coding agent who wants GRC answers without leaving itPersonal access token; rides your ISMS Copilot chat plan
Model APIScripts, pipelines and sub-agent steps that need compliance textAPI key; prepaid credits on the developer platform
EmbedVisitors to your website asking compliance questionsPublic key plus a domain allowlist; separate assistant plans
SlackTeams that ask quick framework questions in channelsConnected by an organization owner; paid chat plans

Next to your GRC platform

ISMS Copilot does not sync with GRC platforms today. Teams use it as the consulting layer beside them: the platform, the tracker, the wiki, or the spreadsheet holds the record. Your AI reads those files if you already connected them to it, and sends ISMS Copilot a short excerpt. ISMS Copilot does not connect to Jira, Confluence, or the sheet, and it does not write back.

Frequently Asked Questions

Does ISMS Copilot sync with Vanta, Drata or other GRC platforms?

Not today. There is no live sync. Use your GRC platform for evidence collection and control tracking, and ISMS Copilot for drafting and framework questions; move the drafts across as Word, PDF, Excel or Markdown files.

Do you offer webhooks?

No. ISMS Copilot does not send webhook notifications. To automate, call the Model API from your own code, or let your coding agent call ISMS Copilot over MCP.

Do you support SAML SSO?

Not today. You can sign in with email, a Google account or a Microsoft account.

Can I export to Confluence or Notion?

There is no direct export to Confluence or Notion. Generate a Word, PDF, Excel or Markdown file from a chat reply and import it into your wiki.

Does ISMS Copilot connect to Jira or Confluence?

No. Your AI does, if you already gave it those tools. It reads the page or the ticket and sends ISMS Copilot a short excerpt. ISMS Copilot answers. You import the draft yourself. There is no write-back.

Can I connect claude.ai, Claude Desktop connectors or ChatGPT?

Yes. claude.ai and Claude Desktop: add the ISMS Copilot MCP server URL as a custom connector (including Team and Enterprise), sign in to ISMS Copilot and click Approve. ChatGPT connects as a custom MCP app: add the server URL with OAuth and the default settings, sign in to ISMS Copilot and click Approve. Claude Code connects by sign-in too; Cursor, Codex, OpenCode and Grok connect with a personal access token.

Connect your coding agent

Connect once and add the setup rule. Your agent does the work, ISMS Copilot checks it, you sign.