ISMS CopilotYour agent does the work. ISMS Copilot is the compliance expert it consults and has check that work.
Your coding agent does the work and keeps the code, the repo and the plan. When a task turns into ISO 27001, SOC 2, GDPR, NIS 2 or DORA work, it consults ISMS Copilot over MCP, and it has that work checked before finishing. You decide and sign.
Claude Code, one line, then /mcp to sign in
claude mcp add --scope user --transport http ismscopilot https://account.ismscopilot.com/v1/account/mcpHow it works
- 01
Your agent consults ISMS Copilot
Mid-task, and before it finishes compliance work, your agent calls ISMS Copilot through the MCP tools create_conversation and send_message. What travels is the message your agent writes. When the work is a policy, a Statement of Applicability, or a risk register, that message carries the passages to judge or check, not the file itself.
- 02
ISMS Copilot brings the compliance judgement
Curated framework knowledge, the memories and files of the workspace the conversation runs in, and the drafting itself all happen on ISMS Copilot's side. A policy draft or a gap analysis is generated there, not in your agent's context window.
- 03
Only the answer comes back
Your agent receives the finished answer as a tool result. The bulk of the GRC context never enters its transcript, so it is never re-sent on every later turn of the session.
- 04
The answer still counts, so ask for short ones
The returned answer is read by your agent like any other tool result, and it stays in the transcript from then on. When you only need a decision or a list, tell the agent to ask for a brief answer.
What to ask ISMS Copilot, what to keep local
| Work | Where it runs | Why |
|---|---|---|
| Exact requirements and identifiers (DORA RTS, NIS2 implementing regulation, ISO 42001, CMMC) | Ask ISMS Copilot | Article, control and practice numbers come from curated framework modules, not from your model's memory. |
| Framework interpretation, gap analysis and control mapping | Ask ISMS Copilot | Framework knowledge is injected there, so you do not paste standards into your own context. |
| Drafting that needs framework grounding or your company context (policies, SoA justifications, risk register entries) | Ask ISMS Copilot | Drafted against curated framework modules plus your workspace memories, files and company context. |
| Audit preparation that needs framework grounding or your company context | Ask ISMS Copilot | ISO 27001, ISO 27701, ISO 42001, SOC 2, GDPR, NIS 2, DORA, EU AI Act, HIPAA, PCI DSS and more. |
| Compliance work before it is final (policies, SoA text, risk entries, registers, audit responses) | Have ISMS Copilot check it | A second opinion on the text your agent sends, not a sign-off. You decide and sign. |
| Small, well-known edits and quick drafts your model already handles | Keep in your agent | When your model knows the answer, needs no lookup and writes straight to a file, delegating adds turns and costs more. |
| Code, git, tests, configuration | Keep in your agent | That is your agent's job. ISMS Copilot has no access to your repository. |
| Reading and editing local files | Keep in your agent | The specialist only sees what your agent puts in the message. |
Connect your harness
| Harness | Status | How it connects |
|---|---|---|
| Claude Code | Supported | The one-line claude mcp add above, then /mcp to sign in and approve. A pat-isms Bearer header remains the fallback. |
| Cursor | Supported | An HTTP MCP server entry in mcp.json: the endpoint URL plus the Authorization header. |
| Codex | Supported | An mcp_servers entry in ~/.codex/config.toml: the endpoint URL plus the Authorization header. |
| OpenCode | Supported | A remote MCP server entry with the endpoint URL and the Bearer header. |
| Grok | Supported | An HTTP MCP server entry with the endpoint URL and the Bearer header. |
| Claude Desktop and claude.ai connectors | Supported | A custom connector with the endpoint URL; sign in to ISMS Copilot and approve. Team and Enterprise owners add it once for the organization. |
| ChatGPT | Supported | A custom MCP app (developer mode) with the endpoint URL and OAuth, default settings; sign in to ISMS Copilot and approve. |
The connection
- Endpoint
- https://account.ismscopilot.com/v1/account/mcp
- Transport
- HTTP MCP (Streamable HTTP)
- Auth
- Sign in to ISMS Copilot and approve (OAuth). Fallback: Authorization: Bearer pat-isms-...
- Token (fallback)
- chat.ismscopilot.com, Settings, Connected apps, Create token. Shown once; grant only the scopes the agent needs.
- Smoke test
- Ask your agent to list your ISMS Copilot workspaces.
Claude Code with ISMS Copilot: same score as Claude Code alone on 20 tested lookups, with fewer Claude tokens
In our pre-registered test (2026-09-28, 3 runs each, Claude Code 2.1.283 with claude-sonnet-5, web tools available to both setups, answer key from official sources), Claude Code delegating to ISMS Copilot scored the same as Claude Code researching alone on 20 identifier lookups across five frameworks (ISO 27001, ISO 42001, CMMC, DORA RTS, NIS2), using fewer Claude tokens per correct answer. ISMS Copilot plan usage is not counted there. Where it does not help: small tasks Claude already knows, such as a short policy draft or a few SoA entries, cost more Claude usage when delegated, so keep those in your agent. Delegated conversations ride your ISMS Copilot chat plan and its usage allowance, with the reset time shown in the app. There is no separate billing, no credits and no per-token meter for the MCP connection. The free plan connects too; Think mode needs a paid plan, and Beyond runs on paid plans under a daily run cap. If you use up your chat plan's allowance, the plan-limit error tells your agent when it resets, and read tools keep working. Your harness model still reads the answer it gets back, so the answer is not free for your Claude or ChatGPT plan: the drafting behind it is what stays on our side.
Method and limits, including where delegation does not help →Sources and product truth
- Set up with your agent
Paste one prompt: your agent connects, writes a routing rule and runs a smoke test. You create the token.
- Connect any MCP client
Token, endpoint, per-client notes, usage limits
- Connect Cursor and Codex
mcp.json and config.toml shapes, smoke test, rotation
- Tokens, scopes, and security
Least privilege, revoke, expiry, hard limits
- Why connect a specialist
Skill file vs maintained registry, with the benchmark's losses stated
- Benchmark: Claude Code with and without ISMS Copilot
2026-09-28, pre-registered: method, answer key, results, caveats
- Where delegation does not help
Small tasks Claude already knows: measured, and cheaper kept local
- The agents product
Tools, scopes, limits and the honest not-list
- For GRC engineers
Mappings at volume on the Model API, cost per 1,000 answers
Frequently Asked Questions
Does this replace Claude, Cursor or Codex?
No. Your agent does the work and keeps the code, the repository, the plan and the tool loop. ISMS Copilot is the compliance expert it consults and has check that work. Use both.
Does calling ISMS Copilot save tokens in my agent?
It depends on the task. By mechanism, the framework knowledge, workspace context and long drafting stay on ISMS Copilot's side, so they never enter your agent's transcript and are never re-sent on later turns. The answer that comes back does enter the transcript, so ask for brief answers when that is enough. What we measured (2026-09-28, pre-registered, Claude Code with claude-sonnet-5, 3 runs each): the same score as Claude Code alone with fewer Claude tokens per correct answer on 20 identifier lookups, no saving on a long mixed coding and compliance session, and more Claude usage on small ISO 27001 tasks Claude already knows. ISMS Copilot plan usage is not counted in those figures. Method and limits are on the benchmark page in the sources above.
What does it cost?
Nothing on top of your ISMS Copilot chat plan. Conversations from your agent count against the same usage allowance as the web app, and there is no separate billing for the MCP connection.
How do I connect claude.ai, Claude Desktop connectors or ChatGPT?
Add the endpoint URL as a custom connector in claude.ai or Claude Desktop, then sign in to ISMS Copilot and click Approve. No token to copy. 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. Cursor, Codex, OpenCode and Grok use a personal access token sent as a Bearer header.
What does ISMS Copilot see from my project?
From your project, only what your agent writes into the message: ISMS Copilot has no direct access to your repository, your filesystem or your harness's context. On its own side, the answer can also draw on the memories and pinned files of the ISMS Copilot workspace the conversation runs in; pinned files reach these turns shortened. The conversation is stored in your ISMS Copilot account like any other chat.
What can the token do?
It acts as you, within the scopes you grant when you create it: for example reading workspaces and memories, or starting conversations. A read-only token cannot start conversations. Revoke it in Settings at any time; revocation takes effect immediately.
Give your agent a GRC specialist
Connect once and add the setup rule. Your agent does the work, ISMS Copilot checks it, you sign.