Cloudpulse MCP Server

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

Local serverstdio

What is the Cloudpulse MCP server?

Connect Cloudpulse to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Cross-cloud observability for AI agents. Covers AWS, GCP, Vercel, and Cloudflare. The cloudpulse mcp server is what makes that connection.

What the server does

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

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • list_cloud_topology — Scan all configured platforms and return a unified service map
  • get_correlated_logs — Fetch and merge logs from Vercel + AWS CloudWatch into one timeline
  • diagnose_service_link — The diagnose_service_link tool exposed by this server
  • check_resource_limits — The check_resource_limits tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: VERCEL_TOKEN, AWS_PROFILE, AWS_REGION, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, VERCEL_TEAM_ID, CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

The server ships on npm as cloudpulse-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cloudpulse's toolset — list_cloud_topology, get_correlated_logs, diagnose_service_link and 1 more — is a fair guide to whether it matches your workflow. It is maintained by lhf552004; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
list_cloud_topologyScan all configured platforms and return a unified service map.
get_correlated_logsFetch and merge logs from Vercel + AWS CloudWatch into one timeline.
diagnose_service_linkThe diagnose_service_link tool exposed by this server.
check_resource_limitsThe check_resource_limits tool exposed by this server.

How to install the Cloudpulse MCP server

{
  "mcpServers": {
    "cloudpulse": {
      "command": "npx",
      "args": ["-y", "cloudpulse-mcp"],
      "env": {
        "VERCEL_TOKEN": "your-value",
        "AWS_PROFILE": "your-value",
        "AWS_REGION": "your-value",
        "AWS_ACCESS_KEY_ID": "your-value",
        "AWS_SECRET_ACCESS_KEY": "your-value",
        "VERCEL_TEAM_ID": "your-value",
        "CLOUDFLARE_API_TOKEN": "your-value",
        "CLOUDFLARE_ACCOUNT_ID": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
VERCEL_TOKENCredential the server authenticates with.Yes
AWS_PROFILEConfiguration value read at startup.Optional
AWS_REGIONConfiguration value read at startup.Optional
AWS_ACCESS_KEY_IDCredential the server authenticates with.Yes
AWS_SECRET_ACCESS_KEYCredential the server authenticates with.Yes
VERCEL_TEAM_IDConfiguration value read at startup.Optional
CLOUDFLARE_API_TOKENCredential the server authenticates with.Yes
CLOUDFLARE_ACCOUNT_IDConfiguration value read at startup.Optional

Example prompts to try

  • Use Cloudpulse to list cloud topology.
  • Use Cloudpulse to get correlated logs.
  • Use Cloudpulse to diagnose service link.

Frequently asked questions

It connects Cloudpulse to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (list_cloud_topology, get_correlated_logs, diagnose_service_link, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cloudpulse directly.