Organization roles and billing access
Who can view AI credits, manage billing, invite members, and what each organization role can do in MCP Stack.
MCP Stack uses organization roles to control what members can see and change. Billing permissions are separate from server and agent access — a Developer can build servers but cannot start Stripe checkout.
| Role | Typical use | Servers & agents | Members | Billing view | Billing manage |
|---|---|---|---|---|---|
| Owner | Account owner | Yes | Yes | Yes | Yes |
| Admin | Day-to-day administration | Yes | Yes | Yes | Yes |
| Developer | Build agents and MCP servers | Yes | No | Yes | No |
| Viewer | Read-only observability | View only | No | No | No |
Owners and Admins can invite members, manage API keys, start billing checkout, and change organization settings.
Developers can create and update MCP servers and agents, view AI credit balance and usage history, and use service-account keys — but cannot invite members or buy top-ups.
Viewers can browse permitted servers, agents, and logs. They cannot open billing pages or create resources.
Use these canonical pages for full dashboard, CLI, and API workflows:
Permissions inherit from your role on the organization. You do not need a separate permission for each ledger entry or API key.
If you expect access but see empty data, ask an Owner or Admin to confirm your role under Settings → Members.
Owners/Admins run the org and billing. Developers build. Viewers read. When in doubt, check Settings → Members for your role.