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
- An MCP token with the
mcp:readscope — see the MCP Quickstart. - Cursor or a recent version of VS Code with MCP support.
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://autociso.io/mcp",
"headers": { "Authorization": "Bearer aci_REPLACE_ME" }
}
}
} {
"inputs": [
{
"id": "autociso_token",
"type": "promptString",
"description": "AutoCISO MCP token",
"password": true
}
],
"servers": {
"autociso": {
"url": "https://autociso.io/mcp",
"headers": { "Authorization": "Bearer ${input:autociso_token}" }
}
}
} Step 2 — Reload and verify
- Reload the editor window so it picks up the new config.
- Confirm AutoCISO appears in the MCP servers list.
- In the AI panel, ask: “List my open risks” — the assistant calls
risk_register_listand answers from your register.
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 |
404 NOT_FOUND | MCP disabled for your org (beta gate) | Expected in beta — see Troubleshooting |
SCOPE_FORBIDDEN | Token missing mcp:read | Recreate the token with mcp:read |
NOT_PERMITTED on a write | Write not enabled for your org | Expected — see Tool Catalog |
See MCP Errors and Retries for the full mapping.
Last reviewed: 2026-09-09
Was this page helpful?