Your coding agent's Terraform security check
before the PR exists

claude mcp add --transport http audytx https://audytx.com/mcp \
  --header "X-Client-ID: YOUR_CLIENT_ID"

Project-level .cursor/mcp.json (or ~/.cursor/mcp.json globally). Cursor interpolates ${env:…} so the ID can live in your environment instead of the file:

{
  "mcpServers": {
    "audytx": {
      "url": "https://audytx.com/mcp",
      "headers": { "X-Client-ID": "${env:AUDYTX_CLIENT_ID}" }
    }
  }
}

VS Code prompts once for the Client ID and stores it as a secret — it never sits in the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "audytx-client-id",
      "description": "audytx Client ID (from audytx.com/dashboard)",
      "password": true
    }
  ],
  "servers": {
    "audytx": {
      "type": "http",
      "url": "https://audytx.com/mcp",
      "headers": { "X-Client-ID": "${input:audytx-client-id}" }
    }
  }
}

JetBrains AI Assistant's remote-server config is URL-only (no custom headers), so connect through the mcp-remote stdio proxy. In Settings | Tools | AI Assistant | Model Context Protocol (MCP), add a server as JSON:

{
  "mcpServers": {
    "audytx": {
      "command": "npx",
      "args": [
        "mcp-remote", "https://audytx.com/mcp",
        "--header", "X-Client-ID:${AUDYTX_CLIENT_ID}"
      ],
      "env": { "AUDYTX_CLIENT_ID": "YOUR_CLIENT_ID" }
    }
  }
}

No space after the colon in X-Client-ID:${…} — some clients split header args on spaces (a documented mcp-remote workaround).

Claude Desktop's native remote connectors require an OAuth sign-in flow, which audytx has staged (RFC 9728 metadata is live; the full authorization server is planned — see /mcp/security). Until then, the same mcp-remote proxy works today in Settings → Developer → Edit Config:

{
  "mcpServers": {
    "audytx": {
      "command": "npx",
      "args": [
        "mcp-remote", "https://audytx.com/mcp",
        "--header", "X-Client-ID:${AUDYTX_CLIENT_ID}"
      ],
      "env": { "AUDYTX_CLIENT_ID": "YOUR_CLIENT_ID" }
    }
  }
}

Step 0: create your Client ID at /dashboard — the UUID is shown once, so copy it then.

Windsurf reads ~/.codeium/windsurf/mcp_config.json. Add audytx as a remote server (Windsurf uses serverUrl for HTTP servers):

{
  "mcpServers": {
    "audytx": {
      "serverUrl": "https://audytx.com/mcp",
      "headers": { "X-Client-ID": "YOUR_CLIENT_ID" }
    }
  }
}

Verify: reload Windsurf's MCP servers, then ask your agent to list the audytx tools, or POST tools/list to the endpoint (discovery needs no auth).

Any other client that can reach a Streamable-HTTP server works too: point it at https://audytx.com/mcp and send the Client ID as either the X-Client-ID header or Authorization: Bearer YOUR_CLIENT_ID. Clients that only speak stdio can bridge with npx mcp-remote as in the JetBrains example above.