Skip to main content
Kit gives you three ways to work with the platform programmatically: the REST API for building integrations against Kit data, the Kit Developer Docs MCP for giving your AI coding agent live access to these docs, and the Kit MCP for letting an AI client read and write to a creator’s Kit account on their behalf.

​
Choose your starting point

Kit API v4

Build apps and integrations against Kit’s REST API.

Kit Developer Docs MCP

Give your AI coding agent real-time access to these developer docs.

Kit MCP

Let an AI client read and write to a creator’s Kit account on their behalf.

​
When to use which

  • Building a Kit App Store app or a custom integration — use the Kit API v4, and connect the Kit Developer Docs MCP so your AI coding agent always has the latest endpoint reference, OAuth flows, and App Store guidelines.
  • Automating your own (or a creator’s) Kit account through an AI client — use the Kit MCP. Natural-language prompts like “draft a broadcast to my new subscribers from this week” become real account actions.
  • Your AI assistant keeps writing stale Kit code — connect the Kit Developer Docs MCP. It queries the live docs so your agent stops working from a cached or hallucinated API surface.

​
Authentication at a glance

  • Kit API v4 — API keys for personal automations, OAuth for apps acting on behalf of a creator. See Authentication.
  • Kit Developer Docs MCP — no auth required. The docs are public.
  • Kit MCP — OAuth on behalf of the creator. The AI client opens a Kit authorization flow on first connect, and tokens are scoped to that creator’s account. See the canonical help centre guide for client-side setup.
The Kit MCP’s complete setup and usage guide lives in the Kit help centre — see Kit MCP for the developer brief and the link through.