# Plutus Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Plutus

Monitor cloud and SaaS spending across 25+ providers with cost tracking, budgets, and anomaly detection.

- Record: https://musedirectory.ai/connector/plutus
- Category: Finance & Bills
- Developer: Plutus Cloud (https://plutus-cloud.com/mcp)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 634ms, checked 2026-09-28T08:46:07Z
- Endpoint: https://console.plutus-cloud.com/api/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T01:51:15Z)
- Source: Found in the official MCP Registry (com.plutus-cloud/plutus-cost-data) https://registry.modelcontextprotocol.io/v0/servers?search=com.plutus-cloud%2Fplutus-cost-data

Connects to AWS, GCP, Azure, Anthropic, OpenAI and other cloud providers to track spend, set budgets, detect cost anomalies, view savings recommendations, and analyze unit economics. Helps teams understand where money goes and optimize cloud costs.

Example request: "Show me which services are driving the biggest cost increases this month and flag any unusual spending patterns."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Plutus to help me. It is a free service with an MCP server at https://console.plutus-cloud.com/api/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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
- 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. a
- 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` (an idle resource to shut down), `modify
- 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 actuall
- 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 
- 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
- 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
- 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 carri
- 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-suppress
- 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
- 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). `status` is only ever set on a suc
- 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 next digest will cover. Mirrors GET /api/
- 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 pre
- 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_dashboa
- 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. 
- 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
- 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), `qu
- 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 r
- 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 accoun
- 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 overla
- 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 callin
- 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 matc
- 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=
- 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_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 NOT converted to the USD base the cost 
- 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). 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_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 figu

Screening checks:
- MCP handshake: pass (Answered in 166ms)
- Domain against threat feeds (Cloudflare security DNS): pass (console.plutus-cloud.com, plutus-cloud.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (31 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 72 days ago)
- AI review of purpose and tool behavior: pass (No concerns)