Cursor
Your project, inside the editor. You approve the send.
Cursor reaches your project through the MCP server while you write the integration: it checks which events and attributes really arrive, compares them with your code and prepares the segment or the campaign that goes with the change. Sending waits for your approval.
Cursor, working on a real project
Connect Cursor to your project
The fast way. Paste this prompt into Cursor and it does the three steps for you.
Or do it by hand:
- 1
Add the server
In Cursor, add a server with Instasent's address from the MCP section of its settings — or add it to mcp.json under mcpServers with its url.
- 2
Sign in
Press Connect next to the server. Cursor opens Instasent in your browser: sign in, pick the project and the permissions it gets. The connection is listed under Connected apps, and you can revoke it any time.
- 3
Check it
In the agent chat, ask it to list Instasent's tools and count your contacts. If the figure matches, you are connected.
What to ask Cursor
- Which events has our store sent in the last 24 hours, and which attributes come empty?
- Compare the payload in checkout.ts with the attributes in my audience and tell me what is missing.
- Create a segment of carts abandoned in the last day so I can test the new event.
- Leave a campaign draft for that segment, ready for me to review in the panel.
What Cursor will not do on its own
- It reads everything.
- Audience, campaigns, flows and results of the project you connect.
- It creates and leaves it ready.
- Segments and campaign drafts that match your change, prepared for you to review.
- It never sends.
- Sending waits for your approval, every time. No agent sends on its own.