Cursor
Call Rotor workflows from Cursor's agent mode.
Cursor's agent mode can trigger and inspect Rotor workflows via the MCP server. Build your automation in Cursor, dispatch it from the same editor, watch it run in production.
How it works
Rotor exposes a standard MCP server. Add it to Cursor's MCP settings and your workflows appear as tools in agent mode. The bearer token authenticates every call — no separate auth flow required.
Setup
// Cursor MCP settings (settings.json)
{
"mcp": {
"servers": {
"rotor": {
"command": "npx",
"args": ["-y", "@rotor/mcp"],
"env": { "ROTOR_API_KEY": "rtr_live_..." }
}
}
}
}Stop babysitting cron. Start shipping.
Your workflows retry themselves. Your pipeline runs unattended. You sleep.
Start shipping$9 to start. 30-day money back.