Kiro Setup

Kiro is AWS's AI IDE. It supports remote MCP servers natively, so no mcp-remote wrapper is needed.

Step 1: Set environment variables (recommended)

Add these to your shell profile before launching Kiro:

export CLOUDSEK_BEARER_TOKEN=your_bearer_token_here
export CLOUDSEK_ORG_ID=your_org_id_here

Step 2: Open the MCP config

From the Kiro command palette (macOS Cmd+Shift+P / Windows & Linux Ctrl+Shift+P), search for MCP and select:

• Kiro: Open workspace MCP config (JSON) applies to this project only
• Kiro: Open user MCP config (JSON) applies to all workspaces

Scope	Path
Workspace (project-specific)	.kiro/settings/mcp.json in your project root
User (global)	~/.kiro/settings/mcp.json

Step 3: Add the CloudSEK server entry

{
  "mcpServers": {
    "cloudsek": {
      "url": "https://api.cloudsek.com/mcp",
      "headers": {
        "Authorization": "Bearer ${CLOUDSEK_BEARER_TOKEN}",
        "X-CloudSEK-Org-Id": "${CLOUDSEK_ORG_ID}"
      }
    }
  }
}

Kiro hot-reloads config after saving; no restart needed. If you want to test quickly with hardcoded values, replace the ${...} references with literal strings, but do not commit that version to git.

warning

If you commit .kiro/settings/mcp.json to version control, always use env var references (${CLOUDSEK_BEARER_TOKEN}) and never hardcode literal token values. Consider adding .kiro/settings/mcp.json to your .gitignore if it contains sensitive values.

Step 4: Verify

Open a Kiro agent chat and ask: "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.