Integration Plan
See how many integrations this project uses against its plan, and choose which ones stay active when it uses more than the plan includes. A choice is locked for one month.
Endpoints (2)
Plan, integration limit, the integrations that count (oldest first), the active set the owner chose (with its lock date), which integrations stay active and which would be switched off when enforcement starts, and the over-limit dates. Read-only.
No input parameters required.
Choose which integrations stay active when the project uses more than its plan includes. Send at most the plan limit, and only integrations the project uses (see get-usage), most important first. Free slots are filled with the oldest remaining integrations. The choice is locked for one month; a new choice before that returns 409 with the date. Ask the user before calling this.
| Field | Type | Required | Description |
|---|---|---|---|
services |
array | ✓ Yes | Integration ids in order of importance, e.g. ["checkout-flow","mollie","resend"]. |
MCP Tool Names
When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:
| Endpoint | MCP Tool Name |
|---|---|
| get-usage | integration-plan_get_usage |
| set-active | integration-plan_set_active |
Website