Yandex Cloud Billing MCP
yandex-cloud-mcp-billing
Yandex Cloud spend MCP: cost breakdowns by service, folder and resource label, with conversion to any currency
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Only reads consumption reports; it cannot change settings or budgets
- Needs a billing-only read role; no access to resources themselves is required
Install
Manual install
uv venv && source .venv/bin/activate && uv pip install -e . && YC_IAM_TOKEN="$(yc iam create-token)" yc-billing-mcpLocal install; by default it starts Streamable HTTP on localhost:8000/mcp.
This is third-party code. Review the repository files before installing.
What it does
The server wraps the Yandex Cloud Billing Usage API and answers only spend questions: how much was spent on a service, folder or cloud in a period, how cost splits across resource labels like project or team, and which specific resources drove the bill. There is a dedicated flow for labels: first a list of label keys with a cardinality estimate, then a breakdown by one key, then detail for specific values. Every response carries a block in a chosen currency, with rates from the Bank of Russia, switchable per session. It does not show balances, budgets or the price list, only actual consumption.
Who it is for. For engineers and founders who want to break down a Yandex Cloud bill by project and team without exporting spreadsheets.
Good fit when
- You need to know how much was spent on a specific service or folder this month
- You need chargeback by resource label across projects or teams
- You want to see spend in another currency, such as euros or dollars
Not a fit when
- You need account balance, budgets or the price list: the server does not expose them
- You lack the billing.accounts.getReport role on the target billing account
Example request
Show last month's spend by project in euros and tell me which project grew the mostLimitations
Requires the billing.accounts.getReport role on the billing account. Consumption data lags as is typical for the Billing Usage API. The ConsumptionCore API is limited to one request per minute per IP, so the server caches responses. An unscoped label or resource report is rejected by the API; an explicit filter or scope is required.
How to disable. Remove the yc-billing block from your MCP client config or stop the server process.
MCP
- Transport
- stdio, http, sse
- Authentication
- API key
| Environment variables | |
|---|---|
| YC_IAM_TOKEN secret | A ready IAM token, not auto-refreshed |
| YC_SA_KEY_FILE secret | Path to the service account JSON key |
| YC_BILLING_ACCOUNT_ID | Default billing account for all tools |
| YC_DISPLAY_CURRENCY | Default display currency, USD if unset |
Security check
- Only reads consumption reports; it cannot change settings or budgets
- Needs a billing-only read role; no access to resources themselves is required
README in short
The README describes the service catalogue, the spend_* tool family over the ConsumptionCore API, a label-discovery flow guarded against unscoped queries, and an automatic currency-conversion block. It separately covers six auth methods from a ready IAM token to Kubernetes Workload Identity Federation, the stdio, Streamable HTTP and SSE transports, and running in Docker.
FAQ
Can I see the account balance?
No, the server is deliberately limited to consumption reports and does not expose balance or budgets.
How do I switch the response currency?
Call set_display_currency once per session, and every following response adds amounts in that currency at the CBR rate.
Related
A set of investment research skills for Claude Code and Codex built on four investors' methodologies. It is a research tool, not investment advice
Stripe's official MCP server, plugins and skills: the agent searches the API and docs, reads and changes account data
Alpaca's official MCP server: orders for stocks, ETFs, crypto and options, position management and market data in plain language
inn-check-ru: counterparty risk traffic light
inn-check-ru
An open-source skill that checks a Russian company by tax ID across EGRUL, bailiffs, courts, bankruptcy and sanctions, and returns a dated risk verdict