get_cost_entries — Plutus MCP Tool Read-only
get_cost_entries
(get cost entries) 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 get_cost_entries from your client
- Claude Code Plutus get_cost_entries run in your project directory
- Claude Desktop Plutus get_cost_entries ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Plutus get_cost_entries ~/.cursor/mcp.json
- VS Code Plutus get_cost_entries .vscode/mcp.json
- Zed Plutus get_cost_entries ~/.config/zed/settings.json
- Windsurf Plutus get_cost_entries ~/.codeium/windsurf/mcp_config.json
- Cline Plutus get_cost_entries ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Plutus get_cost_entries ~/.gemini/settings.json
- Grok Plutus get_cost_entries .mcp.json (in your project root)
- ChatGPT Plutus get_cost_entries Settings → Connectors → Advanced → Developer mode
- Claude.ai Plutus get_cost_entries Settings → Connectors → Add custom connector
- LangChain Plutus get_cost_entries 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
- query_usage
- 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
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.