Plutus

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Plutus": {
      "url": "https://console.plutus-cloud.com/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (34)

• list_cost_sources read-only

  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 rates, because it exposes no historical billing API; "estimated_from_static_rates" = an estimate built from a list-rate card Plutus maintains, which will not reflect rates the customer negotiated. Qualify any total that includes an estimated source rather than reporting it as billed spend.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• query_costs read-only

  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 Anthropic api_key_id) where a provider's cost/usage API can group by it; not every provider populates it. Mirrors the GET /api/analytics endpoint used by the Plutus dashboard charts. All amounts are in USD, converted from each provider's own billing currency at the rate in effect on the day of the charge; the response states this in its `currency` field. A row carries `cost_basis` only when its `cost` figure is an estimate rather than a real invoiced charge — e.g. Anthropic's identity-grain rows, priced from Anthropic's own published per-token rates because Anthropic's cost API has no per-key breakdown at all. Absent (null) `cost_basis` means the figure is invoiced. Always qualify an estimated figure as such when relaying it — do not present it with the same confidence as an invoiced one. Where a provider reports usage alongside cost, a row also carries `quantity` and its `unit` (e.g. tokens, GB-month), plus a derived `cost_per_unit` in that same USD base. Always read `cost_per_unit` together with `cost_per_unit_label`, which names the denominator it is quoted against: token costs are quoted per 1,000 tokens ("per 1k tokens", `cost_per_unit_scale: 1000`), NOT per single token. All four fields are null when the provider reports no usage, and also when the rows behind a group carry more than one unit — a total mixing tokens and GB-month is not a quantity, so none is given. The response also carries `coverage.complete_through`: cost data for the newest periods often has not landed yet (it arrives hours-to-a-day after the period it covers), so `rows` may end before `end_date` without that being a gap in spend — the newest period(s) simply aren't complete yet. `coverage.lagging_sources`, when non-empty, names a cost source that is behind or has stopped reporting; recent periods will under-count its spend. Unlike query_unit_costs, `rows` is NOT truncated to the horizon here — treat complete_through as a caveat on the newest bucket(s), not evidence anything is missing from the rows themselves.

  Parameters:

  • tag_key — string — Required when breakdown_by is "tag" — one of the tag_keys returned by list_cost_tags
  • end_date — string — ISO-8601 end of the date range (exclusive)
  • group_by — string — Time bucket size (default: day)
  • start_date — string — ISO-8601 start of the date range (inclusive)
  • cost_metric — string — Which cost figure to sum (default: "billed"). "amortized" spreads prepaid commitments (AWS Reserved Instances/Savings Plans, Azure reservations) across the term they cover instead of showing the full charge on the day it was billed. Only AWS, FOCUS and Azure sources ever differ from billed — every other provider writes amortized equal to billed, and that is the true figure for a SaaS subscription or LLM API, not a fallback. Amortized data only exists from 2026-08-04 onward and cannot be backfilled; rows before that date are billed-as-amortized regardless of which value is passed here. Not supported by get_cost_entries.
  • breakdown_by — string — Dimension to break spend down by, "tag" to break down by a virtual cost-allocation tag_key (see list_cost_tags) — requires tag_key — or "category" to fold sources into their category (cloud, ai, saas, …), one series per category; "category" cannot be combined with secondary_breakdown_by.
  • filter_model — array — Restrict to these model values
  • exclude_model — array — Leave out these model values
  • filter_region — array — Restrict to these region values
  • exclude_region — array — Leave out these region values
  • filter_cluster — array — Restrict to these cluster values
  • filter_service — array — Restrict to these service values
  • cost_source_ids — array — Restrict to these provider ids (defaults to all enabled providers)
  • exclude_cluster — array — Leave out these cluster values
  • exclude_service — array — Leave out these service values
  • filter_category — array — Restrict to sources in these categories (cloud, ai, kubernetes, data, observability, developer-tools, finance, communications, saas, custom)
  • filter_identity — array — Restrict to these identity values
  • filter_workload — array — Restrict to these workload values
  • exclude_category — array — Leave out sources in these categories
  • exclude_identity — array — Leave out these identity values
  • exclude_workload — array — Leave out these workload values
  • filter_namespace — array — Restrict to these namespace values
  • filter_operation — array — Restrict to these operation values
  • exclude_namespace — array — Leave out these namespace values
  • exclude_operation — array — Leave out these operation values
  • filter_usage_type — array — Restrict to these usage_type values
  • exclude_usage_type — array — Leave out these usage_type values
  • filter_resource_id — array — Restrict to these resource_id values
  • exclude_resource_id — array — Leave out these resource_id values
  • filter_linked_account — array — Restrict to these linked_account values
  • exclude_linked_account — array — Leave out these linked_account values
  • secondary_breakdown_by — string — A second dimension to break spend down by simultaneously with breakdown_by. The allowed pairs depend on the account's sources: a pair that no stored grain covers is rejected unless every source in scope writes the finer detail grain (currently AWS), in which case any pair of service/region/linked_account/usage_type/operation works. Not applicable when breakdown_by is "tag".

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_savings_recommendations read-only

  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 `misconfiguration` below). `type` is one of: `terminate` (an idle resource to shut down), `modify` (an overprovisioned one to downsize), `commitment_savings_plan` or `commitment_reservation` (a commitment worth *buying* — an AWS Savings Plan / Reserved Instance, Azure reservation or savings plan, or GCP committed use discount), or `misconfiguration`. Commitment rows have no `current_instance_type`/`recommended_instance_type` — they are a purchase, not an instance swap; their term, payment option, lookback window and hourly commitment are in `detail`. Only one term/payment/lookback variant per commitment is surfaced (AWS: 30-day lookback, 1-year, no upfront — Cost Explorer's own console default), so do not report these as the only commitment options available. Plutus also computes `misconfiguration` rows (`source` = `plutus`), the findings: a known costly setting found from billing lines (`detail.scope` = `account`) or an idle or orphaned resource found in the inventory (`detail.scope` = `resource`, with `provider_resource_id`). Their `detail` carries `reason`, `fix`, `reference_url`, `confidence`, `spend_usd`, `impact_basis` (`upper_bound` means the saving is a ceiling, at most that figure, not an estimate; say "up to". `resource_cost` means what the resource itself costs a month), `impact_unknown` (true means the saving cannot be estimated, so `estimated_monthly_savings_cents` of 0 is NOT a $0 saving), `where` (service, region, usage types) and `verify` (console links and manual steps to confirm and fix it). Triage them like any recommendation: dismiss, mark acted-on, or ticket. Mirrors GET /api/accounts/:accountId/savings-recommendations. Each recommendation carries the provider's own figure in its own `currency`; the total is in USD (stated in the response's `currency` field), since providers may bill in different ones. `total_estimated_monthly_savings_cents` is the firm total only: it leaves out `upper_bound` findings, which are reported separately as `upper_bound_findings` ({ count, max_monthly_cents }): say "N findings, up to $X/month", never add that into the total.

  Parameters:

  • type — string — Only these recommendation types, comma-separated (for example "misconfiguration" for the findings)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_commitment_utilization read-only

  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 net savings vs on-demand. Mirrors GET /api/accounts/:accountId/commitment-utilization.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_commitment_expirations read-only

  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 the sign). `latest_utilization_percentage` is the commitment TYPE's most recent monthly aggregate utilization (from list_commitment_utilization) applied to every active commitment of that type — there is no true per-commitment utilization API, so this is the closest real signal for "is this expiring commitment even being used," not an exact per-commitment figure. The same 30/14/7/1-day thresholds and 80% cutoff the automatic expiration alert uses are the right ones to flag here too, for consistency with what a subscribed channel already receives.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_cost_tags read-only

  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_bucket, when non-null, names a bucket (often "Untagged") whose spend is dissolved into the other tag_values in proportion to their own attributed spend in the same period — so that bucket will not appear in a query_costs breakdown for this tag_key, and the other values include a proportional share of it. It reappears only in periods where there was no other spend to redistribute against.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_anomalies read-only

  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 "did anything spike" — the detector already accounts for day-of-week baselines and an absolute-dollar noise floor that a naive comparison would miss or over-trigger on. Capped at 200 rows, most recent first; `days` (default 30, max 90) bounds the lookback. `kind` is "service" or "tag". `current_cents`/`baseline_cents`/`delta_cents` are the USD base. `suppressed: true` means a human has marked this exact signature (provider+service, or tag_key+tag_value) as expected — mention it but do not lead with it as a live problem. `driven_by` is null when driver attribution was not measured for this anomaly and `[]` when it WAS measured and found no dominant driver — those mean different things. Its entries differ by anomaly kind: a tag anomaly's entries are service-shaped (`service`/`cost_source_id`/`share_pct` — the services that fed the tag_value's spike); a service anomaly's entries, when the account has resource-grain detection enabled, are resource-shaped (`resource_id`/`resource_type`/`share_pct` — the specific resources, e.g. an EC2 instance or Lambda function, that drove that service's spike). Report a resource entry as a decomposition of the same service anomaly, never as a separate anomaly of its own. `correlated_events` is the service-anomaly counterpart: deploy/incident/release activity that was unusual (above the account's own baseline rate) in the 2-day window ending on the spike day, ranked by share of that excess. Same null-vs-`[]` distinction — null is "not measured" (a tag anomaly, or a row recorded before this shipped), `[]` is "measured and nothing was unusual". It is account-scoped and temporal: it does NOT claim the event caused this particular service's spend to rise, so report it as activity that lines up, never as a cause. `notified: false` means this anomaly was recorded but withheld from alerting because its tag_key was already at the per-run notify cap. Mirrors GET /api/accounts/:accountId/anomalies.

  Parameters:

  • days — integer — Trailing lookback window in days (default: 30)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• explain_cost_change read-only

  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 explanation). RENDER `explanation.sentences` AS WRITTEN. They are generated under a strict discipline and are the only phrasing this data supports: Plutus reports temporal and dimensional evidence, never causation. Each candidate carries a `claim` of "coincides" (temporal proximity only — the common case), "consistent_with" (proximity plus a confirmed link between that event source and this cost entity) or "accounts_for" (a known dollar amount that matches the move). Do not upgrade one to another, do not say an event "caused" or "led to" the change, and do not merge several candidates into a single narrative. Three separate numbers, never interchangeable: `change_evidence` is how sure we are a real change-point exists at all; `attribution_completeness` is what fraction of the move was localized to a specific part of the bill (a low value means "we do not know what this spend is yet", which is NOT the same as "nothing explains it"); `p_cause` is per candidate, and sums with `p_unknown` to 1. `tier: "unknown"` means we looked and found nothing that lines up — say that, rather than reaching for the top-ranked candidate anyway. Confidence is capped at 0.60 by design; there is no "high" tier today. Body: `dimension` + `value` name the slice (e.g. service=AmazonEC2), optional `cost_source_id` narrows it, and exactly one of `day` or `range` says when. A range is narrowed to the single biggest-moving day inside it, reported as `explained_day`. Mirrors POST /api/accounts/:accountId/cost-changes/explain.

  Parameters:

  • dimension (required) — string — Which dimension names the slice
  • value (required) — string — The dimension value that moved, e.g. "AmazonEC2"
  • day — string — YYYY-MM-DD — the day to explain
  • range — object — Half-open YYYY-MM-DD range; narrowed to its biggest-moving day
  • cost_source_id — string — Narrow to one cost source, e.g. "aws"

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_anomaly_suppressions read-only

  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/deleting a suppression is not available over MCP.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_tag_recommendations read-only

  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_spend_cents` (USD base) it would newly cover. Mirrors GET /api/accounts/:accountId/tag-recommendations. Accepting or dismissing a recommendation is a UI/REST-only action, not available over MCP.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_data_health read-only

  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 last 5, and a run that finished but reported a partial failure (`latest_run.partial_failure`, with the reason in `latest_run.error`) counts as failed. `status` flips to `error` when a sync job throws, but not for a partial failure or between a failure and the next success, so `is_overdue` and `recent_failure_count` — not `status` — are the real signals that a connection has gone stale or is failing. Check this before asserting that recent cost or usage data is complete, especially right before calling query_costs or query_usage for a very recent date range. Mirrors GET /api/accounts/:accountId/data-health.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_scheduled_reports read-only

  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 outcome of its last delivery, the layout of widgets it shows (null = the standard digest), and when the next one is due. `next_period_label` names the concrete date range the next digest will cover. Mirrors GET /api/accounts/:accountId/scheduled-reports. Creating and editing are the create_scheduled_report / update_scheduled_report tools.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_report_layouts read-only

  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 heatmaps have no report form) and why. Use the `catalog_id`s with create_scheduled_report / update_scheduled_report's `layout`. Mirrors GET /api/accounts/:accountId/report-layouts.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_dashboard_widget_catalog read-only

  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 trend chart on a dashboard, build one inline with a {"kind": "custom_chart", ...} spec instead of a catalog_id — see create_dashboard's description for that shape. The response also carries `grid_cols` (the canvas width every widget's x/w is measured against) and `size_bounds`, the min/max `w`/`h` each widget TYPE (`kpi`/`chart`/`widget` — not each individual catalog_id) accepts when a spec overrides its default size — use these before calling create_dashboard/set_dashboard_widgets with an explicit `w`/`h`. Each widget also carries what its data is: `data_version`, `report_scopes` (the report scopes it can be shown for: account, cost_source, tag), `window_mode` (`report`: it covers the window it is given; `fixed`: it states its own, such as the last 30 days) and `names_people` (it lists people or API keys, so viewers cannot see it). Pass `data_schema_for` with up to 10 catalog ids to get the JSON Schema of each one's data under `data_schemas`.

  Parameters:

  • data_schema_for — array — Catalog ids whose data JSON Schema to include, at most 10.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_dashboards read-only

  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_widgets or delete_dashboard.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_dashboard read-only

  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_dashboard_widgets if you want to keep some of what's already there rather than replacing the whole set — that tool always replaces everything.

  Parameters:

  • dashboard_id (required) — string — A shared dashboard id from list_dashboards

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_unit_metrics read-only

  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), `denominator_metric` names the usage metric counting the business units, and `denominator_scale` is the readability factor the ratio is quoted at (1, 1000 or 1000000). Pass an id to query_unit_costs to compute one over a date range.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• query_unit_costs read-only

  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 denominator, a raw count with no currency), and `unit_cost`. CRITICAL: `unit_cost` is null whenever it could not be computed, and null does NOT mean zero. It means one half of the fraction is missing for that period — either no usage was ingested (a telemetry gap) or no cost data has landed yet. Do not describe a null unit cost as a cost of zero, and do not average nulls in as zeroes; the `coverage` block reports how many rows are affected and why. Always read `unit_cost` together with `denominator_label` (e.g. "per 1k requests"), which names what it is quoted against — a per-1k figure reported as a per-request figure is wrong by three orders of magnitude. The series stops at `coverage.complete_through` rather than at the requested end_date whenever cost data for the newest periods has not arrived yet (it lands hours-to-a-day after the period it covers, while usage telemetry is pushed live). A short series is therefore normal and is NOT evidence that spend or usage stopped — say what it is complete through instead. `coverage.lagging_sources`, when non-empty, is the opposite case: a cost source that is behind or has stopped reporting, so recent periods are missing its spend and their unit costs read lower than the truth. If `numerator_status.available` is false, the cost source this metric measured has been removed from the account and `rows` is empty. That is a broken definition, not a period of zero spend — never report it as costs having fallen. Amounts are billed cost, never amortized, regardless of any cost_metric used elsewhere. A tag-scoped metric inherits that tag_key's allocation policy, so its numerator may include a redistributed share of shared spend (see list_cost_tags' redistribute_bucket) and will not match a raw dimension total. A metric whose denominator_mode is "per_customer" returns one row per (period, customer) and a `customers` block splitting them into matched, cost_without_usage (spend attributed to a customer who is not sending telemetry) and usage_without_cost (telemetry from a customer whose spend is not being allocated). Those two lists are the honest caveat on any per-customer figure and are worth mentioning when either is non-empty.

  Parameters:

  • unit_metric_id (required) — integer — id of a metric returned by list_unit_metrics
  • end_date — string — ISO-8601 end of the date range (exclusive)
  • group_by — string — Time bucket size (default: day)
  • start_date — string — ISO-8601 start of the date range (inclusive)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• query_usage read-only

  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 a raw count with no currency — never treat it as money. Optionally broken down by `external_customer_id` when the pushed rows carry one. Mirrors GET /api/usage.

  Parameters:

  • end_date — string — ISO-8601 end of the date range (exclusive)
  • group_by — string — Time bucket size (default: day). "hour" is only supported for ranges of 7 days or less.
  • start_date — string — ISO-8601 start of the date range (inclusive)
  • breakdown_by — string
  • filter_metric — array — Restrict to these metric names
  • exclude_metric — array — Leave out these metric names
  • filter_category — array — Restrict to usage from sources in these categories (see query_costs for the list; customer-defined push sources count as "custom")
  • exclude_category — array — Leave out usage from sources in these categories
  • filter_source_id — array — Restrict to usage pushed/synced under these usage-source ids
  • exclude_source_id — array — Leave out usage under these usage-source ids
  • filter_external_customer_id — array
  • exclude_external_customer_id — array — Leave out these customers

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_usage_dimensions read-only

  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 known, falling back to the id itself). Mirrors GET /api/usage/dimensions.

  Parameters:

  • dimension (required) — string
  • end_date — string
  • start_date — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• query_events read-only

  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 Explorer charts. Always scope with start_date/end_date: there is no pagination and results are capped at 5000 rows (oldest-first), so an unscoped query over a long history may be silently truncated. Carries no cost figure. Mirrors GET /api/events.

  Parameters:

  • q — string — Free-text, case-insensitive substring match against the event title
  • category — array — Restrict to event sources in these categories (cloud, ai, kubernetes, data, observability, developer-tools, finance, communications, saas, custom)
  • end_date — string — ISO-8601 end of the date range (inclusive)
  • meta_repo — array — Restrict to these GitHub repos (metadata.repo) — only narrows events that carry a repo; events with no repo (e.g. Salesforce onboarding/churn) are unaffected regardless of value
  • source_id — string — Restrict to one event source, e.g. "github", "pagerduty", "jira"
  • event_type — array — Restrict to these event types, e.g. "issue_created", "deploy"
  • start_date — string — ISO-8601 start of the date range (inclusive)
  • exclude_category — array — Leave out event sources in these categories

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_event_facets read-only

  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 /api/events/facets.

  Parameters:

  • attr (required) — string
  • end_date — string
  • source_id — string
  • start_date — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_cost_tag_rules read-only

  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 to "Untagged". Mirrors GET /api/accounts/:accountId/cost-tags/:tagKey/rules. IMPORTANT — a rule is NOT always a single assignment: when its `splits` field is non-null it is an array of {tag_value, weight} with weights summing to 1, and matched spend is divided across those tag_values by weight rather than going wholly to the rule's own tag_value. On a split rule, `tag_value` is only the rule's display label (e.g. "Shared EKS cluster") and no spend is attributed to it. Do not describe a rule with splits as assigning its spend to one team. Note also that some spend may be reallocated after these rules run — see list_cost_tags' redistribute_bucket.

  Parameters:

  • tag_key (required) — string — One of the tag_keys returned by list_cost_tags

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_cost_source_tag_keys read-only

  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 cost_source_id to search across every enabled provider.

  Parameters:

  • cost_source_id — string — Restrict to one provider, e.g. "gcp"

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_cost_source_tag_values read-only

  List distinct values seen for one provider-native tag/label key (see list_cost_source_tag_keys) in this account's cost data.

  Parameters:

  • tag_name (required) — string — A tag key returned by list_cost_source_tag_keys, e.g. "team"
  • cost_source_id — string — Restrict to one provider, e.g. "gcp"

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_teams read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_tracker_links read-only

  List the tickets linked to savings recommendations (findings included) 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/:accountId/tracker-links.

  Parameters:

  • status — string
  • item_type — string
  • owner_user_id — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_budgets read-only

  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 patterns when there is enough history), not a straight-line run rate. A budget carries its own `currency` (budgets are NOT converted to the USD base the cost tools return), and `amount_cents` is denominated in it; `spend_cents`/`projected_cents` are in `status_currency`, the budget's currency as of the rollup that wrote them. Never quote any of these figures as dollars without checking those two fields.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_alert_channels read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_alert_subscriptions read-only

  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/misconfiguration). Mirrors GET /api/accounts/:accountId/alert-subscriptions.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_alert_deliveries read-only

  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.

  Parameters:

  • limit — integer — Max rows, most recent first (default: 100)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_alert_history read-only

  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 a truncated error. An alert and the report attached to it share a `delivery_key`. Attached reports skipped for a cooldown, the hourly cap or no data appear too. Mirrors GET /api/accounts/:accountId/alert-history.

  Parameters:

  • limit — integer — Max rows, most recent first (default: 500)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_dimensions read-only

  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.

  Parameters:

  • cost_source_id (required) — string — Provider id, e.g. "aws" — must be enabled for this account
  • dimension (required) — string
  • end_date — string
  • start_date — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_cost_entries read-only

  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 returns. A row also carries `native_cost`/`native_currency` — what the provider actually billed, for reconciling against their invoice. Those are the one exception to the USD rule here: never sum or compare `native_cost` across rows, and never quote it without naming the row's `native_currency`. Unlike query_costs, there is no cost_metric parameter here — `cost` is always billed cost, never amortized.

  Parameters:

  • endDate — string
  • startDate — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.