A major creator-email platform with APIs, webhooks, plugins, an app ecosystem, and official MCP support for both developer knowledge and creator-account actions.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Read and write live creator-account data including subscribers, tags, segments, sequences, broadcasts, forms, custom fields, posts, purchases, stats and webhooks; supports drafting and scheduling, with guarded consequential actions
Read live creator-account data exposed by Kit API v4, including subscribers, sequences, broadcasts, tags, segments, custom fields, and account information.
Use Kit API v4 actions through MCP, including creating and updating subscribers, applying audience organization, and drafting, scheduling, or sending broadcasts.
Kit MCP uses OAuth on behalf of the creator. The creator signs in and grants access, and the resulting token is scoped to that creator's account.
Honor Kit's read-only, destructive, idempotent, and open-world tool annotations. Show the connected creator account, audience, content, and effect before confirming external sends or data deletion.
Operational Kit MCP is available on paid Creator and Creator Pro plans and is limited to 120 requests per minute per token. The separate Developer Docs MCP is read-only and has no creator-account access.
Agent access
Support: Official MCP server
Read scope: Read creator-account data exposed by Kit API v4, including subscribers, sequences, broadcasts, tags, segments, custom fields, and account information.
Write scope: Create and update subscribers, tag or untag them, organize audiences, and draft, schedule, or send broadcasts through the Kit API v4-backed tool surface.
Authentication: OAuth on behalf of the creator; the AI client opens Kit's authorization flow and receives a token scoped to that creator account.
Approval boundary: Read operations may run without prompts; supported clients apply write safeguards, and external or destructive actions such as sending broadcasts or deleting data always require explicit user confirmation.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Kit ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Official Kit documentation distinguishes the live-account MCP from the documentation MCP. OAuth scopes the connection to a creator account; 65+ tools are documented, a 120-requests-per-minute token limit applies, and…
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API capabilities.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party API-key and OAuth guidance.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Official API, plugins, app-store, and MCP entry point.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Product overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party event subscriptions.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
