ISMS Copilot, inside your AI tools
In development: connect your ISMS Copilot account to Claude Code, Codex, Cursor and other MCP-compatible tools, and work on compliance without leaving your terminal or editor.
What you'll be able to do
- Ask ISMS Copilot a compliance question mid-task and get the answer inside your tool, grounded in the same framework knowledge as the chat product
- Start and continue conversations in your account from any connected agent
- Browse your workspaces and pull the right client context into your session
- Create and update memories, so what your agent learns stays with your account
- List your generated documents without switching to the browser
Built on MCP
ISMS Copilot for Agents speaks the Model Context Protocol (MCP), the open standard AI tools use to connect to outside services. If your tool can talk to MCP servers, it will be able to talk to ISMS Copilot: Claude Code, Codex, Cursor and a growing list of others. Underneath sits a plain REST API for anything custom you want to wire up yourself.
Designed for safe automation
Scoped personal access tokens: you decide per token what it can read and what it can create
Tokens are issued and revoked from your account settings, not by email to support
No delete operations over the integration: destructive actions stay in the app where you can see them
Every call is logged against the token that made it
Not the same thing as the API
The ISMS Copilot API gives your code our compliance model: you send prompts, you get completions, you build your own product on top. ISMS Copilot for Agents gives your tools your account: your conversations, workspaces, memories and documents, available wherever you work. Different jobs, different keys.
Building a product instead? See the ISMS Copilot API →Status: in development
The integration layer is designed and in active development. Join the waitlist and tell us which tools you use; connector order follows demand.
Frequently Asked Questions
Which tools will work?
The integration targets anything that can connect to an MCP server. Claude Code, Codex and Cursor are the first priorities, sequenced by waitlist demand. A plain REST API is part of the design for everything else.
What happens to my data?
Your account data stays in your account. Access from outside happens only through tokens you issue, scope and revoke yourself, and every call is logged against the token that made it.
Will it cost extra?
It's designed for existing ISMS Copilot subscribers. Final commercial details come with launch; waitlist members hear first.
When does it launch?
We're building now and will invite the waitlist in batches. No date promises; the waitlist email is the announcement channel.
Bring compliance into your workflow
Join the waitlist and we'll email you when agent access opens.