Cloudscope
Ask your agent for Azure and GCP spend, forecasts, budget anomalies, idle resources, and tag hygiene from one MCP server.
Overview
Cloudscope is a MCP server for the Operate phase that surfaces Azure and GCP cost, forecast, anomaly, budget, idle-resource, and tag data to your agent.
What is this MCP server?
- Unified Azure + GCP cost management MCP (cloudscope-mcp v0.3.3 on npm)
- Spending, forecasts, anomalies, budgets, idle resources, and tagging workflows
- Azure auth via DefaultAzureCredential (e.g. az login) or optional service principal env vars
- GCP via GOOGLE_CLOUD_PROJECT and related GCP billing configuration
- Server package version 0.3.3 (cloudscope-mcp on npm)
- stdio transport
- Documented env vars include AZURE_SUBSCRIPTION_ID, AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, and GOOGLE_CLO
What problem does it solve?
Indie founders on Azure or GCP lose margin because spend spikes, untagged resources, and idle assets are buried in separate cloud consoles.
Who is it for?
Solo builders already on Azure and/or GCP who want agent-assisted FinOps checks during weekly ops reviews.
Skip if: Teams on AWS-only stacks, builders with no cloud bills yet, or anyone who needs deploy/provision automation instead of cost intelligence.
What do I get? / Deliverables
After cloudscope-mcp is configured with cloud credentials, you can interrogate multi-cloud cost health from Claude Code or Cursor instead of manual console digging.
- Agent-queryable Azure and GCP spend and forecast views
- Budget, anomaly, and idle-resource signals for cleanup decisions
- Tag and cost-allocation visibility across configured clouds
Recommended MCP Servers
Journey fit
Cloud bills and waste surface after launch when solo builders run real subscriptions; operate is where cost control meets production infra. Infra subphase matches subscription-scoped cost APIs, budgets, and idle resource discovery rather than error triage or support tickets.
How it compares
Multi-cloud FinOps MCP, not an application error-monitoring or CI deploy server.
Common Questions / FAQ
Who is Cloudscope for?
Developers and solo operators running workloads on Azure and/or GCP who want MCP-driven visibility into spend, budgets, anomalies, idle resources, and tags.
When should I use Cloudscope?
Use it in operate when reviewing monthly bills, investigating cost spikes, rightsizing idle resources, or auditing tag coverage before scaling traffic.
How do I add Cloudscope to my agent?
Install cloudscope-mcp (v0.3.3) as a stdio MCP server, set Azure variables and/or GCP project billing access per README, authenticate with az login or a service principal, then expose the server in your MCP client config.