# Plutus

- Registry name: `com.plutus-cloud/plutus-cost-data` · version 2.0.0
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security, Cloud & networking
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): prompts, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.plutus-cloud%2Fplutus-cost-data
- Server page: https://mcpstation.net/s/com.plutus-cloud--plutus-cost-data.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://console.plutus-cloud.com/api/mcp`

## Tools (as reported by the server, not verified)

- `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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html