CloudScope MCP is a read-only Model Context Protocol server that provides AI assistants with cloud cost management capabilities across Azure and GCP. No cloud resources are created, modified, or deleted.
Cost Analysis
Get cost breakdowns by service, resource group, tag, or region for any date range
Compare spending across two time periods to spot changes
Identify the most expensive individual resources
Analyze costs by tag/label for chargeback and cost allocation
Combine costs across multiple Azure subscriptions or GCP projects
Monitoring & Forecasting
Detect spending anomalies by comparing recent days against a prior period
Check budget status: current spend, percentage used, forecast, and overage risk
Forecast future spending using linear trend analysis from the last 30 days
Optimization & Governance
Fetch cost-saving recommendations from Azure Advisor or GCP Recommender, filtered by category (compute, storage, networking)
Identify idle/unused resources (unattached disks, orphaned IPs, idle VMs) with estimated monthly savings
Find untagged resources that hinder cost attribution
Utility Tools
Retrieve the current date and month boundaries for use in queries
List accessible Azure subscriptions or GCP projects
Guided Workflows
Monthly cost review — Full report covering spend, comparisons, anomalies, budgets, and forecasts
Waste audit — Focused report on idle resources and optimization opportunities
Cost spike investigation — Root-cause analysis for unexpected cost increases
Executive summary — Brief, non-technical cost overview for leadership
Chargeback report — Cost allocation by tag/label for internal billing
Provides tools for querying and analyzing cloud costs from GCP (Google Cloud Platform), including cost summaries, anomaly detection, budget status, idle resource identification, and cross-project cost comparisons.
Ask your AI about your cloud bill.
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:
Related MCP server: Azure FinOps Elite
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-budgetis at 78% with 2 days left. Top action: delete the orphaned managed disk → save $63/month.Spend This Month
Service
Cost
%
Virtual Machines
$2,140
49.6%
App Service
$890
20.6%
Storage
$612
14.2%
Redis Cache
$410
9.5%
Networking
$260
6.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
Resource
Type
$/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
Delete
orphaned-osdisk-01(unattached 40 days) → $63/monthTear down
staging-slot-2if staging is idle → ~$280/monthRelease
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.
Azure is auto-detected from your
az loginsession. GCP requires BigQuery billing export setup (see below).
Provider | Status |
Azure | ✅ Supported |
GCP | ✅ Supported |
AWS |
Azure CLI installed and logged in (az login)
Cost Management Reader role on the subscription
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.
CloudScope auto-detects your subscription from az login. Just add the server:
{
"mcpServers": {
"cloudscope": {
"command": "npx",
"args": ["-y", "cloudscope-mcp"]
}
}
}To target a specific subscription, add an env block:
{
"mcpServers": {
"cloudscope": {
"command": "npx",
"args": ["-y", "cloudscope-mcp"],
"env": {
"AZURE_SUBSCRIPTION_ID": "your-subscription-id"
}
}
}
}Variable | Description |
| Azure AD tenant ID |
| App registration client ID |
| App registration client secret |
Set these alongside AZURE_SUBSCRIPTION_ID in the env block above.
GCP requires a BigQuery billing export table. Find your table name in GCP Console > Billing > Billing export > BigQuery export.
{
"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.
Variable | Description | Required |
| GCP project ID | Yes |
| Fully-qualified BigQuery table ( | Yes |
| Override project ID if different from | No |
| Billing account ID for budget monitoring | No |
| Path to service account JSON key file | No |
{
"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.
"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"
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.
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.
git clone https://github.com/alexpota/cloudscope-mcp.git
cd cloudscope-mcp
npm install
npm run build
npm test
npx @modelcontextprotocol/inspector node dist/index.jsMost 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
Tool | Description | Key Parameters |
| Spending breakdown by service, group, or region |
|
| Costs grouped by a tag/label key |
|
| Side-by-side cost comparison of two date ranges |
|
| Most expensive individual resources |
|
| Combined costs across Azure subscriptions |
|
| Combined costs across GCP projects |
|
Monitoring
Tool | Description | Key Parameters |
| Find spending spikes vs previous period |
|
| Budget status, current spend, projected overage | (none) |
| Predict spending based on current trends |
|
Optimization
Tool | Description | Key Parameters |
| Cost optimization suggestions (Azure Advisor / GCP Recommender) |
|
| Provisioned but unused resources with cost estimates | (none) |
| Resources with no tags/labels (cost attribution gaps) | (none) |
Utility
Tool | Description | Key Parameters |
| Today's date and current/previous month bounds | (none) |
| Azure subscriptions with active indicator | (none) |
| GCP projects with active indicator | (none) |
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.
Prompt | Description | Arguments |
| Complete monthly review: spending, last-month comparison, anomalies, top resources, budgets, forecast, savings opportunities |
|
| Find wasted spend: top resources, optimization recommendations, at-risk budgets, total potential savings |
|
| Root-cause analysis for a cost increase: which services, which resources, trend vs one-time, recommended actions |
|
| Brief non-technical cost summary for leadership: spend, trend, budget status, top drivers, forecast, key recommendation |
|
| Cost allocation by tag/label key for chargeback: spending per value, untagged resources, tagged vs untagged split, month-over-month |
|
Check budget status: current spend vs limit, percentage used, forecast, and overage risk. For GCP, requires GCP_BILLING_ACCOUNT_ID to be set.
Inputs: provider.
Compare costs between two date ranges, showing per-service absolute and percentage changes.
Inputs: period_a_start (required), period_a_end (required), period_b_start (required), period_b_end (required), +2 more.
Compares daily spending over the last N days against the prior N days to find cost spikes. Returns a list of services where spending increased above the threshold percentage, sorted by increase amount. Each entry includes service name, previous cost, current cost, percentage change, and absolute change in USD. Returns an empty list if no anomalies found. Use this when the user asks about unexpected cost increases, billing surprises, or wants to know if anything changed recently.
Inputs: provider, days, threshold.
Finds cloud resources that are provisioned but not actively used — unattached disks, orphaned network interfaces, unused IPs, idle VMs, and empty compute plans. Returns each resource with its name, type, resource group/project, reason it is idle, and estimated monthly cost in USD. Returns an empty list if no idle resources are found. Use this when the user asks about waste, idle or unused resources, cleanup opportunities, or wants to find resources to delete to reduce costs.
Inputs: provider.
Finds resources that have no tags or labels applied. Returns each resource with its name, type, resource group/project, and location. Untagged resources cannot be attributed to teams or projects, making cost allocation and chargeback impossible. Returns an empty list if all resources are tagged. Use this when the user asks about tagging compliance, governance, cost attribution gaps, or wants to identify resources that need tags or labels.
Inputs: provider.
Breaks down costs by a specific tag or label key such as team, environment, or project. Returns a sorted table with each tag value, cost in USD, and percentage of total. Includes a total row and daily average. Returns an error if the date range is invalid or no tagged costs exist. Use this when the user asks about costs per team, per environment, cost allocation, chargeback, or wants to understand spending by any custom tag or label.
Inputs: tag_key (required), provider, start_date, end_date.
Projects future cloud spending for the next N days using a linear trend based on the last 30 days of actual costs. Returns the forecast period dates, projected total cost in USD, average daily projected cost, and the confidence basis (number of historical days used). Use this when the user asks "how much will I spend this month", wants to predict upcoming bills, or needs to plan budgets. Returns an error if insufficient historical data exists.
Inputs: provider, days.
Returns a cost breakdown for a date range grouped by service, resource group, tag, or region. Defaults to current month if dates are omitted. Output includes a sorted table with each group name, cost in USD, and percentage of total. Includes a total row, daily average, and collapses groups beyond the top 10 into an "Other" row. Returns an error if the date range is invalid. Use this when the user asks "how much am I spending", "what costs the most", "show me my cloud bill", or wants a spending overview.
Inputs: provider, start_date, end_date, group_by.
Returns a combined cost breakdown across multiple GCP projects sorted by total spend. Each project shows its name, total cost in USD, and percentage of the combined total. Use this when the user asks about costs across all GCP projects, wants to compare project spending, or needs an organization-wide cost overview.
Inputs: provider (required), project_ids, start_date, end_date.
Returns a combined cost breakdown across multiple Azure subscriptions sorted by total spend. Each subscription shows its name, total cost in USD, and percentage of the combined total. Handles partial failures gracefully — if some subscriptions are inaccessible, returns results for the rest with a warning. Use this when the user asks about costs across all subscriptions, wants to compare subscription spending, or needs an organization-wide cost overview.
Inputs: provider (required), subscription_ids, start_date, end_date.
Returns today's date and the start/end of current and previous months in YYYY-MM-DD format
Inputs: no named parameters.
Returns all GCP projects the current credential can access, with name, ID, and state. Shows which project is currently active. Use this when the user has multiple GCP projects and wants to see which ones are available, or before calling get_cross_project_costs.
Inputs: provider (required).
Fetches cost-saving recommendations filtered by category. Returns a list of recommendations each containing: title, category, impact level (high/medium/low), estimated annual savings in USD, affected resource ID, and a short description of the suggested action. Returns an empty list if no recommendations exist for the selected category. Use this when the user wants to reduce costs, find waste, or optimize resource usage.
Inputs: provider, category.
Returns all Azure subscriptions the current credential can access, with name, ID, and state. Shows which subscription is currently active. Use this when the user has multiple subscriptions and wants to see which ones are available, or to confirm which subscription is being queried.
Inputs: provider (required).
Find the N most expensive individual resources over a time period. On GCP, requires the detailed billing export for resource-level data.
Inputs: provider, days, limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 15 tools
Most tools are clearly distinct by their focus (cost summary, tag breakdown, cross-project, anomalies, etc.). A minor potential confusion exists between get_cost_summary and get_cost_by_tag, but descriptions clarify the grouping dimension.
The majority of tools follow a verb_noun pattern (check_, compare_, detect_, find_, get_, list_). The exception is 'top_spending_resources' which uses a less standard verb form, but overall the pattern is consistent.
15 tools is well-scoped for a cloud cost management server, covering summary, breakdowns, forecasts, anomalies, optimization, and utilities without being overwhelming.
Core workflows are covered: cost review, forecast, anomalies, recommendations, and resource waste detection. Missing are write operations like budget creation or tagging, but the server appears read-only and covers its intended domain well.
Hosted MCP server for AWS cloud spend: service breakdowns, anomalies, savings and forecasts.
FinOps harness MCP: allocated cloud, data and LLM bills. Build on it or switch. Cloud read-only.
Hosted MCP server for LLM cost estimation, model comparison, and budget-aware routing.
Cloudflare Workers MCP server: ai-cost-optimizer
