MCP Troubleshooting

Most AutoCISO MCP problems fall into a handful of buckets. Find your symptom below.

Symptom → cause → fix

Symptom	Likely cause	Fix
AutoCISO tools don’t appear in the client	Bad JSON, wrong config file path, or the client wasn’t restarted	Validate the JSON, confirm the file location, then fully restart the client
`404 NOT_FOUND` on `/mcp`	MCP is disabled for your org (beta gate)	Expected in beta — confirm enablement below
`401`	Token typo, expired, or revoked	Re-copy the token; create a new one in Settings → API Tokens if needed
`403` or any `5xx`	Came from infrastructure, not the MCP app (the app only emits 401/404/429)	Retry; if persistent, contact support
`SCOPE_FORBIDDEN`	Token missing the `mcp:read` scope	Recreate the token with `mcp:read`
`NOT_PERMITTED` on a write	`risk_create_draft` called without `mcp:write` or with write disabled for your org	Expected — see the Tool Catalog, not a bug
`429`	Rate limited	Slow down; the SDKs back off automatically

A clean way to check: make a tools/list call (see the Quickstart).

A list of tools → MCP is enabled.
404 NOT_FOUND → MCP is disabled for your org. This is the beta gate; contact AutoCISO support to request access.

Editor MCP config is JSON and unforgiving:

Run the file through a JSON validator — a single trailing comma breaks it.
Confirm the exact file: .cursor/mcp.json for Cursor, .vscode/mcp.json for VS Code, claude_desktop_config.json for Claude Desktop.
After editing, reload the window (editors) or restart (Claude Desktop).

See the connect guides for the exact blocks: Claude Desktop and Cursor / VS Code.

Map any error code to its cause in MCP Errors and Retries.
If a 404 persists and you believe MCP should be on for your org, contact AutoCISO support to confirm beta enablement.

Last reviewed: 2026-09-09

Was this page helpful?