Your Kit list, its growth, tags and broadcasts, answered without logging in.
Connect Kit with a V4 API key and Memtro reads subscriber growth and email stats for any period, subscribers with their tags, forms, sequences and broadcast stats. Every hour it writes each new subscriber into memory. When you ask, and once an administrator has granted each action by name, it can tag and untag subscribers, add or update them, unsubscribe them, add them to a sequence or form, and draft, edit or schedule broadcasts. A scheduled broadcast emails its audience and cannot be recalled, and tags and sequences can start automated emails.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Kit tool, reads what it needs, and answers with the source cited.
These tools change something in Kit. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Kit for you. Each event can start a job, with the event as its input. Kit signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Kit is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
How many subscribers did we gain and lose in October, and what is the net?
Is sarah.mills@example.com on the list and what is she tagged?
What was the open rate on the last five broadcasts?
Which landing page has brought in the most subscribers?
Tag james@northgate.co.uk as 'webinar-attended'
The morning after a launch email, the founder asks how it did. Memtro returns the broadcast's recipients, open and click rates and unsubscribes, compares them with the previous four sends, and notes how many people joined the list overnight.
After a webinar, Holly Grant asks Memtro to draft a follow-up broadcast to everyone tagged webinar-attended and send it at 9:00 tomorrow. Memtro saves the draft in Kit, shows her the subject and text, and schedules it when she approves. At 9:00 Kit emails everyone with that tag.
The teams that lean on Kit most, a question each of them asks, and what they connect beside it.
A record in Kit is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
ActiveCampaign
Klaviyo
MailerLite
GetResponse
Instantly
lemlist
Drip
Omnisend
Mailjet
Moosend
Smartlead
Iterable
Dotdigital
Flodesk
LoyaltyLion
Benchmark Email
Braze
Sender
Rewardful
Mailshake
SurveySparrow
RetentlyIn Kit open Settings → Developer → API Keys and create a V4 API key. The v3 key and secret on the same page do not work
A V4 key has full access to the account and Kit does not scope it, so Memtro acts only when you ask and an administrator has granted that action by name
In Memtro open Connections → Kit, paste the API key and connect. Memtro names the connection after your account, and Kit allows the key 120 requests in any rolling minute
Ask how the list grew this quarter or how the last broadcast did
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Kit tools are the same everywhere.
Only when you ask, and only what it has been granted: add a tag to a subscriber; remove a tag from a subscriber; create a tag; rename a tag; add a subscriber; change a subscriber's name, email or custom fields; unsubscribe a subscriber from all email; add a subscriber to a sequence, which starts its emails; add a subscriber to a form; draft a broadcast; edit a draft or scheduled broadcast; schedule a broadcast to email its audience; delete a draft or scheduled broadcast. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Kit records into memory as entities.
API key. In Kit open Settings → Developer → API Keys and create a V4 API key. The v3 key and secret on the same page do not work.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Kit for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time