Yes — Cursor can build, launch and manage your Instagram DM campaigns in WarmySender, all in plain language, through the same 78-tool connection Claude, ChatGPT, Cursor, Codex, OpenClaw, and Hermes Agent share. You ask in Cursor’s chat panel, inside the editor. It never sends a message itself and can never raise a limit: it writes the campaign and hands it to WarmySender’s scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits no matter who is driving. Connecting and disconnecting accounts stays in the app.
You talk to Cursor in the chat panel of the editor you already work in, so outreach sits next to the code and files of the project. It connects with the one-click Add to Cursor button, or a small block in .cursor/mcp.json in your project root; sign in when Cursor asks. Instagram DM campaigns from Cursor suit an operator whose handle lists are generated by code in the same project — build the follow → like → DM sequence from the chat panel, enroll, and read back reply and follow-back numbers.
Every "can" below stands on a real tool in the WarmySender connection. Every "cannot" is not a setting — there is simply nothing an agent can call that does it.
| Can / cannot | What that means for Instagram DM outreach |
|---|---|
| Can | Create a DM campaign and choose the account and the steps — follow, view, like, comment, then message. |
| Can | Start, pause and resume a campaign, and enroll people from your lists or by handle. |
| Can | Report on how a campaign is doing and why an account is quiet today. |
| Cannot | Send a DM, follow, like or comment itself — WarmySender’s scheduler paces every action inside each account’s strict daily and hourly caps. |
| Cannot | Raise the daily or hourly ceiling, shorten a new account’s ramp, or fire actions in a burst. |
| Cannot | Connect or disconnect an Instagram account — that stays in the app and needs an Instagram seat. |
| Cannot | Read or reply to DMs — that happens in WarmySender’s inbox, with you. |
| Cannot | Write a DM or comment longer than Instagram itself allows. |
Cursor connects with one click from your browser, or one small file in your project — then you drive outreach from the editor you already work in.
Use the Add to Cursor button, or paste this into .cursor/mcp.json in your project root and sign in when Cursor asks.
File: .cursor/mcp.json
{
"mcpServers": {
"warmysender": {
"url": "https://warmysender.com/mcp"
}
}
}
Prefer a key? Create one under Settings › API Keys and choose exactly which permissions it carries, including read-only. With a key, the Cursor route is: Use the Add to Cursor button, or paste this into .cursor/mcp.json in your project root.
Both routes reach the same workspace and stay inside the same safe limits. Every agent's steps live on the AI Agents hub.
Create an Instagram campaign on my brand account: follow, like their latest post, then DM two days later, and enroll these 30 handles.
Pause the "Creators" Instagram campaign and tell me how many people are still waiting.
Why did my Instagram account do nothing this afternoon?
Show me reply and follow-back numbers for every Instagram campaign this month.
Read data/handles.csv from this project, create a follow → like → DM campaign on my brand account, and enroll them all.
Cursor never sends a message itself and can never raise a limit. Creating or launching a campaign only writes it and hands it to WarmySender's scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits and a gradual ramp — the same protections that apply when a human clicks the buttons. Connecting and disconnecting accounts stays in the app. Account safety always wins.
Yes. Connect Cursor to WarmySender and ask in plain language, in Cursor’s chat panel, inside the editor — it can build, launch and manage your Instagram DM campaigns. It never sends a message itself and can never raise a limit: it writes the campaign and hands it to WarmySender’s scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits no matter who is driving. Connecting and disconnecting accounts stays in the app.
Cursor connects with one click from your browser, or one small file in your project — then you drive outreach from the editor you already work in. Use the Add to Cursor button, or paste this into .cursor/mcp.json in your project root and sign in when Cursor asks. The block for .cursor/mcp.json is: { "mcpServers": { "warmysender": { "url": "https://warmysender.com/mcp" } } } — the server address is https://warmysender.com/mcp. The steps are on this page under "Connect Cursor", and the full install hub for every agent is at /ai-agents.
No. Nothing an agent can call moves a limit — not the combined daily and hourly action budget or a new account’s ramp. Cursor can read where you are against a limit and tell you when a pause lifts; WarmySender’s scheduler decides what actually goes out.
No. Connecting and disconnecting accounts stays in the app on purpose — a credential should never pass through an agent or a chat log. Connect the Instagram account once in WarmySender; after that Cursor can use it.
Exactly as they do otherwise. Every follow, view, like, comment and DM draws from one combined daily and hourly budget per account, new accounts start well below the ceiling and climb over their first weeks, and actions are spaced with natural randomness — never bursted. A heavier sequence uses more of the day’s budget per person and reaches fewer people. For more reach, connect another account; nothing an agent can call raises the ceiling.
It opens Cursor and offers to add the WarmySender server — the same result as pasting the block on this page into .cursor/mcp.json (the server address is https://warmysender.com/mcp). Accept, sign in when Cursor asks, and the Instagram DM outreach tools are available in the chat panel.
The block on this page goes in .cursor/mcp.json in the project root, so it travels with that project. Cursor also supports a global configuration file; either way the sign-in is the same and the safe limits are identical.
A sign-in: Cursor asks you to sign in to WarmySender the first time it reaches the server, so no key is written to .cursor/mcp.json. Prefer a key? Create one under Settings › API Keys and use the key form on the AI Agents hub.
Last updated: 2026-09-09