Connect Cursor and VS Code

Add AutoCISO to Cursor or VS Code and ask about your compliance data straight from the editor’s AI panel.

Prerequisites

Step 1 — Add the server config

Cursor reads .cursor/mcp.json; VS Code reads .vscode/mcp.json. VS Code lets you prompt for the token at launch with an inputs entry, so the secret never lives in the file.

{
"mcpServers": {
  "autociso": {
    "url": "https://api.autociso.io/mcp",
    "headers": { "Authorization": "Bearer aci_REPLACE_ME" }
  }
}
}

Step 2 — Reload and verify

  1. Reload the editor window so it picks up the new config.
  2. Confirm AutoCISO appears in the MCP servers list.
  3. In the AI panel, ask: “List my open risks” — the assistant calls risk_register_list and answers from your Risk Register. For more questions to try, see MCP Capabilities.

If something’s wrong

What you see Likely cause Fix
No AutoCISO tools appear Bad JSON, wrong file, or no reload Validate the JSON, confirm the path, reload the window
401 Token typo or revoked Re-enter or recreate the token
No AutoCISO tools, or fewer than expected The token lacks the scope, or your plan does not include the feature See Scope is not entitlement
404 NOT_FOUND MCP is not enabled for your deployment Contact support

For every other code, see MCP Errors and Retries and MCP Troubleshooting.

Last reviewed: 2026-10-08

Was this page helpful?

Esc