cloudpulse

Name: cloudpulse
Author: lhf552004

lhf552004

The Multi-Cloud Glue for AI Agents. Diagnose and troubleshoot connectivity, logs, and config drifts across Vercel, AWS, GCP, and Azure via MCP.

Setup

Choose your client, copy the config, then fill in any required environment variables.

Add to Cursor Add to VS Code

claude mcp add cloudpulse --env AWS_ACCESS_KEY_ID='<AWS_ACCESS_KEY_ID>' --env AWS_SECRET_ACCESS_KEY='<AWS_SECRET_ACCESS_KEY>' --env VERCEL_TOKEN='<VERCEL_TOKEN>' --env CLOUDFLARE_API_TOKEN='<CLOUDFLARE_API_TOKEN>' -- npx -y cloudpulse-mcp

~/.codex/config.toml

[mcp_servers.cloudpulse]
command = "npx"
args = ["-y", "cloudpulse-mcp"]
env = { AWS_ACCESS_KEY_ID = "<AWS_ACCESS_KEY_ID>", AWS_SECRET_ACCESS_KEY = "<AWS_SECRET_ACCESS_KEY>", VERCEL_TOKEN = "<VERCEL_TOKEN>", CLOUDFLARE_API_TOKEN = "<CLOUDFLARE_API_TOKEN>" }

# codex mcp add cloudpulse --env AWS_ACCESS_KEY_ID='<AWS_ACCESS_KEY_ID>' --env AWS_SECRET_ACCESS_KEY='<AWS_SECRET_ACCESS_KEY>' --env VERCEL_TOKEN='<VERCEL_TOKEN>' --env CLOUDFLARE_API_TOKEN='<CLOUDFLARE_API_TOKEN>' -- npx -y cloudpulse-mcp

~/.cursor/mcp.json

{
  "mcpServers": {
    "cloudpulse": {
      "command": "npx",
      "args": [
        "-y",
        "cloudpulse-mcp"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "<AWS_ACCESS_KEY_ID>",
        "AWS_SECRET_ACCESS_KEY": "<AWS_SECRET_ACCESS_KEY>",
        "VERCEL_TOKEN": "<VERCEL_TOKEN>",
        "CLOUDFLARE_API_TOKEN": "<CLOUDFLARE_API_TOKEN>"
      }
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "cloudpulse": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "cloudpulse-mcp"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "<AWS_ACCESS_KEY_ID>",
        "AWS_SECRET_ACCESS_KEY": "<AWS_SECRET_ACCESS_KEY>",
        "VERCEL_TOKEN": "<VERCEL_TOKEN>",
        "CLOUDFLARE_API_TOKEN": "<CLOUDFLARE_API_TOKEN>"
      }
    }
  }
}

~/.gemini/settings.json

{
  "mcpServers": {
    "cloudpulse": {
      "command": "npx",
      "args": [
        "-y",
        "cloudpulse-mcp"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "<AWS_ACCESS_KEY_ID>",
        "AWS_SECRET_ACCESS_KEY": "<AWS_SECRET_ACCESS_KEY>",
        "VERCEL_TOKEN": "<VERCEL_TOKEN>",
        "CLOUDFLARE_API_TOKEN": "<CLOUDFLARE_API_TOKEN>"
      }
    }
  }
}

claude_desktop_config.json

{
  "mcpServers": {
    "cloudpulse": {
      "command": "npx",
      "args": [
        "-y",
        "cloudpulse-mcp"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "<AWS_ACCESS_KEY_ID>",
        "AWS_SECRET_ACCESS_KEY": "<AWS_SECRET_ACCESS_KEY>",
        "VERCEL_TOKEN": "<VERCEL_TOKEN>",
        "CLOUDFLARE_API_TOKEN": "<CLOUDFLARE_API_TOKEN>"
      }
    }
  }
}

.trae/mcp.json

{
  "mcpServers": {
    "cloudpulse": {
      "command": "npx",
      "args": [
        "-y",
        "cloudpulse-mcp"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "<AWS_ACCESS_KEY_ID>",
        "AWS_SECRET_ACCESS_KEY": "<AWS_SECRET_ACCESS_KEY>",
        "VERCEL_TOKEN": "<VERCEL_TOKEN>",
        "CLOUDFLARE_API_TOKEN": "<CLOUDFLARE_API_TOKEN>"
      }
    }
  }
}

Environment variables

AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
VERCEL_TOKEN
CLOUDFLARE_API_TOKEN

Replace the placeholders with your own credentials and keep them out of version control.

Setup

Environment variables

Related