Connect Claude Desktop
Add AutoCISO to Claude Desktop and you can ask Claude about your compliance posture in plain language.
Prerequisites
- An MCP token with the
mcp:readscope — see the MCP Quickstart or MCP Auth and Scopes. - Claude Desktop installed.
Step 1 — Open your config file
Find claude_desktop_config.json:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
If the file doesn’t exist, create it.
Step 2 — Add AutoCISO as a server
Paste the mcpServers block. Use the Remote (HTTP) tab if your Claude Desktop supports remote MCP servers directly; otherwise use the mcp-remote bridge tab, which proxies a remote server through a local command.
{
"mcpServers": {
"autociso": {
"url": "https://autociso.io/mcp",
"headers": { "Authorization": "Bearer aci_REPLACE_ME" }
}
}
} {
"mcpServers": {
"autociso": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://autociso.io/mcp",
"--header", "Authorization: Bearer aci_REPLACE_ME"]
}
}
} Step 3 — Restart and verify
- Quit and reopen Claude Desktop (a restart is required to load the new server).
- Look for the MCP tools icon — AutoCISO’s tools should be listed.
- Ask Claude: “What’s my access posture summary?” — Claude calls
posture_summaryand answers from your data.
If something’s wrong
| What you see | Likely cause | Fix |
|---|---|---|
| No AutoCISO tools appear | Bad JSON, wrong file path, or no restart | Validate the JSON, confirm the path, fully restart Claude |
401 | Token typo or revoked | Re-copy the token; create a new one if needed |
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 |
For the full code-to-fix mapping, see MCP Errors and Retries and MCP Troubleshooting.
Last reviewed: 2026-09-09
Was this page helpful?