{"data":{"name":"com.plutus-cloud/plutus-cost-data","title":"Plutus","description":"Query cloud, AI and SaaS spend across 25+ providers: costs, budgets, anomalies, unit economics.","version":"2.0.0","websiteUrl":"https://plutus-cloud.com/mcp","repositoryUrl":null,"remotes":[{"url":"https://console.plutus-cloud.com/api/mcp","type":"streamable-http","headers":[{"name":"Authorization","isSecret":true,"description":"Optional. Clients that support OAuth should omit this and use the authorization-server metadata advertised at /.well-known/oauth-protected-resource/api/mcp instead. Clients without OAuth may send `Bearer <key>` using an MCP API key minted in the Plutus console at https://console.plutus-cloud.com/mcp-keys"}]}],"packages":[],"status":"active","isLatest":true,"publishedAt":"2026-08-31T14:43:23.049Z","updatedAt":"2026-08-31T14:43:23.049Z","source":"official-registry","verification":"official","confidence":100,"stars":null,"sources":[{"stars":null,"title":"Plutus","source":"official-registry","sourceId":"com.plutus-cloud/plutus-cost-data","updatedAt":"2026-08-31T14:43:23.049Z","confidence":100,"websiteUrl":"https://plutus-cloud.com/mcp","description":"Query cloud, AI and SaaS spend across 25+ providers: costs, budgets, anomalies, unit economics.","verification":"official","repositoryUrl":null}],"toolIndex":{"tools":[{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"explain_cost_change","title":null,"description":"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).\n\nRENDER `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.\n\nThree 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.\n\nBody: `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.\n\nIn apps that show MCP Apps (Claude on the web, desktop and mobile), this result is also drawn as a card under the tool call showing the move and its candidates. Still give `explanation.sentences` as written, but do not rebuild the candidates as a table or draw another chart of them.","inputSchema":{"type":"object","properties":{"cost_source_id":{"description":"Narrow to one cost source, e.g. \"aws\"","type":"string"},"dimension":{"type":"string","enum":["service","region","linked_account","usage_type","resource_id"],"description":"Which dimension names the slice"},"value":{"type":"string","description":"The dimension value that moved, e.g. \"AmazonEC2\""},"day":{"description":"YYYY-MM-DD — the day to explain","type":"string"},"range":{"description":"Half-open YYYY-MM-DD range; narrowed to its biggest-moving day","type":"object","properties":{"start":{"type":"string"},"end":{"type":"string"}},"required":["start","end"]}},"required":["dimension","value"],"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"Explain Cost Change","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"3be70a0d525b258ff2fde15cc952f1f2f32c0d550c9de6f6e59eaf9f4a0fa441","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"get_cost_entries","title":null,"description":"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.","inputSchema":{"type":"object","properties":{"startDate":{"type":"string"},"endDate":{"type":"string"}},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"Get Cost Entries","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"24ff365849fa3730b060513a20d9428e1f297f280ed3597a42f1139073f5a0dd","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"get_dashboard","title":null,"description":"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.","inputSchema":{"type":"object","properties":{"dashboard_id":{"type":"string","description":"A shared dashboard id from list_dashboards"}},"required":["dashboard_id"],"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"Get Dashboard","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"a5a289dedf52b746d1abe6682b3c11fd4ee33303a59d8839f28a9eef2b400598","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"get_gcp_usage_settings","title":null,"description":"The BigQuery job usage settings saved on the GCP connection: bigquery_job_usage and scheduled_query_owners (\"on\"), and bigquery_job_regions. A setting that is not saved is absent (off, or regions discovered). Never returns credentials. Change them with set_gcp_usage_settings. Mirrors GET /api/accounts/:accountId/connections/gcp/usage-settings.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"Get GCP Usage Settings","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"e18ef9efd54f49238dfbd346b9a402e71afaf21296e0828cf3b147a25f7dce57","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"get_remediation_impact","title":null,"description":"Summarise the pull requests the Plutus GitHub App opened for this account from savings recommendations (automated fixes) in a window, default the last 90 days, at most 365: how many were opened, merged, closed without merging by the team, closed by Plutus itself (withdrawn, superseded or replaced, not a rejection) and are still open (each counted once, in its current state), how many were opened automatically versus requested by an admin, the median hours from opening to merge, a per-month series by the month each was opened, the change kinds, and the 10 most recent (number, GitHub URL, state, dates, estimated saving). Plutus never merges a pull request: a person on the account does. Every money figure is an estimate, in USD cents (the response's `currency`): the savings recommendation's estimated monthly saving as it stood when the pull request opened, a potential monthly saving once the change is applied. A merged change saves nothing until it is applied (for example by a Terraform apply). After a merge Plutus checks the resource inventory and gives each merged change a verification verdict: `confirmed` (the resource now shows the new configuration), `pending` (too early to tell), `not_applied` (merged, still the old configuration after 21 days) or `unverifiable` (the resource is gone, was never inventoried, or no evidence can be read). `pull_requests.verification` counts merged changes by verdict, `estimated_monthly_savings.merged_by_verification` splits the merged total by verdict (it adds up to `merged_cents`), and each recent merged pull request has `verification.status`. Confirmed means the change is in place, not that the saving was measured: the amount is still the estimate. Never call it realised, verified or guaranteed saving. Each recommendation is priced once per total; `merged_priced`/`open_priced` say how many pull requests the totals cover; a null total means none was priced, not zero. Jobs that never opened a pull request are not counted. `available` false means automated fixes are not offered to this account. Mirrors GET /api/accounts/:accountId/remediation/impact.","inputSchema":{"type":"object","properties":{"days":{"description":"Window length in days, ending now (default 90)","type":"integer","minimum":1,"maximum":365}},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"Get Automated Fix Impact","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"aba861c53eb7f8b935e4d1178bd465daf13212b4ca96bd6ec15141cd081a0385","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"get_sync_cadence","title":null,"description":"How often a connected source syncs, per data type (costs, events, usage): the effective rate, the default, and the choices with whether this plan may take each (faster rates need a paid plan; `fast_sync_enabled` says whether it does). Mirrors GET /api/accounts/:accountId/sync-cadence/:sourceId. Change a rate with set_sync_cadence.","inputSchema":{"type":"object","properties":{"source_id":{"type":"string","minLength":1,"maxLength":100,"description":"The connected source, for example \"gcp\" or \"github\""}},"required":["source_id"],"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"Get Sync Cadence","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"c2ac04484a1058b5211498273fca72c74c38abd8990efdd234a347813f8def2a","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"get_widget","title":null,"description":"Fetch one dashboard widget (a chart, tile or list the Plutus app shows) for a source, window and setting you choose, so the user sees the same picture the app draws. `widget_id` is a `catalog_id` from list_dashboard_widget_catalog, which says each widget's `shape`, the `report_scopes` it can speak for, its `window_mode`, the `config_keys` it accepts, and the schemas of its settings and its `data` (ask for them with `data_schema_for`; take setting names from `config_schemas`). A key the widget does not take is an error that lists the ones it does. Pick by what the user wants to see: spend over time `spend-trend` (config `dimension`, `top` 2-7, `chart` \"stacked-bar\" or \"line\"); a ranked split `spend-breakdown` (`dimension`, `top`); usage over time `usage-trend` (scope `usage_source`, config `metric`); events on the timeline `event-lanes` or `event-volume` (scope `event_source`); which events were followed by a cost move `event-impact`; budgets, anomalies, commitments and the rest from the catalog. To see two things together, call this once per widget.\n\n`scope_type` is \"account\" (default), \"cost_source\", \"event_source\", \"usage_source\" (then `scope_ref` is one source id or a comma-separated list) or \"tag\" (`scope_ref` is the tag value and `tag_key` is required); a widget refuses a scope it does not serve and says so in `unavailable`. `start_date` and `end_date` are YYYY-MM-DD, end exclusive, default the last 30 days (event-impact 61), at most 400 days. Money is in `currency` (default USD). An envelope with `unavailable` set carries a reason and no data: say what it says, not that there was no spend. `truncated` means a list was cut; say so. The widget names no cause for a change: do not add one.\n\nIn apps that show MCP Apps (Claude on the web, desktop and mobile), the widget is drawn under the tool call as the app's own chart, so the user already sees it. Say in a sentence or two what it shows and what stands out; do not restate its data as a table or draw another chart of it unless the user asks for one.","inputSchema":{"type":"object","properties":{"widget_id":{"type":"string","pattern":"^[a-z0-9-]{1,64}$","description":"A catalog_id from list_dashboard_widget_catalog, e.g. \"spend-trend\""},"start_date":{"description":"YYYY-MM-DD, inclusive","type":"string","pattern":"^\\d{4}-\\d{2}-\\d{2}$"},"end_date":{"description":"YYYY-MM-DD, exclusive","type":"string","pattern":"^\\d{4}-\\d{2}-\\d{2}$"},"scope_type":{"type":"string","enum":["account","cost_source","tag","event_source","usage_source"]},"scope_ref":{"description":"A source id or comma-separated list, or a tag value","type":"string","minLength":1,"maxLength":1000},"tag_key":{"description":"Required with scope_type \"tag\"","type":"string","minLength":1,"maxLength":200},"currency":{"description":"ISO 4217 display currency (default USD)","type":"string","pattern":"^[A-Za-z]{3}$"},"config":{"description":"The widget's own settings, e.g. { \"dimension\": \"region\", \"top\": 5 }","type":"object","propertyNames":{"type":"string"},"additionalProperties":{}}},"required":["widget_id"],"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"Get Widget","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"f95763277d39bbd62f7243add21775b2b7839420a75afe825b38d4344859bca4","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_alert_channels","title":null,"description":"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.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Alert Channels","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"e36afe61c7f7ff51a20c98aed32f3fda717c9009cc011ea0b123b831c142a9ba","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_alert_deliveries","title":null,"description":"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.","inputSchema":{"type":"object","properties":{"limit":{"description":"Max rows, most recent first (default: 100)","type":"integer","exclusiveMinimum":0,"maximum":500}},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Alert Deliveries","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"23307a4ab65d80b4cebf691aa75e6f9763e80058e0f6deb72ec1573d5283629c","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_alert_history","title":null,"description":"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.","inputSchema":{"type":"object","properties":{"limit":{"description":"Max rows, most recent first (default: 500)","type":"integer","exclusiveMinimum":0,"maximum":1000}},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Alert History","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"e9138b93a5885dce6ad3928c1dfefab62aa5771315fd5860d61f4e180acd91b4","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_alert_rules","title":null,"description":"List this account's metric alert rules (cost, usage and event rules): the slice and condition each judges, how many series are firing now, and the plan's rule limit. Mirrors GET /api/accounts/:accountId/alert-rules.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Alert Rules","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"fd0d2784b34d5ba92b361bc4ffdc5cc9dccee12ab5cd31395fb669396af49588","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_alert_subscriptions","title":null,"description":"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.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Alert Subscriptions","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"06f2d46b2a5db8b0484e0844a53fba8fb795080f26d28ec17cbdd583d4f87e67","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_anomalies","title":null,"description":"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.\n\nCapped 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.","inputSchema":{"type":"object","properties":{"days":{"description":"Trailing lookback window in days (default: 30)","type":"integer","minimum":1,"maximum":90}},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Anomalies","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"66699da891b7ee9ae5c4e72b218ab447f16556421b2b85b0dbc9e0f92d99e4a3","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_anomaly_suppressions","title":null,"description":"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.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Anomaly Suppressions","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"718e1fa32d245d8108556dc923c538a7bc4f87e4117095ec97fd7c25c57ea474","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_aws_member_accounts","title":null,"description":"The AWS member accounts Plutus discovered behind the connected organization: how many are readable, unreadable or excluded, and per account the access status, the fix when it is unreadable, and whether it is included. `enabled` false means multi-account inventory is off for this account. Change inclusion with set_aws_member_account_included. Mirrors GET /api/accounts/:accountId/aws/member-accounts.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List AWS Member Accounts","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"607df3b9c2705535c836a8c91e3e1f747e0e5f81fe30d7ebd9e800e7f07bb2db","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_budgets","title":null,"description":"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.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Budgets","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"29447094bc85f9b4a557a90481991a643152703ae6ceba09c0ddafdbfa8d3da4","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_commitment_expirations","title":null,"description":"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.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Commitment Expirations","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"7275238cdfe1c72ec7c3442cfa594bdbda2f3a8a2afcc178c8e8652b26e19a2c","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_commitment_utilization","title":null,"description":"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.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Commitment Utilization","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"c97ed23710939c5953864dfa528e349bac17b8ad316ac1bffc79c9c2ba41b075","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_cost_source_tag_keys","title":null,"description":"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.","inputSchema":{"type":"object","properties":{"cost_source_id":{"description":"Restrict to one provider, e.g. \"gcp\"","type":"string"}},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Cost Source Tag Keys","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"d326fcc4443a3a334f2908af6336ed0c58cb6c41c78b09599930bdd9ba1adb6d","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_cost_source_tag_values","title":null,"description":"List distinct values seen for one provider-native tag/label key (see list_cost_source_tag_keys) in this account's cost data.","inputSchema":{"type":"object","properties":{"tag_name":{"type":"string","description":"A tag key returned by list_cost_source_tag_keys, e.g. \"team\""},"cost_source_id":{"description":"Restrict to one provider, e.g. \"gcp\"","type":"string"}},"required":["tag_name"],"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Cost Source Tag Values","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"d9ecdc28132ac27ad9adad7765c393be83543b9a406a139eb13d771eacf767ad","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_cost_sources","title":null,"description":"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.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Cost Sources","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"3ad39646d76b095764c7e5e9b9898c3b0a1c1a2785d8429025d6a2a71f7f1659","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_cost_tag_rules","title":null,"description":"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.","inputSchema":{"type":"object","properties":{"tag_key":{"type":"string","description":"One of the tag_keys returned by list_cost_tags"}},"required":["tag_key"],"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Cost Tag Rules","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"fc6be769b47536da585ddd89149797ca1323795ee943ebecd40bce204ecc1096","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_cost_tags","title":null,"description":"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. redistribute_basis says what \"proportional\" means: attributed_spend (their own spend) or usage_metric (a usage metric, named by redistribute_usage_metric, whose value per tag_value weights the split; days with no usage fall back to spend).","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Cost Tags","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"6d0b0a05b84a98a3e0930fe13f68d396c17b950d298f9cd355df1f81524adb52","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_credits","title":null,"description":"List this account's credits (AWS Activate and promotional credits read from the provider, plus credits entered by hand for sources that expose no grant totals, such as GCP), with balances, burn rate and projected exhaustion, and per source whether credits could be read at all. Mirrors GET /api/accounts/:accountId/credits. Presentation and forecast only: budgets, spend limits and anomaly detection count gross spend and ignore credits. Each credit carries its own `currency` with `base_*` amounts in USD; check which one a figure is in before quoting it. `source` says whether a credit was read from the provider (\"provider\") or entered by hand (\"manual\"); only manual credits can be removed with delete_credit.","inputSchema":{"type":"object","properties":{},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Credits","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"6237118009c1e22b7d9b79ffc5d5162540bbd7eaea0fa0805e0d42946dbd0ab8","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"},{"serverName":"com.plutus-cloud/plutus-cost-data","endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","name":"list_dashboard_widget_catalog","title":null,"description":"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.\n\nThe 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`.\n\nEach widget also carries what its data is: `data_version`, `shape` (what it draws, such as kpi, line or ranked-list), `report_scopes` (the report scopes it can be shown for: account, cost_source, tag, event_source, usage_source), `window_mode` (`report`: it covers the window it is given, `default_days` long when none is; `current`: point-in-time state no window changes; `calendar`: a calendar period such as the month to date; `config`: the period is in its own configuration) and `names_people` (it lists people or API keys, so viewers cannot see it). `config_keys` lists the settings get_widget accepts for that widget in its `config` ([] when it takes none). Pass `data_schema_for` with up to 10 catalog ids to get the JSON Schema of each one's data under `data_schemas` and of its settings under `config_schemas`. Take setting names from `config_schemas`, not from the `config` inside a data schema: that is the normalised config the widget ran with, and its keys can differ.","inputSchema":{"type":"object","properties":{"data_schema_for":{"description":"Catalog ids whose data and settings JSON Schemas to include, at most 10.","maxItems":10,"type":"array","items":{"type":"string"}}},"$schema":"https://json-schema.org/draft/2020-12/schema"},"annotations":{"title":"List Dashboard Widget Catalog","readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false},"definitionHash":"e9e0da55fc3e098cd958c81b3045587f772c7c9ea1788dcfa3e5c892bc269c9b","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-16T18:46:03.291Z","metadataTrust":"untrusted"}],"endpoints":[{"endpointFingerprint":"20aa658bcc247df5cb3765d62b6cc030ce5525a6b096569aa72a465ef4bb1290","protocol":"streamable-http","status":"indexed","toolCount":44,"observedAt":"2026-11-16T18:46:03.291Z"}],"authentication":"unknown"},"connectionConfigurations":{"status":"ready","authentication":"not embedded","clients":{"Claude Desktop":{"mcpServers":{"com.plutus-cloud/plutus-cost-data":{"url":"https://console.plutus-cloud.com/api/mcp"}}},"Cursor":{"mcpServers":{"com.plutus-cloud/plutus-cost-data":{"url":"https://console.plutus-cloud.com/api/mcp"}}},"VS Code":{"servers":{"com.plutus-cloud/plutus-cost-data":{"type":"http","url":"https://console.plutus-cloud.com/api/mcp"}}}}},"resourceType":"mcp-server","callable":true,"runtime":{"callable":true,"protocols":["mcp"]},"interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://console.plutus-cloud.com/api/mcp"}],"profile":{"apiVersion":"1","schemaVersion":"1","id":"mcp-server:com.plutus-cloud%2Fplutus-cost-data","resourceType":"mcp-server","canonicalUrl":"https://www.agentsjunction.com/api/v1/servers/com.plutus-cloud%2Fplutus-cost-data","name":"com.plutus-cloud/plutus-cost-data","description":"Query cloud, AI and SaaS spend across 25+ providers: costs, budgets, anomalies, unit economics.","interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://console.plutus-cloud.com/api/mcp"}],"capabilities":[],"identity":{"source":"official-registry","websiteUrl":"https://plutus-cloud.com/mcp","repositoryUrl":null,"version":"2.0.0"},"verification":{"state":"official","confidence":100},"operations":{"resourceType":"mcp-server","name":"com.plutus-cloud/plutus-cost-data","status":"online","lastCheckedAt":"2026-11-20T07:17:48.411Z","lastSuccessfulCheck":"2026-11-20T07:17:48.411Z","latencyMs":349,"consecutiveFailures":0,"isStale":false,"checks":{"endpointReachable":true,"protocolValid":true,"agentCardValid":null,"mcpHandshakeValid":true},"lastSeen":null,"lastSuccessfulInteraction":null,"lastHealthCheck":"2026-11-20T07:17:48.411Z","source":{"type":"health-check","url":null},"observedAt":"2026-11-20T07:17:48.411Z"},"security":null,"timestamps":{"createdAt":"2026-08-31T14:43:23.049Z","updatedAt":"2026-08-31T14:43:23.049Z","observedAt":"2026-11-20T07:17:48.411Z"},"compatibility":{"serverVersion":"2.0.0","protocolVersions":[{"protocol":"mcp","version":null}]}}}}