An earlier version of this guide used a partner service (Ogment.ai) to turn Cursor’s API into an MCP server. That service is no longer offered, so this guide now uses Notis’ built-in MCP support instead.
What you’ll need
- A Cursor account that can run cloud agents
- An MCP server that exposes Cursor’s coding agents (see Step 2)
- Notis with MCP support
Step 1: Get your Cursor API key
- Go to your Cursor dashboard
- Open Integrations
- Create a new API key and copy it — the MCP server will use it to talk to Cursor on your behalf
Step 2: Pick an MCP server for Cursor
Cursor doesn’t offer an official MCP server for managing its cloud agents, but community-built ones exist — you’ll find them on MCP directories like cursor.directory. Any server built on Cursor’s Agents API works; look for one with tools to launch an agent, check its status, and send follow-ups. These servers come in two flavors, and Notis supports both:- Hosted — the server runs on the internet and gives you a URL.
- Runs on your computer — the server’s instructions give you a small command to run, and it works right on your machine.
Step 3: Connect it to Notis
If your server is hosted: Add an MCP server with these values:-
Display Name:
Cursor - Description: a few words on what it does. For example: “Manages my Cursor coding agents”
- Server URL: the URL your server gives you
- Authentication: if the server asks for your Cursor API key, choose Headers and add your key from Step 1 the way the server’s instructions show
You’re done!
Ask Notis things like “start a coding agent on my repo to fix the login bug”, “how’s my coding agent doing?”, or “tell the agent to also update the tests” — directly from:- Telegram
- iMessage
- Slack

