CloudScope MCP server
✓ VerifiedLets an AI client analyze Azure and GCP cloud spending, detect anomalies, forecast costs, and identify idle resources for optimization.
Also known as alexpota/cloudscope-mcp, cloudscope-mcp
- Stars
- 1
- Tools
- 15
- Downloads, 30 days
- —
- Latest version
- 0.3.3
- Last commit
- Aug 12, 2026
- License
- MIT
What is CloudScope MCP?
CloudScope lets an AI client analyze Azure and GCP cloud spending, detect anomalies, forecast costs, and identify idle resources for optimization. It exposes 15 tools, such as get_cost_summary, get_cost_by_tag, compare_periods.
Summary generated from the project's README
About CloudScope MCP server
CloudScope allows developers and cloud administrators to analyze spending across Azure and GCP through an AI client. It transforms complex billing data into decision-ready reports that highlight spending deltas, cost anomalies, and budget statuses. By connecting to your existing cloud environments, the server provides visibility into which services are driving costs and where money is being wasted on unused infrastructure.
For Azure users, the server auto-detects subscriptions via an active az login session and requires the Cost Management Reader role. GCP integration relies on a BigQuery billing export and requires the BigQuery Data Viewer and Job User roles. The server operates in a read-only capacity, meaning it can inspect your billing data and provide optimization suggestions through tools like find_idle_resources or list_recommendations without the ability to modify or delete any actual cloud resources.
Users can interact with the server using various commands to get cost summaries, compare different time periods, or forecast future spending. It is designed to work with clients like Claude Code, Cursor, and VS Code, providing a way to ask natural language questions about cloud expenses.
What you can do with it
- 1Generate monthly cost reviewsAsk the AI to perform a full workflow analysis including spending, anomalies, and idle resources to get a summary report.
Written from the project's README. Every use case is checked against a quote from it.
How to install CloudScope MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall CloudScope MCP in Claude Code
$ claude mcp add --env 'AZURE_CLIENT_SECRET=<YOUR_AZURE_CLIENT_SECRET>' --env 'GOOGLE_APPLICATION_CREDENTIALS=<YOUR_GOOGLE_APPLICATION_CREDENTIALS>' cloudscope-mcp -- npx -y cloudscope-mcpInstall CloudScope MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cloudscope-mcp": {
"command": "npx",
"args": [
"-y",
"cloudscope-mcp"
],
"env": {
"AZURE_CLIENT_SECRET": "<YOUR_AZURE_CLIENT_SECRET>",
"GOOGLE_APPLICATION_CREDENTIALS": "<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"
}
}
}
}Install CloudScope MCP in VS Code
.vscode/mcp.json
{
"servers": {
"cloudscope-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cloudscope-mcp"
],
"env": {
"AZURE_CLIENT_SECRET": "<YOUR_AZURE_CLIENT_SECRET>",
"GOOGLE_APPLICATION_CREDENTIALS": "<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"
}
}
}
}Install CloudScope MCP in VS Code CLI
$ code --add-mcp '{"name":"cloudscope-mcp","type":"stdio","command":"npx","args":["-y","cloudscope-mcp"],"env":{"AZURE_CLIENT_SECRET":"<YOUR_AZURE_CLIENT_SECRET>","GOOGLE_APPLICATION_CREDENTIALS":"<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"}}'Install CloudScope MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"cloudscope-mcp": {
"command": "npx",
"args": [
"-y",
"cloudscope-mcp"
],
"env": {
"AZURE_CLIENT_SECRET": "<YOUR_AZURE_CLIENT_SECRET>",
"GOOGLE_APPLICATION_CREDENTIALS": "<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"
}
}
}
}Install CloudScope MCP in Codex
$ codex mcp add cloudscope-mcp --env 'AZURE_CLIENT_SECRET=<YOUR_AZURE_CLIENT_SECRET>' --env 'GOOGLE_APPLICATION_CREDENTIALS=<YOUR_GOOGLE_APPLICATION_CREDENTIALS>' -- npx -y cloudscope-mcpInstall CloudScope MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.cloudscope-mcp] command = "npx" args = ["-y", "cloudscope-mcp"] [mcp_servers.cloudscope-mcp.env] AZURE_CLIENT_SECRET = "<YOUR_AZURE_CLIENT_SECRET>" GOOGLE_APPLICATION_CREDENTIALS = "<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"
Install CloudScope MCP in Gemini CLI
$ gemini mcp add -s user -e 'AZURE_CLIENT_SECRET=<YOUR_AZURE_CLIENT_SECRET>' -e 'GOOGLE_APPLICATION_CREDENTIALS=<YOUR_GOOGLE_APPLICATION_CREDENTIALS>' cloudscope-mcp npx -- -y cloudscope-mcpInstall CloudScope MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cloudscope-mcp": {
"command": "npx",
"args": [
"-y",
"cloudscope-mcp"
],
"env": {
"AZURE_CLIENT_SECRET": "<YOUR_AZURE_CLIENT_SECRET>",
"GOOGLE_APPLICATION_CREDENTIALS": "<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"
}
}
}
}CloudScope MCP tools 15
Detected from the READMEget_cost_summaryget_cost_by_tagcompare_periodstop_spending_resourcesget_cross_subscription_costsget_cross_project_costsdetect_anomaliescheck_budgetsget_cost_forecastlist_recommendationsfind_idle_resourcesfind_untagged_resources
| get_cost_summary | — | |
| get_cost_by_tag | — | |
| compare_periods | — | |
| top_spending_resources | — | |
| get_cross_subscription_costs | — | |
| get_cross_project_costs | — | |
| detect_anomalies | — | |
| check_budgets | — | |
| get_cost_forecast | — | |
| list_recommendations | — | |
| find_idle_resources | — | |
| find_untagged_resources | — |
Show all 15 toolsShow fewer tools
get_current_datelist_subscriptionslist_projects
| get_current_date | — | |
| list_subscriptions | — | |
| list_projects | — |
Configuration
AZURE_CLIENT_SECRETSecretService principal client secret. Optional; required only when using ClientSecretCredential.
GOOGLE_APPLICATION_CREDENTIALSSecretPath to GCP service account JSON key file. Optional; falls back to Application Default Credentials (gcloud auth).
AZURE_CLIENT_IDService principal client ID. Optional; required only when using ClientSecretCredential.
AZURE_SUBSCRIPTION_IDAzure subscription ID to query for cost data. Optional; auto-detected from az login session if not set.
AZURE_TENANT_IDAzure tenant ID for service principal authentication. Optional; falls back to DefaultAzureCredential (e.g. az login) if unset.
GCP_BILLING_ACCOUNT_IDGCP billing account ID (format: XXXXXX-XXXXXX-XXXXXX). Optional; needed only for budget monitoring.
GCP_BILLING_TABLEFully-qualified BigQuery billing export table (project.dataset.table_name). Required for GCP cost queries.
GCP_PROJECT_IDOverride GCP project ID if the billing dataset lives in a different project than GOOGLE_CLOUD_PROJECT.
GOOGLE_CLOUD_PROJECTGCP project ID. Recommended to set explicitly in the MCP client env block — may not be inherited from gcloud shell configuration.
| Name | Description | |
|---|---|---|
| AZURE_CLIENT_SECRET | Service principal client secret. Optional; required only when using ClientSecretCredential. | Secret |
| GOOGLE_APPLICATION_CREDENTIALS | Path to GCP service account JSON key file. Optional; falls back to Application Default Credentials (gcloud auth). | Secret |
| AZURE_CLIENT_ID | Service principal client ID. Optional; required only when using ClientSecretCredential. | |
| AZURE_SUBSCRIPTION_ID | Azure subscription ID to query for cost data. Optional; auto-detected from az login session if not set. | |
| AZURE_TENANT_ID | Azure tenant ID for service principal authentication. Optional; falls back to DefaultAzureCredential (e.g. az login) if unset. | |
| GCP_BILLING_ACCOUNT_ID | GCP billing account ID (format: XXXXXX-XXXXXX-XXXXXX). Optional; needed only for budget monitoring. | |
| GCP_BILLING_TABLE | Fully-qualified BigQuery billing export table (project.dataset.table_name). Required for GCP cost queries. | |
| GCP_PROJECT_ID | Override GCP project ID if the billing dataset lives in a different project than GOOGLE_CLOUD_PROJECT. | |
| GOOGLE_CLOUD_PROJECT | GCP project ID. Recommended to set explicitly in the MCP client env block — may not be inherited from gcloud shell configuration. |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablealexpota/cloudscope-mcp is public and reachablegithub.com/alexpota/cloudscope-mcp ↗Pass
- Package names this repository as its sourcecloudscope-mcp names alexpota/cloudscope-mcp as sourcenpmjs.com/package/cloudscope-mcp ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for cloudscope-mcpnpmjs.com/package/cloudscope-mcp/v/0.3.3#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-08-12github.com/alexpota/cloudscope-mcp ↗Pass
- OpenSSF ScorecardOpenSSF Scorecard 6.3 / 10; weakest: Code-Review 0, Maintained 0, CII-Best-Practices 0scorecard.dev/viewer/?uri=github.com/alexpota/cloudscope-mcp ↗Partial 9/15
- Package name not close to a popular packageNo popular package one edit away from cloudscope-mcpPass
- No critical advisory in the package or its dependencies294 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model15 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubCloudScope MCP
Ask your AI about your cloud bill.
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-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/month- Tear down
staging-slot-2if staging is idle → ~$280/month- 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 Code | Cursor | VS Code |
|---|---|---|
claude mcp add cloudscope -- npx -y cloudscope-mcp |
Install | Install |
Azure is auto-detected from your
az loginsession. GCP requires BigQuery billing export setup (see below).
Supported Providers
| Provider | Status |
|---|---|
| Azure | ✅ Supported |
| GCP | ✅ Supported |
| AWS | Use 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:
{
"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_TENANT_ID |
Azure AD tenant ID |
AZURE_CLIENT_ID |
App registration client ID |
AZURE_CLIENT_SECRET |
App 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.
{
"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 |
|---|---|---|
GOOGLE_CLOUD_PROJECT |
GCP project ID | Yes |
GCP_BILLING_TABLE |
Fully-qualified BigQuery table (project.dataset.table) |
Yes |
GCP_PROJECT_ID |
Override project ID if different from GOOGLE_CLOUD_PROJECT |
No |
GCP_BILLING_ACCOUNT_ID |
Billing account ID for budget monitoring | No |
GOOGLE_APPLICATION_CREDENTIALS |
Path to service account JSON key file | No |
Both Providers
{
"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
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.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
| Tool | Description | Key Parameters |
|---|---|---|
get_cost_summary |
Spending breakdown by service, group, or region | start_date, end_date, group_by |
get_cost_by_tag |
Costs grouped by a tag/label key | tag_key, start_date, end_date |
compare_periods |
Side-by-side cost comparison of two date ranges | period_a_start/end, period_b_start/end |
top_spending_resources |
Most expensive individual resources | days, limit |
get_cross_subscription_costs |
Combined costs across Azure subscriptions | subscription_ids, start_date, end_date |
get_cross_project_costs |
Combined costs across GCP projects | project_ids, start_date, end_date |
Monitoring
| Tool | Description | Key Parameters |
|---|---|---|
detect_anomalies |
Find spending spikes vs previous period | days, threshold |
check_budgets |
Budget status, current spend, projected overage | (none) |
get_cost_forecast |
Predict spending based on current trends | days |
Optimization
| Tool | Description | Key Parameters |
|---|---|---|
list_recommendations |
Cost optimization suggestions (Azure Advisor / GCP Recommender) | category |
find_idle_resources |
Provisioned but unused resources with cost estimates | (none) |
find_untagged_resources |
Resources with no tags/labels (cost attribution gaps) | (none) |
Utility
| Tool | Description | Key Parameters |
|---|---|---|
get_current_date |
Today's date and current/previous month bounds | (none) |
list_subscriptions |
Azure subscriptions with active indicator | (none) |
list_projects |
GCP 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.
| Prompt | Description | Arguments |
|---|---|---|
monthly-cost-review |
Complete monthly review: spending, last-month comparison, anomalies, top resources, budgets, forecast, savings opportunities | provider (optional) |
waste-audit |
Find wasted spend: top resources, optimization recommendations, at-risk budgets, total potential savings | provider (optional) |
cost-spike-investigation |
Root-cause analysis for a cost increase: which services, which resources, trend vs one-time, recommended actions | days (optional), provider (optional) |
executive-summary |
Brief non-technical cost summary for leadership: spend, trend, budget status, top drivers, forecast, key recommendation | provider (optional) |
chargeback-report |
Cost allocation by tag/label key for chargeback: spending per value, untagged resources, tagged vs untagged split, month-over-month | tag_key (required), provider (optional) |
License
CloudScope MCP questions
How do I add CloudScope MCP to Claude Code?
Run claude mcp add --env 'AZURE_CLIENT_SECRET=<YOUR_AZURE_CLIENT_SECRET>' --env 'GOOGLE_APPLICATION_CREDENTIALS=<YOUR_GOOGLE_APPLICATION_CREDENTIALS>' cloudscope-mcp -- npx -y cloudscope-mcp in your terminal. Add --scope user to make it available in every project.
How do I add CloudScope MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does CloudScope MCP provide?
It exposes 15 tools, including get_cost_summary, get_cost_by_tag, compare_periods, top_spending_resources, get_cross_subscription_costs.
Does this modify my cloud resources?
No, CloudScope is read-only and cannot create, modify, or delete any cloud resources.
Do I need a service principal for local use?
No, you can use az login for Azure or gcloud auth application-default login for GCP for local environments.
Does the Azure Cost Management API cost money?
No, the Azure Cost Management API is free to use.