Skip to content
Grok

cloudscope for Grok

io.github.alexpota/cloudscope

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

client:Grok transport:stdio runtime:npm

Install cloudscope in Grok

.mcp.json (in your project root)

Held in this page only — never stored, logged, or sent anywhere but back to your screen.

{
  "mcpServers": {
    "cloudscope": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "cloudscope-mcp"
      ],
      "env": {
        "AZURE_SUBSCRIPTION_ID": "<AZURE_SUBSCRIPTION_ID>",
        "AZURE_TENANT_ID": "<AZURE_TENANT_ID>",
        "AZURE_CLIENT_ID": "<AZURE_CLIENT_ID>",
        "AZURE_CLIENT_SECRET": "<AZURE_CLIENT_SECRET>",
        "GOOGLE_CLOUD_PROJECT": "<GOOGLE_CLOUD_PROJECT>",
        "GCP_BILLING_TABLE": "<GCP_BILLING_TABLE>",
        "GCP_PROJECT_ID": "<GCP_PROJECT_ID>",
        "GCP_BILLING_ACCOUNT_ID": "<GCP_BILLING_ACCOUNT_ID>",
        "GOOGLE_APPLICATION_CREDENTIALS": "<GOOGLE_APPLICATION_CREDENTIALS>"
      }
    }
  }
}

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

cloudscope in other clients