All servers · Monitoring & logs · Cloud & networking

Plutus

com.plutus-cloud/plutus-cost-data · v2.0.0

Measured by MCP Station

Description written by the publisher, not verified

Query cloud, AI and SaaS spend across 25+ providers: costs, budgets, anomalies, unit economics.

Connect

claude mcp add --transport http plutus-cost-data https://console.plutus-cloud.com/api/mcp

{
  "mcpServers": {
    "plutus-cost-data": {
      "url": "https://console.plutus-cloud.com/api/mcp"
    }
  }
}

Tools as reported by the server

• list_cost_sources
  List the cost-source providers (AWS, GCP, Anthropic, etc.) enabled for this account. Each row's cost_basis says where that provider's money figures come from: "invoiced" = amounts the provider actually charged; "estimated_from_provider_rates" = an estimate built from the provider's own published rat
• query_costs
  Query time-bucketed spend for this account, optionally broken down by a dimension (service, region, linked_account, usage_type, operation, or identity) or by a custom cost-allocation tag (see list_cost_tags), and filtered by dimension values. `identity` is per-actor spend (e.g. an OpenAI or Anthropi
• list_savings_recommendations
  List active cost-reduction recommendations for this account. Most come from each provider's own already-computed engine (AWS Cost Explorer, Azure Advisor, GCP Recommender); rows with `source` = `plutus` are computed by Plutus itself (rightsizing, and `billing_pattern` below). `type` is one of: `term
• list_commitment_utilization
  List Reservation (RI) and Savings Plan utilization/coverage snapshots for this account — sourced from AWS Cost Explorer's own GetReservationUtilization/GetSavingsPlansUtilization APIs, one snapshot per commitment type per month. Shows how much of a purchased commitment is actually being used and its
• list_commitment_expirations
  List this account's Reserved Instance / Savings Plan / Azure Reservation commitments with their expiration dates, ordered soonest-first. `days_until_expiration` is computed server-side against the current UTC date (negative means already expired — rows are not pruned immediately on expiry, so check
• list_cost_tags
  List the virtual cost-allocation tag_keys defined for this account (e.g. "team", "product"), each with the cost_entries grain it's locked to and how many rules map dimension values to a tag_value. Use a tag_key with query_costs (breakdown_by: "tag") to see spend broken down by it. redistribute_bucke
• list_anomalies
  List detected cost anomalies for this account over a trailing lookback window — the real output of Plutus's nightly anomaly detector (severity, baseline vs. current spend, and what drove a tag-level spike), not something recomputed here from raw spend. Prefer this over eyeballing query_costs for "di
• explain_cost_change
  Explain a specific cost change: which timeline events line up with it, how strongly, and how much of the move Plutus could account for. Ask this about any point on a cost chart — it is not limited to anomalies the detector flagged (use list_anomalies for those; each already carries the same explanat
• list_anomaly_suppressions
  List this account's active anomaly suppressions — signatures (a provider+service pair, or a tag_key+tag_value) a human has marked as expected, so the detector stops surfacing them. Each has an `expires_at` (null = indefinite). Mirrors GET /api/accounts/:accountId/anomaly-suppressions. Creating/delet
• list_tag_recommendations
  List suggested cost-allocation tag rules this account doesn't have yet — high-spend values currently falling through to "Untagged" for an existing tag_key, or a provider-native tag worth promoting into a virtual tag_key of its own (see list_cost_tags). Each recommendation carries `estimated_monthly_
• list_data_health
  List sync health for every cost/event/usage connection this account has — last synced time, next scheduled sync, the outcome of its most recent run, and `is_overdue` (no successful sync within twice the connection's own effective sync interval). `recent_failure_count` counts failed runs among the la
• list_scheduled_reports
  List this account's scheduled cost digests — schedule (daily, weekdays, weekly, monthly, quarterly, first/last business day, a chosen weekday or day of month, or custom dates, all UTC), scope (whole account, one cost source, or one cost-allocation tag value), every destination alert channel with the
• list_report_layouts
  List what a scheduled report's layout can be made of: the presets (executive summary, spend by service, AI spend, budgets and anomalies), and the dashboard widgets that can be rendered into a report — each with the cost-scope types it supports — plus the dashboard widgets that cannot be (charts and
• list_dashboard_widget_catalog
  List the built-in ("preset") dashboard widgets available to place with create_dashboard/set_dashboard_widgets — small `kpi` stat tiles and larger `widget` data cards, each with the id (`catalog_id`) a {"kind": "preset", "catalog_id": "..."} widget spec references. There is no preset chart: to put a
• list_dashboards
  List this account's org-shared dashboards — visible to every account member. Does not include any member's PERSONAL dashboard: those live in one specific signed-in user's own browser session and have no id an account-level MCP key can address. Use a returned `id` with get_dashboard, set_dashboard_wi
• get_dashboard
  Fetch one org-shared dashboard's full layout — its placed widgets, custom metrics and custom charts, and their grid positions. A `widgets` entry references a preset catalog_id (see list_dashboard_widget_catalog); `customMetrics`/`customCharts` carry their own full config inline. Call this before set
• list_unit_metrics
  List this account's saved unit-economics metrics — each one a cost ÷ business-unit ratio such as "cost per 1k API requests" or "infra cost per order". `numerator_scope` says which slice of spend is on top (the whole account, one cost source, or one cost-allocation tag_value — see list_cost_tags), `d
• query_unit_costs
  Compute one of this account's saved unit-economics metrics (see list_unit_metrics) over a date range — the cost of a slice of spend divided by the business units it produced. Each row carries `cost` (the numerator, in the USD base like every other figure this server returns), `quantity` (the denomin
• query_usage
  Query time-bucketed usage telemetry this account's own backend has pushed or synced in (e.g. API request counts, tokens processed) — the raw data unit-economics metrics divide cost by (see list_unit_metrics/query_unit_costs), inspected directly rather than through a pre-defined ratio. `quantity` is
• list_usage_dimensions
  List the distinct values seen for a usage dimension ("metric" or "external_customer_id") over a date range — useful for discovering filter values before calling query_usage. Each entry pairs the raw `value` with a `label` (for external_customer_id, the customer's name from account_customers when kno
• query_events
  Query this account's business-event timeline (GitHub releases/PRs, PagerDuty incidents, Jira issues, GitLab, Salesforce onboarding/churn, Stripe subscription created/canceled, Vercel production deploys, Linear issue creation, Sentry newly reported errors) — the same events overlaid on the Cost/Event
• list_event_facets
  List the distinct values seen for a faceted event metadata field over a date range — currently just "repo" (every GitHub repo with at least one event), the same facet the Event Explorer's repo picker uses. Useful for discovering query_events' meta_repo filter values before calling it. Mirrors GET /a
• list_cost_tag_rules
  List the actual match rules for one of this account's cost-allocation tag_keys (see list_cost_tags) — which dimension values (or provider-native tag) map to which tag_value, and in what priority order. Rules are evaluated in ascending priority and the first match wins; spend matching no rule falls t
• list_cost_source_tag_keys
  List distinct provider-native tag/label keys actually present in this account's cost data (AWS Cost Allocation Tags, GCP/Hetzner labels, Azure tags) — useful for discovering what a "tags.<key>" cost-tag-rule match could reference before creating one. Only ever populated on grain='service' rows. Omit
• list_cost_source_tag_values
  List distinct values seen for one provider-native tag/label key (see list_cost_source_tag_keys) in this account's cost data.
• list_teams
  List this account's teams (user groups) with their members and the cost-tag tag_value each is reserved under — team-scoped budgets (create_budget with scope_type: "team") reference a team's id as scope_ref. Mirrors GET /api/accounts/:accountId/teams.
• list_tracker_links
  List the tickets linked to savings recommendations, waste findings and anomalies, with their tracker status, resolution and Plutus-side owner. status is open, done, closed_unresolved (closed as Won't Do/Duplicate/Declined), orphaned (ticket not found) or disconnected. Mirrors GET /api/accounts/:acco
• list_budgets
  List this account's spend budgets with their current-cycle status (spend so far, projected total, ok/warning/exceeded state, and forecast state). Mirrors GET /api/accounts/:accountId/budgets. `projected_cents` is the app's trend-based estimate of the period total (it follows weekday and weekend patt
• list_alert_channels
  List this account's alert notification channels (Slack/Teams/webhook/email) — need a channel's id to call create_alert_subscription. Never returns the channel's credentials/URL, only its id/type/name/enabled state.
• list_alert_subscriptions
  List which alert channels are subscribed to which trigger (a specific budget's spend_threshold, or account-wide event_overage/cost_anomaly/commitment_expiring/sync_failure/billing_pattern). Mirrors GET /api/accounts/:accountId/alert-subscriptions.
• list_alert_deliveries
  List recent alert delivery history for this account (did an alert actually fire, and did it send successfully) — the same data behind the Alerts page's delivery heatmap. Does not include the delivery error text. Mirrors GET /api/accounts/:accountId/alert-deliveries.
• list_alert_history
  The delivery history behind the Alerts page table: every alert, scheduled report, report attached to an alert, and test sent through an alert channel in the last 90 days, with the channel and recipients, the budget and the threshold that fired (`trigger_key`), the window a report covered, status and
• list_dimensions
  List the distinct values seen for a given dimension (service, region, linked_account, usage_type, or operation) for one provider — useful for discovering filter values before calling query_costs.
• get_cost_entries
  Fetch raw per-service cost entries for this account over a date range (unaggregated). Prefer query_costs for time-bucketed/aggregated spend — this is for inspecting individual rows. Each row's `cost` is in USD (see the response's top-level `currency` field), like every other figure this server retur

Tool changes

• 2026-10-24: list_cost_sources, query_costs, list_savings_recommendations, list_commitment_utilization, list_commitment_expirations, list_cost_tags, list_anomalies, explain_cost_change, list_anomaly_suppressions, list_tag_recommendations, list_data_health, list_scheduled_reports
• 2026-10-20: list_cost_sources, query_costs, list_savings_recommendations, list_commitment_utilization, list_commitment_expirations, list_cost_tags, list_anomalies, explain_cost_change, list_anomaly_suppressions, list_tag_recommendations, list_data_health, list_scheduled_reports
• 2026-10-19: list_cost_sources, query_costs, list_savings_recommendations, list_commitment_utilization, list_commitment_expirations, list_cost_tags, list_anomalies, explain_cost_change, list_anomaly_suppressions, list_tag_recommendations, list_data_health, list_scheduled_reports
• 2026-10-17: list_cost_sources, query_costs, list_savings_recommendations, list_commitment_utilization, list_commitment_expirations, list_cost_tags, list_anomalies, explain_cost_change, list_anomaly_suppressions, list_tag_recommendations, list_data_health, list_scheduled_reports

Website · JSON · Text for agents · Registry updated 2026-08-31