Connect Plutus and your agent gets 29 tools, among them get_cost_entries, get_dashboard, list_alert_channels. It answers at https://console.plutus-cloud.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Query cloud, AI and SaaS spend across 25+ providers: costs, budgets, anomalies, unit economics.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 Inputs: startDate, endDate |
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`/`customChar Inputs: dashboard_id |
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_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/:a Inputs: limit |
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). Mirrors GET /api/accounts/:accountId/alert-subscriptions. |
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 fro Inputs: days |
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 / |
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. A budget carries its own `currency` (budgets are |
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 m |
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 cre Inputs: cost_source_id |
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. Inputs: tag_name, cost_source_id |
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_rate |
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 prior Inputs: tag_key |
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_b |
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": "..."} |
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 addre |
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 inter |
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. Inputs: cost_source_id, dimension, start_date, end_date |
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_event Inputs: attr, source_id, start_date, end_date |
list_savings_recommendations | List active cost-reduction recommendations for this account — sourced from each provider's own already-computed engine (AWS Cost Explorer, Azure Advisor, GCP Recommender), not something Plutus computes itself. `type` is one of: `terminate` |
list_scheduled_reports | List this account's scheduled cost digests — cadence, scope (whole account, one cost source, or one cost-allocation tag value), destination alert channel, and when the next one is due. `next_period_label` names the concrete date range the n |
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 |
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/:accoun |
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 |
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_cust Inputs: dimension, start_date, end_date |
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 value Inputs: start_date, end_date, cost_source_ids, group_by, breakdown_by, tag_key |
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 r Inputs: start_date, end_date, source_id, event_type, meta_repo, q |
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 ever Inputs: unit_metric_id, start_date, end_date, group_by |
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 dire Inputs: start_date, end_date, group_by, breakdown_by, filter_metric, filter_external_customer_id |
Every block below points at https://console.plutus-cloud.com/api/mcp. Pick your client and copy.
claude mcp add --transport http plutus https://console.plutus-cloud.com/api/mcp
{
"mcpServers": {
"plutus": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://console.plutus-cloud.com/api/mcp"]
}
}
}{
"mcpServers": {
"plutus": {
"url": "https://console.plutus-cloud.com/api/mcp"
}
}
}{
"servers": {
"plutus": {
"type": "http",
"url": "https://console.plutus-cloud.com/api/mcp"
}
}
}{
"context_servers": {
"plutus": {
"url": "https://console.plutus-cloud.com/api/mcp"
}
}
}{
"mcpServers": {
"plutus": {
"serverUrl": "https://console.plutus-cloud.com/api/mcp"
}
}
}{
"mcpServers": {
"plutus": {
"url": "https://console.plutus-cloud.com/api/mcp"
}
}
}name: Plutus
version: 0.0.1
schema: v1
mcpServers:
- name: Plutus
type: streamable-http
url: https://console.plutus-cloud.com/api/mcp{
"mcpServers": {
"plutus": {
"httpUrl": "https://console.plutus-cloud.com/api/mcp"
}
}
}{
"mcpServers": {
"plutus": {
"type": "http",
"url": "https://console.plutus-cloud.com/api/mcp"
}
}
}{
"mcpServers": {
"plutus": {
"url": "https://console.plutus-cloud.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fconsole.plutus-cloud.com%2Fapi%2Fmcp&type=streamable_http&id=plutus&name=Plutus
It answered our last check on 18 October 2026 in 177 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by plutus-cloud.com and served from console.plutus-cloud.com, the vendor's own domain: https://console.plutus-cloud.com/api/mcp.
29, as returned by the server's own tools/list on 31 August 2026: get_cost_entries, get_dashboard, list_alert_channels, list_alert_deliveries, list_alert_subscriptions, list_anomalies, list_anomaly_suppressions, list_budgets, and 21 more.
It answered our last check on 18 October 2026 in 177 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://console.plutus-cloud.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.plutus-cloud. Endpoint host: console.plutus-cloud.com. ARD identifier: urn:air:com.plutus-cloud:mcp:plutus-cost-data.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.