query_usage — Plutus MCP Tool Read-only
query_usage
(query usage) is one of 31 tools on the
Plutus
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call query_usage from your client
- Claude Code Plutus query_usage run in your project directory
- Claude Desktop Plutus query_usage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Plutus query_usage ~/.cursor/mcp.json
- VS Code Plutus query_usage .vscode/mcp.json
- Zed Plutus query_usage ~/.config/zed/settings.json
- Windsurf Plutus query_usage ~/.codeium/windsurf/mcp_config.json
- Cline Plutus query_usage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Plutus query_usage ~/.gemini/settings.json
- Grok Plutus query_usage .mcp.json (in your project root)
- ChatGPT Plutus query_usage Settings → Connectors → Advanced → Developer mode
- Claude.ai Plutus query_usage Settings → Connectors → Add custom connector
- LangChain Plutus query_usage pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http plutus-cost-data https://console.plutus-cloud.com/api/mcpOther tools on this server
- list_cost_sources
- query_costs
- list_savings_recommendations
- list_commitment_utilization
- list_commitment_expirations
- list_cost_tags
- list_anomalies
- explain_cost_change
- list_anomaly_suppressions
- list_tag_recommendations
- list_data_health
- list_scheduled_reports
- list_dashboard_widget_catalog
- list_dashboards
- get_dashboard
- list_unit_metrics
- query_unit_costs
- list_usage_dimensions
- query_events
- list_event_facets
- list_cost_tag_rules
- list_cost_source_tag_keys
- list_cost_source_tag_values
- list_teams
- list_budgets
- list_alert_channels
- list_alert_subscriptions
- list_alert_deliveries
- list_dimensions
- get_cost_entries
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.