Connect any MCP client

Point Cursor, Codex, or another MCP-capable tool at the ISMS Copilot account MCP endpoint with a Bearer token.

If your tool is not Claude Code, the same account MCP endpoint still works. You need a personal access token and a client that supports HTTP MCP with a custom Authorization header.

1. Create a token

In chat.ismscopilot.com, open Settings → Connected apps → Create token. Copy the pat-isms-… value once.

For the full Claude Code walkthrough (permissions table, reconnect, troubleshooting), see Connect ISMS Copilot to Claude Code.

2. Endpoint

https://account.ismscopilot.com/v1/account/mcp

Transport: HTTP MCP.
Auth: Authorization: Bearer pat-isms-…

3. Client-specific notes

Claude Code (reference)

claude mcp add --scope user --transport http ismscopilot \
  https://account.ismscopilot.com/v1/account/mcp \
  --header "Authorization: Bearer pat-isms-..."

Keep --scope user so the server is available in every folder.

Cursor / Codex / other

Add an MCP server entry with:

URL: https://account.ismscopilot.com/v1/account/mcp
Header: Authorization: Bearer pat-isms-…

Exact JSON shape depends on the client. If the client only supports OAuth connectors and rejects personal access tokens, it cannot use this path yet (ChatGPT connectors are in that category).

4. Smoke test

Ask the agent to list your ISMS Copilot workspaces. If tools do not appear, restart the client after adding the server, and confirm the token was not truncated when pasted.

5. Rotate

claude mcp remove ismscopilot

Then mint a new token and re-add. Always revoke the old token in Settings if it may have leaked.

A token acts as you. Grant only the scopes you need, and revoke unused tokens.