Kit MCP

Live

API KEY

MARKETING

Marketing

Connect your AI agent to Kit to manage email subscribers, sequences, broadcasts, tags, and forms for your email marketing workflows. Agents can create and update subscribers, organize contacts with tags, enroll them in sequences, send broadcasts, and retrieve engagement analytics — all scoped to the authorizing Kit account.

  • Acts as the user: All Kit operations execute under the account that authorized the agent, so every subscriber update, broadcast send, and tag assignment is traceable to the account owner.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: Permissions enforced per-user. 90-day audit trail.
Kit MCP
agent · Acme Q3
Run
Add a tag 'vip' to all subscribers who clicked the last email campaign.
S
kit_tag_subscribers
112ms
Kit agent
Done! Tagged 847 subscribers with 'vip' — these are all contacts who clicked at least one link in your last campaign sent on Jun 18.
Sources: 847 subscribers, June campaign
kitmcp
847 subscribers
18:29
Message Claude...

Tools your marketing agent reaches for on Kit MCP, scoped per user.

CALL ANY TOOL
Kit MCP exposes tools for managing subscribers, tags, sequences, broadcasts, forms, custom fields, webhooks, and account analytics — giving agents full control over email marketing workflows.
kitmcp_add_subscriber_to_form
Add Subscriber To Form
Subscribe a single email address to a Kit form. Creates the subscriber if they do not exist; returns the subscriber record.
Parameters
Name
Type
Required
Description
email_address
string
Required
Subscriber's email address (required)
form_id
integer
Required
The form ID (required). Use list_forms to find IDs.
session_id
string
Optional
UUID v4 identifier for grouping tool calls in the same conversation. Generate once at the start of the session and reuse it on every call.
user_goal
string
Optional
What the creator is trying to accomplish with this tool call. Pick the closest match; use 'unknown' only when no category fits.
kitmcp_add_subscriber_to_sequence
Add Subscriber To Sequence
kitmcp_bulk_add_subscribers_to_form
Bulk Add Subscribers To Form
kitmcp_bulk_create_custom_fields
Bulk Create Custom Fields
kitmcp_bulk_create_subscribers
Bulk Create Subscribers
kitmcp_bulk_create_tags
Bulk Create Tags
kitmcp_bulk_tag_subscribers
Bulk Tag Subscribers
kitmcp_bulk_untag_subscribers
Bulk Untag Subscribers
kitmcp_bulk_update_subscriber_custom_field_values
Bulk Update Subscriber Custom Field Values
kitmcp_create_broadcast
Create Broadcast
kitmcp_create_custom_field
Create Custom Field
kitmcp_create_sequence
Create Sequence
kitmcp_create_sequence_email
Create Sequence Email
kitmcp_create_snippet
Create Snippet
kitmcp_create_subscriber
Create Subscriber
kitmcp_create_tag
Create Tag
kitmcp_create_webhook
Create Webhook
kitmcp_delete_broadcast
Delete Broadcast
kitmcp_delete_custom_field
Delete Custom Field
kitmcp_delete_sequence
Delete Sequence
kitmcp_delete_sequence_email
Delete Sequence Email
kitmcp_delete_webhook
Delete Webhook
kitmcp_filter_subscribers
Filter Subscribers
kitmcp_get_account
Get Account
kitmcp_get_account_colors
Get Account Colors
kitmcp_get_broadcast
Get Broadcast
kitmcp_get_broadcast_clicks
Get Broadcast Clicks
kitmcp_get_broadcast_stats
Get Broadcast Stats
kitmcp_get_broadcasts_stats
Get Broadcasts Stats
kitmcp_get_creator_profile
Get Creator Profile

For more tools, view docs.

Build your Agent
Same auth pattern across every framework.
Try these prompts
Prompts that put Kit MCP tools to work immediately.
SEE HOW AUTH WORKS
Scalekit vaults and refreshes Kit credentials so your agent never handles tokens directly.
1
Authorize
Your user connects
Kit MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Kit MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Kit MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Kit MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
More MCP connectors with the same auth model.
SALES
Outbound prospecting agent
Build targeted prospect lists with Apollo, enrich with firmographic data, and draft personalised outreach. Runs on a schedule.
GTM
HubSpot to Slack updates agent
Watch HubSpot deal stage changes and post structured updates to the right Slack channel. Reps stop checking the CRM all day.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Why teams build on Scalekit instead of rolling their own.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Kit as the user or as a shared service account?
As the user. Scalekit resolves the OAuth token for the specific person who authorized the agent. Every subscriber update, tag assignment, and sequence action is performed under their Kit account — not a shared API key or service credential.
What data can the agent access through Kit MCP?
The agent can access subscriber profiles (email, name, custom fields, tags), email sequences, broadcast drafts, forms, automations, and account-level analytics. Access is scoped to whatever Kit OAuth scopes were granted at authorization time — the agent cannot reach data outside those permissions.
Are agent actions in Kit reversible?
Some are, some are not. Adding or removing tags, updating subscriber custom fields, and unsubscribing contacts can generally be reversed manually in Kit. However, sending a broadcast or triggering an automation sequence cannot be undone once dispatched — those emails are delivered immediately. Use listScopedTools to block destructive or send-capable tools if you want the agent to operate in a read-only or draft-only mode.
How does Scalekit secure the Kit MCP connection?
Scalekit vaults the Kit OAuth token with AES-256 encryption at rest. The token is resolved at request time and never written into LLM context, agent memory, or logs. If the user revokes access in Kit, the next tool call fails immediately with an auth error — Scalekit does not cache stale tokens past revocation.
Kit charges per subscriber. Can the agent accidentally import contacts and increase my bill?
Yes, if the agent has access to subscriber-creation tools. You can prevent this by using listScopedTools to expose only read and tag-management tools while blocking kit_create_subscriber and kit_import_subscribers. This way the agent can manage and segment your existing list without ever adding new contacts that would push you into a higher billing tier.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""kitmcp"": {
""url"": ""https://mcp.scalekit.com/kitmcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.kitmcp]
url = ""https://mcp.scalekit.com/kitmcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""kitmcp"": {
""url"": ""https://mcp.scalekit.com/kitmcp"",
""type"": ""http""
}
}
}