Cloudpulse
Let your agent pull cross-cloud health and observability signals from AWS, GCP, Vercel, and Cloudflare in one MCP session.
Overview
Cloudpulse is an Operate-phase MCP server for cross-cloud observability across AWS, GCP, Vercel, and Cloudflare via stdio.
What is this MCP server?
- Cross-cloud coverage: AWS, GCP, Vercel, and Cloudflare from one MCP server
- stdio npm package cloudpulse-mcp v0.1.2
- Credential-driven setup via AWS keys, VERCEL_TOKEN, GCP service account path, and CLOUDFLARE_API_TOKEN
- Built for AI agents that triage incidents without switching vendor consoles
- Developer Tools–adjacent ops surface rather than a single-cloud CLI wrapper
- 4 cloud platforms: AWS, GCP, Vercel, Cloudflare
- Package cloudpulse-mcp version 0.1.2
- stdio transport
Community signal: 1 GitHub stars.
What problem does it solve?
Your stack spans multiple clouds and your agent cannot see deployment or infra status without you pasting screenshots from each console.
Who is it for?
Solo builders running production on Vercel plus Cloudflare plus AWS or GCP who want agent-assisted incident triage.
Skip if: Single-host hobby projects with no cloud accounts, or teams that need enterprise-grade SLO dashboards out of the box.
What do I get? / Deliverables
After MCP registration with provider tokens, the agent can query Cloudpulse-backed tools for unified multi-vendor operational context.
- Agent-accessible cross-provider operational queries
- Faster multi-console incident context inside the IDE
- Credential-scoped MCP integration v0.1.2
Recommended MCP Servers
Journey fit
Observability belongs in Operate when the product is live across multiple providers and you need unified signals, not during first prototype wiring. Monitoring is the canonical shelf for uptime, metrics, and platform status checks that agents can query on demand.
How it compares
Multi-cloud observability MCP, not a single-provider IaC skill or hosted APM product.
Common Questions / FAQ
Who is Cloudpulse for?
Indie operators and agent users who manage live apps split across AWS, GCP, Vercel, and Cloudflare and want one MCP entry for status-style checks.
When should I use Cloudpulse?
Use it during Operate when debugging outages, verifying deploy health, or comparing signals across providers from Claude Code or Cursor.
How do I add Cloudpulse to my agent?
Install cloudpulse-mcp from npm, configure stdio MCP, and set AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, VERCEL_TOKEN, GOOGLE_APPLICATION_CREDENTIALS, GOOGLE_CLOUD_PROJECT, and CLOUDFLARE_API_TOKEN as needed.