Log inSubmit server
Cloudpulse logo

Cloudpulse

Cross-cloud MCP tools for mapping services, correlating logs, diagnosing links, and checking limits across AWS, Vercel, GCP, and Cloudflare.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Cloudpulse

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "cloudpulse": {
      "command": "npx",
      "args": [
        "-y",
        "cloudpulse-mcp"
      ],
      "env": {
        "AWS_ACCESS_KEY_ID": "YOUR_VALUE_HERE",
        "AWS_SECRET_ACCESS_KEY": "YOUR_VALUE_HERE",
        "AWS_PROFILE": "YOUR_VALUE_HERE",
        "AWS_REGION": "YOUR_VALUE_HERE",
        "VERCEL_TOKEN": "YOUR_VALUE_HERE",
        "VERCEL_TEAM_ID": "YOUR_VALUE_HERE",
        "GOOGLE_APPLICATION_CREDENTIALS": "YOUR_VALUE_HERE",
        "CLOUDFLARE_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The cloudpulse MCP server gives AI agents read-only visibility into AWS, Vercel, GCP, and Cloudflare infrastructure. It maps deployed services, combines Vercel and CloudWatch logs, checks connectivity between services and resources, and reports approaching quotas. Run it with npx or from a local build, then provide credentials through environment variables or existing AWS configuration. Reach for it when diagnosing cross-provider application failures or reviewing cloud resource capacity from an editor.

Use cases

  • Map services across configured cloud platforms before debugging
  • Correlate Vercel and AWS CloudWatch logs by time or trace ID
  • Diagnose connectivity between an application service and a cloud resource
  • Check cloud quotas before workloads approach their limits

Key features

  • Unified multi-cloud topology scanning
  • Vercel and CloudWatch log correlation
  • Service-link and security-group diagnostics
  • Quota monitoring with configurable warnings
  • Read-only credential handling

Tools4

What Cloudpulse lets your agent do. Expand a tool for its parameters.

Self-reported~77 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · cloudpulse-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads145Package downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Tools exposed4Callable tools this server registers over MCP.

How Cloudpulse works

What the cloudpulse MCP server does

The cloudpulse MCP server connects an MCP-compatible AI client to selected AWS, Vercel, GCP, and Cloudflare APIs. Its purpose is operational inspection rather than resource management: the tools read service metadata, logs, network-related configuration, and quota information without storing credentials or changing infrastructure.

The server is useful when an application spans providers and the relevant evidence is split between consoles. For example, an agent can inspect a Vercel deployment alongside AWS resources, or review Cloud Run, Cloud SQL, and Cloud Logging data when those credentials are configured.

How it works

Cloudpulse discovers which providers are configured and uses their APIs when a tool is called. AWS access can come from access-key environment variables, an AWS profile, or an EC2 instance role. Other providers use their documented token or application-credential environment variables. Values are read at call time, and the project states that credentials are neither logged nor persisted.

The cloudpulse MCP server communicates over MCP and exposes four tools. Inputs can narrow scans by platform, region, project, time range, trace ID, or other provider-specific values. Some fields are required for a particular operation, while optional fields use defaults such as the current time, the /aws/lambda log-group prefix, or an 80 percent warning threshold.

Setup and configuration

The quickest launch method is:

Terminal
npx cloudpulse-mcp

The package requires Node.js 18 or newer. Claude Desktop and Cursor can start it with an MCP configuration that invokes npx -y cloudpulse-mcp. VS Code 1.99 or newer with GitHub Copilot in Agent Mode uses a built project and starts dist/index.js as a stdio server. A source checkout can be installed with npm install, run during development with npm run dev, and compiled with npm run build.

Configure only the providers needed for the investigation. AWS supports AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY, AWS_PROFILE, or an instance role. Vercel uses VERCEL_TOKEN, with VERCEL_TEAM_ID available for team access. GCP uses GOOGLE_APPLICATION_CREDENTIALS. Cloudflare uses CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID.

Tools and capabilities

  • list_cloud_topology returns a unified map of active services across configured platforms. Platform filters and an AWS region can be supplied.
  • get_correlated_logs merges Vercel and AWS CloudWatch events into one timeline. It accepts a required start time, an optional end time, trace or request ID, project, log-group prefix, and region.
  • diagnose_service_link investigates why a source service cannot reach a target. It checks relevant Vercel database environment variables, AWS security-group ingress, and external API reachability; ports can be supplied or inferred for common targets.
  • check_resource_limits queries quotas and flags usage at a configurable threshold, defaulting to 80 percent.

Limitations and notes

The current implementation is read-only and does not provide deployment, mutation, or remediation operations. Cross-provider log correlation specifically covers Vercel and AWS CloudWatch, while topology and quota coverage depends on configured credentials and supported provider data. The documented roadmap lists diagnostic playbooks for CORS, 504 timeouts, and cold-start loops as future work, so those workflows should not be assumed to be built in. The project is licensed under MIT.

Read the full README View source on GitHub

Reviews

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

Frequently Asked Questions about Cloudpulse

cloudpulse is an MCP server that connects AI agents to AWS, Vercel, GCP, and Cloudflare for read-only infrastructure inspection. Its main tools map cloud topology, merge Vercel and AWS CloudWatch logs, diagnose links between services and resources, and check quotas for resources nearing configured usage thresholds.

Run `npx cloudpulse-mcp` with Node.js 18 or newer. You can also clone the repository, run `npm install`, use `npm run dev` during development, or build the project with `npm run build` before starting its compiled entry point.

Yes, cloudpulse works with Cursor through a project-level `.cursor/mcp.json` configuration. The example starts `npx -y cloudpulse-mcp` and passes values such as `VERCEL_TOKEN` and `AWS_REGION` through the server environment.

The cloudpulse MCP server needs credentials only for the providers you want to inspect. AWS accepts access keys, an AWS profile, or an EC2 role; Vercel uses `VERCEL_TOKEN`; GCP uses `GOOGLE_APPLICATION_CREDENTIALS`; and Cloudflare uses an API token plus account ID.

No, cloudpulse is documented as read-only and does not provide resource mutation or deployment tools. Its operations inspect topology, logs, connectivity-related settings, and quota usage, while credentials are read at call time and not stored.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

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 PreviewCloudpulse AllMCPs Directory Badge
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>