Cloudpulse MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add cloudpulse -- npx -y cloudpulse-mcp

{
  "mcpServers": {
    "cloudpulse": {
      "args": [
        "-y",
        "cloudpulse-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.cloudpulse]
command = "npx"
args = ["-y", "cloudpulse-mcp"]

{
  "mcpServers": {
    "cloudpulse": {
      "args": [
        "-y",
        "cloudpulse-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "cloudpulse": {
      "args": [
        "-y",
        "cloudpulse-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: AWS_ACCESS_KEY_ID (AWS access key ID), AWS_SECRET_ACCESS_KEY (AWS secret access key), AWS_REGION (AWS region (e.g. us-east-1)), VERCEL_TOKEN (Vercel personal access token), GOOGLE_APPLICATION_CREDENTIALS (Path to GCP service account JSON file), GOOGLE_CLOUD_PROJECT (GCP project ID), CLOUDFLARE_API_TOKEN (Cloudflare API token), CLOUDFLARE_ACCOUNT_ID (Cloudflare account ID). The author declared them in the registry entry; get the values from the project itself.