Send email campaigns on Listmonk from Cursor
Cursor can send campaigns on Listmonk through ClipSpeed. Add the ClipSpeed server with one config block, sign in, and then ask Cursor to send campaigns, pick the time, and apply Listmonk's settings, without leaving the Cursor editor's Agent. Listmonk is on the roadmap on ClipSpeed's rail; this page describes how it works and says so.
Keep a human in the loop: Cursor shows the plan and asks before anything is public. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn.
Also try
How to send email campaigns Listmonk from Cursor
Cursor reads MCP servers from a JSON file. Add the block, open Cursor Settings → MCP, click the sign-in for clipspeed, and the Agent has the tools. Connect Listmonk in ClipSpeed, then describe the post. Setup takes about a minute.
# One-time setup: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"clipspeed": { "url": "https://api.clipspeed.ai/mcp" }
}
}
# Then ask Cursor:
> Send the newsletter to the Weekly list Friday 10am
Cursor: Preview — nothing booked yet. Listmonk — title. Book it?Cursor shows the tools under Settings → MCP once the server connects. If the list is empty, check the JSON and restart Cursor. ClipSpeed has not yet seen a real Cursor session connect; the setup is Cursor's documented MCP route and the URL is the same as every verified client.
- Create .cursor/mcp.json in the project (or ~/.cursor/mcp.json for every project) with the block shown.
- Open Cursor Settings → MCP. clipspeed appears; click to authenticate and approve the ClipSpeed sign-in.
- Open the Agent panel and ask it to list your channels.
- Connect Listmonk in the ClipSpeed app, or ask Cursor for a connect link: it is private, valid for ten minutes, and Listmonk signs you in itself.
Developer reference: the Cursor MCP page.
What can Cursor do on Listmonk?
On Listmonk, Cursor can create and schedule email campaigns to a list on your Listmonk. Every booking runs through the same rules as the ClipSpeed app.
Text and Image posts
Listmonk takes text and image through ClipSpeed. Image: images by URL inside the email.
Limits checked at booking
the title is the email subject. Titles are required and cap at 200.
Exact time or refused
Name the minute and Cursor books it, or you are told why not and offered the next open slot. A booked Listmonk post is never moved behind your back.
Preview before anything posts
preview: true runs the whole booking and writes nothing. Cursor shows the plan, with each slot and the day's remaining cap, and books only on your yes.
Clips cut in the same chat
Submit a video or stream link, get captioned 9:16 clips with a viral score, and post the best moment's hook on Listmonk with a link to the clip. No download, no re-upload.
Pacing and numbers
Planned: Text posts on Listmonk are at least 240 minutes apart, up to 2 a day. After a post goes out, Cursor can read back views and engagement where Listmonk provides them.
How does Cursor post to Listmonk through ClipSpeed?
You describe what you want in plain language and Cursor makes the ClipSpeed calls. A typical conversation has three beats.
Find your Listmonk channel
Ask Cursor whether Listmonk is connected. It calls list_channels and reads platform_settings, so it also knows what Listmonk accepts and the limits before you write a word.
Compose within the rules
Describe the post. Cursor drafts within Listmonk's limits; mention a clip or a file and it attaches it.
Schedule or publish
Name a time, or say now. The slot is booked exactly or refused with the next open one, and the reply carries the id you can cancel or edit by.
Listmonk settings reference
These are the schedule_post fields that apply to Listmonk. Mention any of them in plain language and Cursor sets them; the server checks them at booking. Fields marked planned land with the Listmonk release.
| Field | Type | Required | What it does on Listmonk |
|---|---|---|---|
platforms | string[] | Yes | Include "listmonk". Up to ten platforms per call; each books its own slot. |
title | string | Yes | The subject line. |
text | string | Yes | The email body in HTML or Markdown. |
list | string | Planned | The Listmonk list to send to. |
scheduled_at | ISO 8601 | No | The send time; exact or refused. |
preview | boolean | No | Plan only. |
Common Listmonk configurations
Ask Cursor for any of these and it applies the matching settings.
Weekly newsletter
Launch broadcast
Test to yourself
Preview
Example prompts for Listmonk in Cursor
Type these into the Cursor editor's Agent, or pass one to terminal in a script. Cursor calls ClipSpeed and confirms before publishing.
Send email campaigns Listmonk with a scheduled time
Send the newsletter to the Weekly list Friday 10am. Preview first.
Cut the clips, then post the hook
Clip this link, keep the top moment by viral score, and write a Listmonk post from the best moment's transcript, scheduled for tomorrow 9am. Show me the plan before booking.
From a script with Cursor
cursor-agent -p "Summarise the changes since the last git tag as one Listmonk post with a title. Schedule it via ClipSpeed for today at 10am; preview first and book if nothing is refused."
Listmonk limits and gotchas to know
Listmonk enforces a few rules that Cursor and ClipSpeed respect automatically, but knowing them helps you phrase requests.
- Email is unforgiving: a sent campaign cannot be recalled. Use preview and a test list.
- Listmonk is self-hosted; you connect your own instance with an API user.
- Listmonk is on ClipSpeed's roadmap, not the next rail. Bookings are refused plainly until it posts.
- Pacing is deliberately tight: two campaigns a day four hours apart.
- Templates and personalisation fields are planned.
| Rule | Listmonk |
|---|---|
| Accepts | Text, Image |
| Text limit | the title is the email subject |
| Title | 200 characters, required |
| Links in the caption | Kept |
| Pacing | Planned: Text posts on Listmonk are at least 240 minutes apart, up to 2 a day. |
| Formats | Image: images by URL inside the email. Aspect: any |
| Status | On the roadmap; described here, not yet bookable |
What Postiz-style schedulers cannot do
Cut the clips first
Cursor does not need finished video to start. Hand it a YouTube link, a podcast, a stream VOD or a local export. ClipSpeed finds the moments, cuts them to 9:16 with word-by-word captions, scores each one 0 to 100 for shareability, and returns them in the same conversation. Cursor picks by score, writes the post from the transcript, and books the best moments as links on Listmonk. Three tool calls, one approval, no download and no re-upload.
- Clips arrive with a title written from the hook, a transcript and a viral score, so the agent can choose and caption without watching the footage.
- Live streams can be clipped while they are still on air; the agent books the highlights for the next morning before the stream ends.
- Every clip is already hosted, so
schedule_posttakes its id directly. Nothing moves through your laptop.
submit_to_clipspeedPaste the link. ClipSpeed starts the job and returns a project id.check_clipsPoll with the project id. Back come the finished 9:16 clips with titles, transcripts, viral scores and preview links.schedule_postPass the clip id, the platforms, a caption and a time. Cursor shows the plan with preview: true, you say yes, it books.generate_image or generate_videoDescribe the shot. ClipSpeed runs it on the model that fits (Seedance, Kling, Veo, Nano Banana Pro, GPT Image and others) and quotes the credits first.wait_for_generationReturns the hosted result link and a preview the agent can show you.schedule_post with media_urlThe result link goes straight into the booking on Listmonk. The caption, the time and the file are approved together.The other half nobody else has
Generate the image, then post it
A product shot for Instagram, a 16:9 announcement graphic for X, a six-second opener before a clip: Cursor can make an image with ClipSpeed's image and video models and book the result in the same reply. There is no separate design tool, no export, no upload page. The generated file is hosted, so media_url is the only thing the booking needs.
- The price in credits is quoted before anything renders, within the per-generation and daily caps you set in Settings.
- Results are previewed in the conversation, so you approve the picture and the post at once.
- Images post as JPG, PNG or WebP up to 25 MB; links are kept clickable.
What is Cursor?
Cursor is the AI code editor built on VS Code. Its Agent runs multi-step tasks in your project, runs commands and calls MCP tools. With ClipSpeed in Cursor's MCP settings, the Agent can clip a video, generate media and schedule posts from inside the editor, and the Cursor CLI can do the same from a script.
How ClipSpeed works with Cursor
- Cursor reads .cursor/mcp.json and connects to the ClipSpeed server; sign in under Settings → MCP
- The Agent reads
platform_settingsbefore composing schedule_postbooks exactly or refuses with the next open slotpreview: truefor a plan with nothing booked- cursor-agent -p runs the same flow from a script
Cursor vs Windsurf vs Claude Code: Cursor (cursor editor, cursor-agent), Windsurf (windsurf editor), Claude Code (terminal). This page is about Cursor; the Cursor guide compares them.
{
"mcpServers": {
"clipspeed": {
"url": "https://api.clipspeed.ai/mcp"
// no browser on this machine? add:
// "headers": { "Authorization": "Bearer csai_live_..." }
}
}
}
# .cursor/rules/clipspeed.mdc
# Always call schedule_post with preview: true first and show the plan.
# X posts stay under 280 characters; every link counts as 23.# What the agent reads at connect time (tool descriptions, abridged)
list_channels Connected platforms, what each accepts, limits, your time zone
connect_channel A private 10-minute link to connect one platform
platform_settings Limits, title rules, link handling, pacing per platform
schedule_post clip_id | text | media_url → platforms[], scheduled_at, preview
list_scheduled_posts Scheduled, sending, posted, failed — with post links
update_scheduled_post Edit copy while still scheduled (the time never moves)
cancel_scheduled_post Cancel; undoable 72 h in the app
post_analytics Views, likes, comments, shares where the platform gives them
submit_to_clipspeed Start clipping a video or stream link → projectId
check_clips Finished 9:16 clips with titles, transcripts, viral scores
generate_image / generate_video / wait_for_generation
# Listmonk: text/image · text n/a · title 200 requiredSend email campaigns on Listmonk and other platforms from Cursor
One request can book the same content to Listmonk and other channels, each keeping its own settings and its own slot. Every platform below has its own Cursor guide.
Also works with
Listmonk and Cursor: frequently asked questions
How do I send email campaigns to Listmonk from Cursor?
Create .cursor/mcp.json in the project (or ~/.cursor/mcp.json for every project) with the block shown. Open Cursor Settings → MCP. clipspeed appears; click to authenticate and approve the ClipSpeed sign-in. Connect Listmonk in ClipSpeed (or ask Cursor for a connect link; it is private and valid for ten minutes), then describe the post in plain language. Cursor reads the Listmonk rules, drafts within them, shows the plan and books on your yes. Listmonk is on the roadmap; until the badge changes, the booking is refused with a plain message.
What can Cursor post to Listmonk through ClipSpeed?
Create and schedule email campaigns to a list on your Listmonk. Listmonk takes text and image posts. A title is required and is capped at 200 characters.
Which Listmonk settings can Cursor control?
The fields in the settings reference above: title, text, list, scheduled_at, preview. Mention any of them in plain language ("unlisted", "tomorrow at 9", "preview first") and Cursor sets the matching field before it books.
Do I need a Listmonk API key or developer account?
No. You connect Listmonk to ClipSpeed once through Listmonk's own sign-in, and Cursor talks to ClipSpeed over OAuth. No Listmonk developer key, bearer token or password is pasted anywhere.
How many Listmonk posts a day can Cursor schedule?
Planned: Text posts on Listmonk are at least 240 minutes apart, up to 2 a day. When a time is taken, the booking is refused with the next open slot rather than moved. Ask for preview to see a day's plan and the remaining cap before anything is booked.
Can Cursor post to Listmonk from a script or a cron job?
Yes. Cursor's headless mode (terminal) runs one prompt and exits, and the ClipSpeed server registered on that machine does the booking. On a runner with no browser, authenticate with a ClipSpeed API key header. Keep preview on so the run reports a plan before it books.
Is posting to Listmonk from Cursor different from Windsurf?
The booking is identical: the same rules, the same calendar, the same refusals. What differs is where you work. Cursor: the cursor editor; cursor-agent on the command line. Windsurf: windsurf editor, cascade agent; same url.