Working with agents
Usage units
How MCP work is metered and how to keep agents efficient.
MCP work is measured in units. Small reads cost little; generating a whole project costs more. Your balance resets every Monday at 00:00 UTC.
Weekly allowance
| Plan | MCP units per week |
|---|---|
| Free | 150 |
| Pro | 1,500,000 |
| Max | Unlimited for a limited time — still metered, with fair-use and rate limits |
What each action costs
| Action | Units |
|---|---|
| A targeted read (list screens, read your selection, read tokens) | 1 |
| A context pack for specific layers | 2–5 |
| An image upload | 2 |
| A canvas change set (an edit) | 3–10 |
| A visual preview of a screen | 5 |
| Generating a full design-system package or project, or a repository sync | 50–200 |
Note
Where to see your usage
Open Workspace settings → Plan & billing and look for Your MCP usage (this week). Every client you connect — Claude, Cursor, VS Code or any other — draws from this same personal balance.
Keep agents efficient
Ask for edits in batches — one change set holds up to 50 commands and costs far less than 50 separate calls.
Ask for previews at checkpoints, not after every small change.
Reuse components for repeating UI instead of building each copy separately.
Generate a whole project or package only when you need it; for one component, ask for that component.
Plans and prices are on Plans & usage.