Pregunta a tu IA sobre tu factura de la nube.
Related MCP server: Azure FinOps Elite
CloudScope proporciona a los asistentes de IA acceso de solo lectura a tus datos de costes de Azure. Pregunta sobre el gasto, encuentra anomalías, obtén recomendaciones de optimización y prevé la factura del próximo mes, todo mediante lenguaje natural.
Proveedor | Estado |
Azure | ✅ Compatible |
GCP | Próximamente |
AWS | Usa el servidor oficial de AWS |
Azure CLI instalado e iniciada la sesión (az login)
Tu ID de suscripción (az account show --query id -o tsv)
Rol de Lector de Cost Management en la suscripción
Añádelo a la configuración de tu cliente MCP (claude_desktop_config.json, ajustes de Cursor, etc.):
{
"mcpServers": {
"cloudscope": {
"command": "npx",
"args": ["-y", "cloudscope-mcp"],
"env": {
"AZURE_SUBSCRIPTION_ID": "your-subscription-id"
}
}
}
}No se necesita una entidad de servicio para el desarrollo local. DefaultAzureCredential detecta automáticamente tu sesión de az login.
Variable | Descripción |
| ID de inquilino de Azure AD |
| ID de cliente de registro de la aplicación |
| Secreto de cliente de registro de la aplicación |
Configura esto junto con AZURE_SUBSCRIPTION_ID en el bloque env anterior.
Herramienta | Descripción | Parámetros clave |
| Desglose de gastos por servicio, grupo o región |
|
| Encuentra picos de gasto frente al periodo anterior |
|
| Sugerencias de optimización de costes de Azure Advisor |
|
| Predice el gasto basado en las tendencias actuales |
|
| Estado del presupuesto, gasto actual, exceso proyectado | (ninguno) |
| Comparación de costes lado a lado de dos rangos de fechas |
|
| Recursos individuales más costosos |
|
| Fecha de hoy y límites del mes actual/anterior | (ninguno) |
"¿Cuánto costó Azure el mes pasado?"
"Muestra el gasto por grupo de recursos de los últimos 7 días"
"¿Hay alguna anomalía de costes esta semana?"
"¿Cuánto costará Azure el próximo mes?"
"Muéstrame recomendaciones de optimización de costes"
"¿Qué servicios tuvieron el mayor aumento de gasto?"
CloudScope es de solo lectura. No puede crear, modificar ni eliminar ningún recurso de Azure. Todas las llamadas a la API utilizan permisos de Lector de Cost Management sin acceso de escritura.
¿Esto modifica mis recursos de Azure? No. Solo acceso de lectura.
¿Necesito una entidad de servicio? No. az login funciona para uso local.
¿Qué pasa con GCP? Próximamente.
¿La API de Azure Cost Management cuesta dinero? No. Es gratuita.
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.jsCheck 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
