Cloudpulse

Cross-cloud observability for AI agents. Covers AWS, GCP, Vercel, and Cloudflare.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

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

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

CloudPulse MCP Server

Cross-cloud infrastructure visibility for AI agents. Diagnose issues across AWS, Vercel, GCP, and Cloudflare without ever leaving your editor.

Why CloudPulse?

Pain point	CloudPulse fix
Frontend error on Vercel → must open AWS console	`get_correlated_logs` merges both timelines automatically
AI can't see if an SG blocks port 5432	`diagnose_service_link` inspects the security group rules live
Hitting Lambda concurrency limits silently	`check_resource_limits` warns at 80% usage
Topology unknown before debugging	`list_cloud_topology` maps every active service in seconds

Quick Start

1. Install / run with npx

Terminal

npx cloudpulse-mcp

The server auto-detects credentials already present on your machine (AWS CLI, environment variables, etc.).

2. Configure your AI client

Claude Desktop – add to ~/Library/Application Support/Claude/claude_desktop_config.json:

config.json

{
  "mcpServers": {
    "cloudpulse": {
      "command": "npx",
      "args": ["-y", "cloudpulse-mcp"],
      "env": {
        "VERCEL_TOKEN": "<your-vercel-token>",
        "AWS_PROFILE": "default",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

Cursor – add to .cursor/mcp.json in your project:

config.json

{
  "mcpServers": {
    "cloudpulse": {
      "command": "npx",
      "args": ["-y", "cloudpulse-mcp"],
      "env": {
        "VERCEL_TOKEN": "<your-vercel-token>",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

VS Code + GitHub Copilot (Agent Mode) – requires VS Code 1.99+ and the GitHub Copilot extension.

First, build the project:

Terminal

npm run build

Then create .vscode/mcp.json in this repository:

config.json

{
  "servers": {
    "cloudpulse": {
      "type": "stdio",
      "command": "node",
      "args": ["${workspaceFolder}/dist/index.js"],
      "env": {
        "VERCEL_TOKEN": "${env:VERCEL_TOKEN}",
        "AWS_REGION": "${env:AWS_REGION}",
        "AWS_PROFILE": "${env:AWS_PROFILE}"
      }
    }
  }
}

${env:VAR} reads from your shell environment — no secrets in source control.

To use: open Copilot Chat, switch to Agent mode, click Select Tools and enable the CloudPulse tools, then ask naturally:

Code

Why can't my Vercel project reach AWS RDS instance "my-db"?

Credentials & Security

CloudPulse follows a read-only, no-storage policy:

Credential	How to provide
AWS	`AWS_ACCESS_KEY_ID` + `AWS_SECRET_ACCESS_KEY`, or `AWS_PROFILE`, or EC2 instance role
Vercel	`VERCEL_TOKEN` (personal access token from vercel.com/account/tokens)
Vercel Team	`VERCEL_TEAM_ID` (optional)
GCP	`GOOGLE_APPLICATION_CREDENTIALS`
Cloudflare	`CLOUDFLARE_API_TOKEN` + `CLOUDFLARE_ACCOUNT_ID`

No credentials are logged or stored. All values are read from environment variables at call time.

Available Tools

`list_cloud_topology`

Scan all configured platforms and return a unified service map.

Code

Input (all optional):
  platforms       – ["aws", "vercel"]  filter platforms
  aws_region      – "us-east-1"

`get_correlated_logs`

Fetch and merge logs from Vercel + AWS CloudWatch into one timeline.

Code

Input:
  start_time *    – ISO-8601 or epoch ms  e.g. "2024-06-01T10:00:00Z"
  end_time        – defaults to now
  trace_id        – filter by trace/request ID across all sources
  aws_log_group_prefix  – default "/aws/lambda"
  vercel_project  – project name or ID
  aws_region

`diagnose_service_link`

Check why service A can't reach resource B.

Code

Input:
  source_service *  – "vercel" | "lambda" | "ec2" | ...
  target_resource * – "<type>:<id>"  e.g. "aws-rds:my-db", "external-api:https://..."
  port              – auto-detected (5432 for RDS, 443 for APIs, ...)
  vercel_project
  aws_region

Checks performed:

Vercel env vars contain a DATABASE_URL / DB_URL
AWS Security Group allows inbound TCP on the required port
External API HEAD reachability test

`check_resource_limits`

Query quotas and flag resources nearing their limits.

Code

Input (all optional):
  platforms        – filter platforms
  warn_threshold   – usage % to warn at (default 80)
  aws_region

Roadmap

Phase	Status	Scope
1 – MVP	✅ Done	Vercel + AWS (Lambda, RDS, CloudWatch, Security Groups, S3)
2 – Extend	✅ Done	GCP Cloud Run + Cloud SQL + Logging; Cloudflare Workers + Pages; S3 CORS
3 – Intelligence	🔜	Pre-built diagnostic playbooks for CORS, 504 timeout, cold-start loops

Development

bash

git clone https://github.com/Galadriel-Tech-Solutions/cloudpulse-mcp
cd cloudpulse-mcp
npm install
npm run dev        # run from source with tsx
npm run build      # compile to dist/

Project structure

Code

src/
├── index.ts                     # MCP server + tool registration
├── types.ts                     # shared domain types
├── utils.ts                     # concurrency, formatting helpers
├── providers/
│   ├── aws/
│   │   ├── index.ts             # client factory + isAWSConfigured()
│   │   ├── cloudwatch.ts        # CloudWatch Logs
│   │   ├── lambda.ts            # Lambda function listing
│   │   ├── rds.ts               # RDS/Aurora instances & clusters
│   │   ├── ec2.ts               # Security Group inspection
│   │   ├── s3.ts                # S3 buckets + CORS checks
│   │   └── quotas.ts            # Service Quotas API
│   ├── gcp/
│   │   ├── index.ts             # isGCPConfigured() + resolveGCPProject()
│   │   ├── cloud-run.ts         # Cloud Run services
│   │   ├── cloud-sql.ts         # Cloud SQL instances (sqladmin v1beta4)
│   │   └── logging.ts           # Cloud Logging
│   ├── cloudflare/
│   │   └── index.ts             # Pages, Workers, Worker tail logs (WebSocket)
│   └── vercel/
│       └── index.ts             # Vercel REST API v9
└── tools/
    ├── list-cloud-topology.ts
    ├── get-correlated-logs.ts
    ├── diagnose-service-link.ts
    └── check-resource-limits.ts

Adding a new cloud platform

Create src/providers/<platform>/index.ts exporting:
- is<Platform>Configured(): boolean
- Provider-specific data functions
Wire the functions into the relevant tools under src/tools/
Add the platform name to the CloudPlatform union in src/types.ts

License

MIT © CloudPulse Contributors

Read the full README →View source on GitHub →

Related MCP Servers

View all in Cloud Platforms View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Cloudpulse

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "cloudpulse": { "command": "npx", "args": ["-y", "cloudpulse"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/cloudpulse?style=directory)](https://allmcps.com/mcp/cloudpulse)

HTML Embed

<a href="https://allmcps.com/mcp/cloudpulse"><img src="https://allmcps.com/api/badge/cloudpulse?style=directory" alt="Cloudpulse on AllMCPs" /></a>

Technical Specs & Signals

CategoryCloud Platforms

36Quality signal: Fair · 36/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools16/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in ☁️ Cloud Platforms →Best MCP servers for Cloud Platforms →Alternatives to Cloudpulse →Install in Claude Desktop Install in Cursor Install in VS Code

Cloudpulse

Cross-cloud observability for AI agents. Covers AWS, GCP, Vercel, and Cloudflare.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

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

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

CloudPulse MCP Server

Cross-cloud infrastructure visibility for AI agents. Diagnose issues across AWS, Vercel, GCP, and Cloudflare without ever leaving your editor.

Why CloudPulse?

Pain point	CloudPulse fix
Frontend error on Vercel → must open AWS console	`get_correlated_logs` merges both timelines automatically
AI can't see if an SG blocks port 5432	`diagnose_service_link` inspects the security group rules live
Hitting Lambda concurrency limits silently	`check_resource_limits` warns at 80% usage
Topology unknown before debugging	`list_cloud_topology` maps every active service in seconds

Quick Start

1. Install / run with npx

Terminal

npx cloudpulse-mcp

The server auto-detects credentials already present on your machine (AWS CLI, environment variables, etc.).

2. Configure your AI client

Claude Desktop – add to ~/Library/Application Support/Claude/claude_desktop_config.json:

config.json

{
  "mcpServers": {
    "cloudpulse": {
      "command": "npx",
      "args": ["-y", "cloudpulse-mcp"],
      "env": {
        "VERCEL_TOKEN": "<your-vercel-token>",
        "AWS_PROFILE": "default",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

Cursor – add to .cursor/mcp.json in your project:

config.json

{
  "mcpServers": {
    "cloudpulse": {
      "command": "npx",
      "args": ["-y", "cloudpulse-mcp"],
      "env": {
        "VERCEL_TOKEN": "<your-vercel-token>",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

VS Code + GitHub Copilot (Agent Mode) – requires VS Code 1.99+ and the GitHub Copilot extension.

First, build the project:

Terminal

npm run build

Then create .vscode/mcp.json in this repository:

config.json

{
  "servers": {
    "cloudpulse": {
      "type": "stdio",
      "command": "node",
      "args": ["${workspaceFolder}/dist/index.js"],
      "env": {
        "VERCEL_TOKEN": "${env:VERCEL_TOKEN}",
        "AWS_REGION": "${env:AWS_REGION}",
        "AWS_PROFILE": "${env:AWS_PROFILE}"
      }
    }
  }
}

${env:VAR} reads from your shell environment — no secrets in source control.

To use: open Copilot Chat, switch to Agent mode, click Select Tools and enable the CloudPulse tools, then ask naturally:

Code

Why can't my Vercel project reach AWS RDS instance "my-db"?

Credentials & Security

CloudPulse follows a read-only, no-storage policy:

Credential	How to provide
AWS	`AWS_ACCESS_KEY_ID` + `AWS_SECRET_ACCESS_KEY`, or `AWS_PROFILE`, or EC2 instance role
Vercel	`VERCEL_TOKEN` (personal access token from vercel.com/account/tokens)
Vercel Team	`VERCEL_TEAM_ID` (optional)
GCP	`GOOGLE_APPLICATION_CREDENTIALS`
Cloudflare	`CLOUDFLARE_API_TOKEN` + `CLOUDFLARE_ACCOUNT_ID`

No credentials are logged or stored. All values are read from environment variables at call time.

Available Tools

`list_cloud_topology`

Scan all configured platforms and return a unified service map.

Code

Input (all optional):
  platforms       – ["aws", "vercel"]  filter platforms
  aws_region      – "us-east-1"

`get_correlated_logs`

Fetch and merge logs from Vercel + AWS CloudWatch into one timeline.

Code

Input:
  start_time *    – ISO-8601 or epoch ms  e.g. "2024-06-01T10:00:00Z"
  end_time        – defaults to now
  trace_id        – filter by trace/request ID across all sources
  aws_log_group_prefix  – default "/aws/lambda"
  vercel_project  – project name or ID
  aws_region

`diagnose_service_link`

Check why service A can't reach resource B.

Code

Input:
  source_service *  – "vercel" | "lambda" | "ec2" | ...
  target_resource * – "<type>:<id>"  e.g. "aws-rds:my-db", "external-api:https://..."
  port              – auto-detected (5432 for RDS, 443 for APIs, ...)
  vercel_project
  aws_region

Checks performed:

Vercel env vars contain a DATABASE_URL / DB_URL
AWS Security Group allows inbound TCP on the required port
External API HEAD reachability test

`check_resource_limits`

Query quotas and flag resources nearing their limits.

Code

Input (all optional):
  platforms        – filter platforms
  warn_threshold   – usage % to warn at (default 80)
  aws_region

Roadmap

Phase	Status	Scope
1 – MVP	✅ Done	Vercel + AWS (Lambda, RDS, CloudWatch, Security Groups, S3)
2 – Extend	✅ Done	GCP Cloud Run + Cloud SQL + Logging; Cloudflare Workers + Pages; S3 CORS
3 – Intelligence	🔜	Pre-built diagnostic playbooks for CORS, 504 timeout, cold-start loops

Development

bash

git clone https://github.com/Galadriel-Tech-Solutions/cloudpulse-mcp
cd cloudpulse-mcp
npm install
npm run dev        # run from source with tsx
npm run build      # compile to dist/

Project structure

Code

src/
├── index.ts                     # MCP server + tool registration
├── types.ts                     # shared domain types
├── utils.ts                     # concurrency, formatting helpers
├── providers/
│   ├── aws/
│   │   ├── index.ts             # client factory + isAWSConfigured()
│   │   ├── cloudwatch.ts        # CloudWatch Logs
│   │   ├── lambda.ts            # Lambda function listing
│   │   ├── rds.ts               # RDS/Aurora instances & clusters
│   │   ├── ec2.ts               # Security Group inspection
│   │   ├── s3.ts                # S3 buckets + CORS checks
│   │   └── quotas.ts            # Service Quotas API
│   ├── gcp/
│   │   ├── index.ts             # isGCPConfigured() + resolveGCPProject()
│   │   ├── cloud-run.ts         # Cloud Run services
│   │   ├── cloud-sql.ts         # Cloud SQL instances (sqladmin v1beta4)
│   │   └── logging.ts           # Cloud Logging
│   ├── cloudflare/
│   │   └── index.ts             # Pages, Workers, Worker tail logs (WebSocket)
│   └── vercel/
│       └── index.ts             # Vercel REST API v9
└── tools/
    ├── list-cloud-topology.ts
    ├── get-correlated-logs.ts
    ├── diagnose-service-link.ts
    └── check-resource-limits.ts

Adding a new cloud platform

Create src/providers/<platform>/index.ts exporting:
- is<Platform>Configured(): boolean
- Provider-specific data functions
Wire the functions into the relevant tools under src/tools/
Add the platform name to the CloudPlatform union in src/types.ts

License

Read the full README →View source on GitHub →

Related MCP Servers

View all in Cloud Platforms View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Cloudpulse

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "cloudpulse": { "command": "npx", "args": ["-y", "cloudpulse"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/cloudpulse?style=directory)](https://allmcps.com/mcp/cloudpulse)

HTML Embed

<a href="https://allmcps.com/mcp/cloudpulse"><img src="https://allmcps.com/api/badge/cloudpulse?style=directory" alt="Cloudpulse on AllMCPs" /></a>

Technical Specs & Signals

CategoryCloud Platforms

36Quality signal: Fair · 36/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools16/30

Adoption & activity1/15

Community engagement0/10

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in ☁️ Cloud Platforms →Best MCP servers for Cloud Platforms →Alternatives to Cloudpulse →Install in Claude Desktop Install in Cursor Install in VS Code