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
- 1 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Runs a local Python server that reads Billing Usage API reports with an IAM token
- Gets exchange rates from the Bank of Russia and changes no budgets or settings
Install
- Works in
- Services
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.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs a local Python server that reads Billing Usage API reports with an IAM token
- Gets exchange rates from the Bank of Russia and changes no budgets or settings
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 mostMCP
- Transport
- stdio, http, sse
- Authentication
- key is optional
Environment variables
YC_IAM_TOKENsecret- A ready IAM token, not auto-refreshed
YC_SA_KEY_FILEsecret- 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
Limitations
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.
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.
How is the Yandex Cloud billing MCP different from the Yandex Cloud console?
The server wraps the Billing Usage API and answers only about spending: how much was spent on a service, folder or cloud over a period and how spending splits by resource labels. Amounts can be converted to any currency.
Can I see the account balance and how do I switch currency?
The balance is not shown: the server answers only about spending. Currency is chosen in call parameters or server settings, see the README. Access goes through a service account key. It works in Claude Code, Claude Desktop and Cursor.
Discussion
No questions or reviews yet.
Related
All Yandex Cloud toolsYandex Cloud's official MCP server set: documentation, search, app deployment, serverless functions, containers and a data catalog
Yandex Cloud MCP: VMs and Object Storage
yandex-cloud-mcp
MCP server for basic Yandex Cloud operations: virtual machines, Object Storage buckets and serverless functions from an agent chat
Yandex Cloud Object Storage MCP server
yandex-cloude-mcp
An unofficial single-file MCP server for Yandex Object Storage: bucket listing, contents and file downloads via the AWS SDK
Official Yandex demo templates: MCP gateways over cloud functions for YandexART, charts, PDF, arXiv, Kaggle and weather
Read-only Yandex Cloud MCP server
Yandex Cloud MCP Server
An unofficial read-only Yandex Cloud MCP server: VMs, networks, disks, and access at folder, cloud and org level
A 155-tool MCP server for Yandex Direct, Metrika, Wordstat and Webmaster, with self-setup OAuth and read-only and confirm modes
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.