Cloudscope

io.github.alexpotaPublished by GitHub account alexpotav0.3.3Updated Oct 24, 2026

Azure + GCP cost management: spending, forecasts, anomalies, budgets, idle resources, and tags.

Overview

AI-generated overview

Read-only MCP server that lets an assistant query Azure and GCP cloud costs: spend, forecasts, anomalies, budgets, idle resources and tags.

What you can do
  • Analyze spend: cost summaries by service, group or region, costs by tag, period comparisons, top spending resources, and combined costs across Azure subscriptions or GCP projects
  • Monitor: detect spending anomalies, check budget status and projected overage, and forecast future spend
  • Optimize: list cost recommendations, find idle resources with cost estimates, and find untagged resources
  • Look up context: current date and month bounds, Azure subscriptions and GCP projects
  • Run guided report prompts such as monthly cost review, waste audit, cost spike investigation, executive summary and chargeback report
When to use it
Useful when you want an assistant to answer questions about your Azure or GCP bill, investigate a cost increase, audit wasted or idle resources, or produce a recurring cost review or chargeback report without reading raw billing data yourself.
Requirements
Runs locally via npx (Node.js). Azure: Azure CLI logged in with az login and the Cost Management Reader role; optionally AZURE_SUBSCRIPTION_ID, or a service principal via AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_SECRET. GCP: gcloud application default credentials, BigQuery billing export enabled, GOOGLE_CLOUD_PROJECT and GCP_BILLING_TABLE, plus BigQuery Data Viewer and Job User roles; optional GCP_PROJECT_ID, GCP_BILLING_ACCOUNT_ID and GOOGLE_APPLICATION_CREDENTIALS.
Before you install
The server is described as read-only and cannot create, modify or delete cloud resources. It reads cloud billing data using your existing CLI credentials or a service principal secret (AZURE_CLIENT_SECRET) or service account key file (GOOGLE_APPLICATION_CREDENTIALS), so protect those credentials. GCP BigQuery queries are billed by data scanned (first 1 TiB per month free); typical queries are stated to cost under a cent each.

Installation

In SourceWeft

  1. Open Cloudscope in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

CloudScope MCP

Ask your AI about your cloud bill.

[npm version] [MCP Registry] [Node.js] [TypeScript] [License: MIT]

What you get

Ask once: "Give me this month's cost review" — and CloudScope runs the full workflow (spend, deltas, anomalies, idle resources, budgets, forecast) and hands back a decision-ready report, not raw numbers to interpret yourself:

TL;DR

Month-to-date Azure spend is $4,312 (May 1–29), tracking +11% vs April. The mover is App Service (+$280) — a new staging slot left running. 2 idle resources cost $94/month; prod-budget is at 78% with 2 days left. Top action: delete the orphaned managed disk → save $63/month.

Spend This Month

ServiceCost%
Virtual Machines$2,14049.6%
App Service$89020.6%
Storage$61214.2%
Redis Cache$4109.5%
Networking$2606.0%

vs Last Month

+$427 (+11%) overall. App Service +$280 drove most of it; everything else flat. → new staging-slot-2, created May 12, never torn down.

Idle & Wasted Resources

ResourceType$/month
orphaned-osdisk-01Managed Disk$63
old-lb-ipPublic IP$31

Budget Status

prod-budget — 78% used, $4,312 / $5,500, on track (2 days left).

Recommended Actions

  1. Delete orphaned-osdisk-01 (unattached 40 days) → $63/month
  2. Tear down staging-slot-2 if staging is idle → ~$280/month
  3. Release old-lb-ip (no binding) → $31/month

Illustrative example showing the report format. Run /cloudscope:monthly-cost-review against your own subscription for live numbers.

Install

Claude CodeCursorVS Code
claude mcp add cloudscope -- npx -y cloudscope-mcpInstallInstall

Azure is auto-detected from your az login session. GCP requires BigQuery billing export setup (see below).

Supported Providers

ProviderStatus
Azure✅ Supported
GCP✅ Supported
AWSUse AWS's official server

Prerequisites

Azure

  • Azure CLI installed and logged in (az login)
  • Cost Management Reader role on the subscription

GCP

  • gcloud CLI installed and logged in (gcloud auth application-default login)
  • Billing export to BigQuery enabled — this is a one-time manual setup step, not enabled by default (the detailed export is recommended for resource-level cost queries)
  • BigQuery Data Viewer + BigQuery Job User roles on the dataset project
  • Note: BigQuery on-demand queries cost $6.25 per TiB scanned (pricing). The first 1 TiB/month is free. Billing export tables are small — typical CloudScope queries cost <$0.01 each.

Configuration

Azure (zero-config)

CloudScope auto-detects your subscription from az login. Just add the server:

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

To target a specific subscription, add an env block:

json
{  "mcpServers": {    "cloudscope": {      "command": "npx",      "args": ["-y", "cloudscope-mcp"],      "env": {        "AZURE_SUBSCRIPTION_ID": "your-subscription-id"      }    }  }}
Advanced: Service Principal (CI/CD & automated environments)
VariableDescription
AZURE_TENANT_IDAzure AD tenant ID
AZURE_CLIENT_IDApp registration client ID
AZURE_CLIENT_SECRETApp registration client secret

Set these alongside AZURE_SUBSCRIPTION_ID in the env block above.

GCP

GCP requires a BigQuery billing export table. Find your table name in GCP Console > Billing > Billing export > BigQuery export.

json
{  "mcpServers": {    "cloudscope": {      "command": "npx",      "args": ["-y", "cloudscope-mcp"],      "env": {        "GOOGLE_CLOUD_PROJECT": "my-project",        "GCP_BILLING_TABLE": "my-project.my_dataset.gcp_billing_export_resource_v1_XXXXXX"      }    }  }}

Set GOOGLE_CLOUD_PROJECT to your GCP project ID. Override with GCP_PROJECT_ID if your billing dataset lives in a different project.

These variables apply only when using GCP; Azure-only users can skip them.

VariableDescriptionRequired
GOOGLE_CLOUD_PROJECTGCP project IDYes
GCP_BILLING_TABLEFully-qualified BigQuery table (project.dataset.table)Yes
GCP_PROJECT_IDOverride project ID if different from GOOGLE_CLOUD_PROJECTNo
GCP_BILLING_ACCOUNT_IDBilling account ID for budget monitoringNo
GOOGLE_APPLICATION_CREDENTIALSPath to service account JSON key fileNo

Both Providers

json
{  "mcpServers": {    "cloudscope": {      "command": "npx",      "args": ["-y", "cloudscope-mcp"],      "env": {        "AZURE_SUBSCRIPTION_ID": "your-subscription-id",        "GOOGLE_CLOUD_PROJECT": "my-project",        "GCP_BILLING_TABLE": "my-project.my_dataset.gcp_billing_export_resource_v1_XXXXXX"      }    }  }}

Azure is auto-detected from az login. Add AZURE_SUBSCRIPTION_ID to target a specific subscription.

Example Questions

  • "How much did Azure cost last month?"
  • "Show GCP spending by service for the last 7 days"
  • "Any cost anomalies this week on GCP?"
  • "What will Azure cost next month?"
  • "Show me cost optimization recommendations for GCP"
  • "Compare Azure and GCP costs across all projects and subscriptions"

Security

CloudScope is read-only. It cannot create, modify, or delete any cloud resources. Azure uses Cost Management Reader permissions. GCP uses BigQuery Data Viewer + Job User with no write access.

FAQ

Does this modify my cloud resources? No. Read-only access only.

Do I need a service principal? No. az login (Azure) or gcloud auth application-default login (GCP) works for local use.

Does the Azure Cost Management API cost money? No. It's free.

Do GCP BigQuery cost queries cost money? Yes, but typically <$0.01 per query ($6.25/TiB scanned, first 1 TiB/month free). See BigQuery pricing.

Can I use both Azure and GCP at the same time? Yes. Configure both sets of env vars and CloudScope queries whichever provider you specify in each tool call.

Development

bash
git clone https://github.com/alexpota/cloudscope-mcp.gitcd cloudscope-mcpnpm installnpm run buildnpm testnpx @modelcontextprotocol/inspector node dist/index.js

Reference

Tools

Most tools accept a provider parameter (azure or gcp); the provider-specific tools (list_subscriptions, list_projects, and the cross-account tools get_cross_subscription_costs / get_cross_project_costs) are fixed to their own cloud. The default provider is auto-detected based on which providers are configured.

Cost Analysis

ToolDescriptionKey Parameters
get_cost_summarySpending breakdown by service, group, or regionstart_date, end_date, group_by
get_cost_by_tagCosts grouped by a tag/label keytag_key, start_date, end_date
compare_periodsSide-by-side cost comparison of two date rangesperiod_a_start/end, period_b_start/end
top_spending_resourcesMost expensive individual resourcesdays, limit
get_cross_subscription_costsCombined costs across Azure subscriptionssubscription_ids, start_date, end_date
get_cross_project_costsCombined costs across GCP projectsproject_ids, start_date, end_date

Monitoring

ToolDescriptionKey Parameters
detect_anomaliesFind spending spikes vs previous perioddays, threshold
check_budgetsBudget status, current spend, projected overage(none)
get_cost_forecastPredict spending based on current trendsdays

Optimization

ToolDescriptionKey Parameters
list_recommendationsCost optimization suggestions (Azure Advisor / GCP Recommender)category
find_idle_resourcesProvisioned but unused resources with cost estimates(none)
find_untagged_resourcesResources with no tags/labels (cost attribution gaps)(none)

Utility

ToolDescriptionKey Parameters
get_current_dateToday's date and current/previous month bounds(none)
list_subscriptionsAzure subscriptions with active indicator(none)
list_projectsGCP projects with active indicator(none)

Prompts

Guided workflows that produce structured reports. All prompts accept an optional provider argument (azure or gcp). In Claude Code, type /cloudscope: to see all prompts. In Claude Desktop, click the + button → Connectors → cloudscope.

PromptDescriptionArguments
monthly-cost-reviewComplete monthly review: spending, last-month comparison, anomalies, top resources, budgets, forecast, savings opportunitiesprovider (optional)
waste-auditFind wasted spend: top resources, optimization recommendations, at-risk budgets, total potential savingsprovider (optional)
cost-spike-investigationRoot-cause analysis for a cost increase: which services, which resources, trend vs one-time, recommended actionsdays (optional), provider (optional)
executive-summaryBrief non-technical cost summary for leadership: spend, trend, budget status, top drivers, forecast, key recommendationprovider (optional)
chargeback-reportCost allocation by tag/label key for chargeback: spending per value, untagged resources, tagged vs untagged split, month-over-monthtag_key (required), provider (optional)

License

MIT

Source: README.md at commit 99a2a7a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts