create_project
Register a new Subscriby project on behalf of the authenticated creator.
Scaffold a new project. Enforces the creator tier's project limit and handle uniqueness (across every project's current and former handles) before the row lands; a handle may be chosen on every tier, and one omitted is generated. A project has no platform of its own: install connectors on it afterwards with install_connector.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
It reaches beyond Subscriby: a connector, a provider or a member.
Arguments
name*stringProject name (min 5, max 255 characters).
descriptionstringoptionalOptional description. Max 1000 chars, HTML is filtered.
handlestringoptionalOptional URL-friendly handle, on every tier. Alpha-dash lowercase, 5-255 chars, unique across every project's current and former handles; omitted, a random one is assigned.
termsstringoptionalOptional URL to the terms page. Max 255 chars.
privacystringoptionalOptional URL to the privacy page. Max 255 chars.
activebooleanoptionalDefaults to true. Set false to create in draft state.
hide_brandingbooleanoptionalTake the "Powered by Subscriby" mark off the portal page, its social card and the bot. Defaults to false on every plan; true needs a Starter or Growth tier (TEAM_TIER_REQUIRED otherwise).
team_idstringoptionalOptional UUID of the owning team. Defaults to the token's scoped team.
What it returns
{ "data": { "id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "name": "Research Premium", "handle": "research-premium-abc123", "team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86", "active": true, "created_at": "2026-05-18T10:05:00Z" }}How it fails
TEAM_TIER_REQUIREDcreator has hit their plan's project limit, or hide_branding is true on a tier that keeps the mark. Error context carries required_capability.
VALIDATION_FAILEDname too short, handle malformed / taken (a handle another project used to answer on counts as taken), or team_id is a team the token's owner does not belong to.
How is this guide?
Last updated on