Kit
Kit is a platform that allows creators to automate tasks and developers to build apps for the Kit App Store.
Verdict
Common use cases
- Add webinar registrants to email sequences
- Tag subscribers based on chat interactions
- Create custom fields for lead scoring
- Delete outdated broadcasts before send
- Sync webhook events to project tracker
Integration
- Vendor
- Kit
- Category
- other
- Auth
- OAUTH2
- Tools
- 29
- Composio slug
kit
Tools
- Add Subscriber to Form
Tool to add a subscriber to a specific form by id. use after confirming form and subscriber ids.
- Create Custom Field
Tool to create a new custom field for subscriber data. use when you need to store extra attributes for subscribers.
- Create Tag
Tool to create a new tag in the account. use when you need a custom label to segment subscribers. use after confirming tag uniqueness to avoid duplicates. example: "create a tag called 'vip' for premium customers."
- Create Webhook
Tool to create a new webhook subscription. use when you need subscriber or purchase event notifications.
- Delete Broadcastdestructive
Tool to delete a specific broadcast. use when you need to permanently remove a broadcast by id (after confirming the id). example prompt: "delete broadcast with id 123"
- Delete Custom Fielddestructive
Tool to delete a specific custom field. use after confirming the custom field id is correct. deletes the field permanently.
- Delete Subscriberdestructive
Tool to delete (unsubscribe) a subscriber by id. use when you need to remove a subscriber from all sequences and forms after confirming the subscriber exists.
- Delete Tagdestructive
Tool to delete a tag by id. use when you need to remove obsolete or incorrect tags after confirming the tag exists.
- Delete Webhookdestructive
Tool to delete a webhook by id. use when you want to permanently remove a webhook after confirming its id.
- Get Account
Tool to retrieve current account information. use after validating api key to fetch account id, plan type, primary email, and timezone details.
- Get Account Colors
Tool to retrieve list of colors associated with the account. use after confirming authentication to fetch account-specific color palette.
- Get Broadcast
Tool to retrieve details of a specific broadcast by id. use when you have a valid broadcast id and need its metadata.
- Get Broadcast Stats
Tool to retrieve statistics for a specific broadcast by id. use after a broadcast has been sent to monitor performance.
- Get Creator Profile
Tool to retrieve the creator profile information for the account. use when you need creator metadata (bio, avatar, social links) before publishing or customizing content.
- Get Email Stats
Tool to retrieve email statistics for the account. use after confirming authentication to fetch metrics on emails (sent, opened, clicked) over the last 90 days.
- List Broadcasts
Tool to retrieve a paginated list of all broadcasts. use when you need to enumerate or review broadcast summaries with cursor-based pagination.
- List Custom Fields
Tool to retrieve a paginated list of custom fields. use after confirming you need to enumerate or inspect all custom fields with cursor-based pagination.
- List Forms
Tool to list all forms. use when you need to fetch forms with optional filters and pagination.
- List Segments
Tool to retrieve a paginated list of segments. use when you need to enumerate segments with cursor-based pagination for further processing or display.
- List Sequences
Tool to retrieve a paginated list of all sequences. use when you need to enumerate sequences with pagination for further processing or display.
- List Subscribers
Tool to retrieve a list of subscribers. use when you need to fetch subscriber records with optional filtering, sorting, and pagination.
- List Subscribers For Form
Tool to retrieve subscribers for a specific form by id. use when you need to page or filter subscribers of a form.
- List Tags
Tool to retrieve a list of all tags. use when you need a complete inventory of tags for the kit account.
- List Tag Subscribers
Tool to retrieve subscribers for a specific tag. use after confirming the tag id when you need to list subscribers associated with a tag.
- Tag Subscriber
Tool to associate a subscriber with a specific tag by id. use after confirming tag and subscriber ids when tagging a subscriber.
- Tag Subscriber by Email
Tool to associate a subscriber with a tag using an email address. use when you have a tag id and subscriber email ready. use after confirming both resources exist.
- Update Account Colors
Tool to update the list of colors for the account. use when customizing your kit account's color palette for broadcasts and templates.
- Update Custom Field
Tool to update a custom field's label. use after listing or retrieving custom fields and confirming the field id to rename.
- Update Tag
Tool to update a tag's name by id. use after retrieving tag id and confirming the new name.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find Kit in the MCP directory and click Connect. 3. You'll be redirected to Kit's OAuth consent screen — sign in with your Kit account credentials. 4. Kit will ask you to authorize Switchy to manage subscribers, tags, forms, broadcasts, custom fields, and webhooks; review the scopes and click Authorize. 5. You'll return to Switchy with a confirmation that Kit is connected. 6. Open any Space and type '@Kit list all tags' to test the connection — the MCP should return your account's tags. 7. To invoke a tool, @mention Kit followed by your request, like '@Kit add subscriber email@example.com to form 12345' (you'll need form IDs from your Kit dashboard). 8. Check the Space's activity log to confirm the action completed successfully.
What teammates see: by default, memories from Kit are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Tag New Leads
@Kit create a tag called 'Q1-2024-leads' and then add all subscribers from form 98765 to that tagOpen in a Space →
Audit Subscriber List
@Kit list all subscribers tagged 'vip' and show me their email addresses and custom field valuesOpen in a Space →
Clean Up Old Broadcasts
@Kit show me all draft broadcasts created before January 1 2024 and delete any that are no longer neededOpen in a Space →
Add Custom Field for Scoring
@Kit create a custom field called 'engagement_score' with type number so we can track subscriber activityOpen in a Space →
Set Up Event Webhook
@Kit create a webhook that sends subscriber.created events to https://our-app.com/kit-events so we can sync new signupsOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Kit show me all subscribers who joined in the last 7 days and what forms they signed up through
Based on the Kit account data, 47 subscribers joined in the past week. The breakdown by form: 'Homepage Newsletter' (23 subscribers), 'Lead Magnet Download' (18 subscribers), 'Webinar Registration' (6 subscribers). The most recent subscriber joined 2 hours ago via the Homepage Newsletter form. This illustrative example shows how Kit's subscriber and form data can be queried and cross-referenced to understand recent growth patterns.
This example demonstrates Kit's read capabilities for subscriber and form data. Requires OAuth scope for reading subscribers and forms. The actual response structure depends on your account's subscriber volume and form setup — accounts with thousands of subscribers may need date-range filtering to avoid rate limits.
@Kit create a new tag called 'Q1-2024-Webinar' and add all subscribers from the 'Webinar Registration' form to it
Tag 'Q1-2024-Webinar' created successfully (tag ID: 8472). Now adding subscribers from 'Webinar Registration' form (form ID: 1523) to this tag. Processing 6 subscribers... Complete. All 6 subscribers from the Webinar Registration form now have the Q1-2024-Webinar tag applied. You can use this tag to send targeted broadcasts or build automation sequences for this cohort. This illustrative example shows the two-step workflow of tag creation followed by bulk subscriber tagging.
This example showcases Kit's write capabilities for segmentation. The MCP creates the tag first, then applies it to matching subscribers. Side-effect: this permanently modifies subscriber records in your Kit account. Always confirm form IDs before bulk tagging operations to avoid misapplying tags to the wrong audience.
@Kit analyze my subscriber growth over the last 30 days and draft a summary email I can send to stakeholders about our email list performance
Subscriber growth analysis (last 30 days): Started at 1,842 subscribers, ended at 1,889 (+47 net growth, +2.6%). Top-performing form: 'Homepage Newsletter' drove 49% of new signups. Unsubscribe rate: 1.1% (21 unsubscribes). Draft email for stakeholders: 'Our email list grew 2.6% in the past month, adding 47 net subscribers. The homepage newsletter continues to be our strongest acquisition channel. Retention remains healthy with an unsubscribe rate below 1.5%. Recommend: double down on homepage CTA placement and test a lead magnet to accelerate growth.' This illustrative example combines Kit's subscriber data with AI synthesis.
This example pairs Kit's read-only data access with the AI's analytical reasoning to produce actionable insights. The draft email is generated by the AI, not stored in Kit. Useful for monthly reporting workflows, but verify subscriber counts match your Kit dashboard before sharing externally — data freshness depends on API sync timing.
Use-case deep-dives
When Kit MCP handles bulk list hygiene without export loops
A 3-person content team publishes two newsletters weekly and hits 40k subscribers across six forms. Every quarter they need to prune inactive tags, merge duplicate custom fields, and remove hard-bounced emails flagged by their support inbox. Kit MCP wins here because the 29 tools cover the full CRUD cycle—delete subscribers, remove obsolete tags, clean custom fields—all from a single Switchy thread without CSV round-trips or Zapier rate limits. The OAuth2 scope means the whole team can run cleanup scripts without sharing API keys. If your list is under 10k or you only touch Kit once a month, the native UI is faster. But once you're doing systematic hygiene or syncing subscriber state with another tool, this MCP pays off in the first session.
Kit MCP for event-driven tagging and webhook orchestration
A 5-person SaaS marketing team runs monthly product webinars and needs to tag registrants, trigger post-event sequences, and log purchase conversions back to their CRM. Kit MCP handles the webhook creation and tag assignment in real time—when someone registers via Typeform, Switchy calls Add Subscriber to Form and Create Tag to segment them by webinar topic, then sets up a webhook to catch the purchase event and update the CRM. The 29-tool breadth means you're not context-switching between Kit's UI, your CRM, and a middleware dashboard. This setup works best when you're running 4+ events per quarter and need consistent tagging logic. If you're doing one-off launches or your CRM already has a native Kit integration, skip the MCP and use the vendor's Zapier templates instead.
When Kit MCP bridges support tooling and email segmentation
A 6-person support team uses Intercom and wants to auto-tag Kit subscribers when a ticket is marked 'feature request' or 'bug report' so the product team can send targeted update emails. Kit MCP lets you wire this in a Switchy workflow: when a ticket closes, the agent prompts Switchy to look up the subscriber by email, create or apply the relevant tag, and optionally add a custom field with the ticket ID for future reference. The Delete Subscriber and Delete Tag tools also mean you can handle unsubscribe requests or tag corrections without leaving the support thread. This scenario only makes sense if you're already using Switchy for support triage and your team touches Kit data daily. If support and email are siloed teams, a dedicated integration platform like Segment is cleaner.
Frequently asked
What does the Kit MCP let me do in Switchy?
It connects your Kit email marketing account so your team can manage subscribers, tags, custom fields, forms, broadcasts, and webhooks through AI prompts. You can add people to forms, create segments with tags, delete broadcasts, or set up event notifications — all without switching to the Kit dashboard. The MCP exposes 29 tools covering subscriber lifecycle, content management, and automation setup.
Which OAuth scopes does Kit MCP request when I connect it?
Kit uses OAuth2, so you'll authorise Switchy during setup through Kit's standard permission flow. The exact scopes depend on Kit's API design, but the MCP needs read-write access to subscribers, tags, custom fields, forms, broadcasts, sequences, and webhooks. You'll see the full permission list on Kit's consent screen before you approve. Only Kit account admins can complete this connection.
Can the Kit MCP send email broadcasts or manage sequences?
It can delete broadcasts you've already created, but it won't draft or send new ones — that still happens in Kit's editor. For sequences, the MCP can subscribe or unsubscribe people and manage tags that trigger automation rules, but it doesn't build the sequence emails themselves. Think of it as subscriber and metadata management, not content authoring.
Why use this instead of Kit's dashboard or Zapier?
The MCP is faster for bulk subscriber ops and tag cleanup when you're already working in Switchy. Instead of exporting CSVs or building multi-step Zaps, you describe what you want in plain English and the AI calls the right tools. It's not a replacement for designing email templates or analysing campaign stats — Kit's dashboard still wins there. Use the MCP for operational tasks your team repeats weekly.
Who on my team should connect the Kit integration?
Whoever owns your Kit account and has admin rights. Once connected, any Switchy workspace member can use the MCP to manage subscribers and tags, so set this up if your marketing or ops team needs shared access without handing out Kit logins. Each action logs who triggered it in Switchy's audit trail, but Kit itself will only show the connected account as the actor.