io.github.mcp-dir/gcp_billing-mcp · v0.1.0 · finance-and-payments
GCP Billing is healthy: it completed an MCP handshake in 240 ms and exposes 9 tools.
Google Cloud Billing BigQuery export reporting through a user-connected service account.
Endpoint: https://api.mcp.ai/p_gcp_billing (streamable-http)
Repository · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 9 |
| Latency | 240 ms |
| Last checked (UTC) | 2026-10-16T09:50:35.575Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T09:50:35.575Z | Healthy | 240 | |
| 2026-10-15T05:15:46.896Z | Healthy | 1473 |
gcp_billing_list_accounts | List GCP Billing BigQuery export credential records linked to this install. |
gcp_billing_cost | Query normalized GCP Billing BigQuery export costs by day, service, project, and SKU. Returns compact totals only. |
gcp_billing_top_services | Query top GCP services by cost from the user's BigQuery billing export. Returns normalized service totals. |
show_version | Show the current MCP platform and adapter versions. |
report_bug | Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction. |
connect | Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs. |
toolkit_info | Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes. |
marketplace | The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (ev |
authenticate | MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes |