Plan & Usage (read-only) — MCP Tools
Read-only plan, usage limits, credit balance and trial status. This page documents the Plan & Usage (read-only) group of the Routebase MCP server, with the scope and the parameters of each tool.
A session that stages its tools advertises this group once the agent calls enable_toolset with the slug billing. Full-access keys, scoped keys and OAuth sessions see every tool they are allowed to call without that step.
get_credit_balance
Get the AI credit balance: what is left, what the plan includes, what came from rollover or top-ups, and when the allowance resets. Set includeHistory to also get where the credits went — per day and per feature. Use this for AI credits only; for plan limits across every category use get_usage_limits. Requires organization context. Read-only: plan, seat and top-up changes are not available through MCP by design — a human does those in the web app.
Required scope: billing:read
| Parameter | Type | Required | Description |
|---|---|---|---|
includeHistory |
boolean | No (default false) |
Also return consumption per day and per feature (default false) |
days |
integer | No (default 30) |
For includeHistory: how many days back to aggregate (default 30, max 365) |
featureId |
string | No | For includeHistory: limit the aggregation to one feature ID |
get_subscription
Get the organization's subscription: which plan is in force, its status, how many seats are paid for versus actually used, and whether a plan change is already scheduled for the period end. effectiveTier is the field feature limits are gated on — it accounts for a running trial and the grace period and can differ from the subscribed planTier. Use this for the plan in force; while a trial is running use get_trial. Requires organization context. Read-only: plan, seat and top-up changes are not available through MCP by design — a human does those in the web app.
Required scope: billing:read
No parameters.
get_trial
Get the organization's trial: which tier it grants, whether it is still running, when it expires and how many days are left. Unlike the other billing tools this one only needs organization membership, not billing:read. Use this for the trial; for the paid plan behind it use get_subscription. Requires organization context. Read-only: plan, seat and top-up changes are not available through MCP by design — a human does those in the web app.
No special scope — available to any authenticated key.
No parameters.
get_usage_limits
Get current usage against the plan limits, one entry per category (projects, specs, members, …) with the current count, the maximum and whether the category is unlimited. This is the tool that answers 'why can I not create another one'. Use this for usage against plan limits; for the AI credit balance use get_credit_balance. Requires organization context. Read-only: plan, seat and top-up changes are not available through MCP by design — a human does those in the web app.
Required scope: billing:read
No parameters.