Skip to main content

Claude Desktop Setup

Claude Desktop is the easiest path. It supports custom HTTP headers via mcp-remote, which is how your Bearer token reaches the server.

Step 1: Locate your config file​

OSConfig file path
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
Linux~/.config/Claude/claude_desktop_config.json

If the file doesn't exist yet, create it.

Step 2: Add the CloudSEK connector​

Open the file and add the cloudsek-mcp entry inside mcpServers:

{
"mcpServers": {
"cloudsek-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.cloudsek.com/mcp",
"--header",
"Authorization: Bearer YOUR_API_TOKEN",
"--header",
"X-CloudSEK-Org-Id: YOUR_ORG_ID",
"--allow-http"
]
}
}
}

Replace YOUR_API_TOKEN and YOUR_ORG_ID with your actual values.

Windows users

There is a known issue in mcp-remote where spaces inside argument strings can break the connection on Windows. If the config above fails, use this alternative that keeps the token out of the args array:

{
"mcpServers": {
"cloudsek": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://api.cloudsek.com/mcp",
"--header", "Authorization: ${AUTH_HEADER}",
"--header", "X-CloudSEK-Org-Id: ${ORG_ID}"
],
"env": {
"AUTH_HEADER": "Bearer YOUR_BEARER_TOKEN",
"ORG_ID": "YOUR_ORG_ID"
}
}
}
}

Step 3: Restart Claude Desktop​

Fully quit Claude Desktop (macOS: Cmd+Q, Windows: right-click tray icon → Quit) and reopen it. The CloudSEK tools will appear in the tools menu.

Step 4: Verify​

Ask Claude: "What CloudSEK tools do you have available?"

You should see tools like get_alerts, ioc_lookup, and get_threat_actor_by_name. If nothing appears, see Troubleshooting.

Claude.ai Web (browser)​

The Claude.ai browser interface uses OAuth 2.0, which CloudSEK MCP does not currently support. Use Claude Desktop (the downloadable app) instead. Web support is on the CloudSEK roadmap; contact your CSM for the timeline.