Connect Koma to Cursor
Cursor sees what's due, adds what you mention, and knows what's next.
Use the one-click link, Add Koma to Cursor, or add this to ~/.cursor/mcp.json (or the project's .cursor/mcp.json) and sign in when Cursor asks:
{
"mcpServers": {
"koma": { "url": "https://koma.ac/api-preview/mcp" }
}
}
How to use it
Once connected, talk to Cursor the way you already do. Koma is there whenever a task comes up:
- "What's on my plate today?"
- "Add "call the dentist" and "send the invoice", both for Friday."
- "Save the plan we just made as a note."
Make Koma your to-do list
Koma works best as the one list behind everything: tell Cursor what you need to do and it lands in Koma; ask any agent, or Koma itself, what is next and it answers from the same list. Nothing lives only in one chat.
Send this once. Cursor makes Koma its to-do list, looks through your recent conversations for what is still open, and keeps Koma current as you work.
Koma is my to-do list from now on. Look through our recent conversations for anything I still need to do, show me the list, and after I confirm add it to Koma. From here on: add anything I mention needing to do to Koma, answer "what should I work on next" from Koma, and when something we discussed gets done or changes, update it in Koma.
What Cursor can do in Koma
- Context. See where you are: what is due, your lists, recent notes, and what you asked Koma to remember.
- Lists. Keep any list: your tasks, your notes, a reading list, a CRM, each with the properties you give it. Create one, reshape it, delete it.
- Items. Add, update, move and delete what is on a list, many at once: a task with its due date, a note, a book on a reading list, each with a body to work in.
- Search. Find anything you keep, by meaning or keyword.
- Chats. Read the chat on an item, and leave a note there under its own name, so you see it on every device.
- Trash. Nothing is lost on delete: the trash keeps it for about 30 days and puts it back.
- Automations. Read your automations and what their runs found, and start one when you ask.
Cursor only ever acts as you, on your own workspace, and asks before anything changes.
Good to know
If the sign-in window does not open at all, some setups block it. Tell the app that it did not open; it gives you the link to open yourself.
Go deeper
The setup above is all most people need. The developer docs have the rest: every tool with what it takes and returns, guides for saving research, filling a list and running a worker loop, the standing orders to paste into a scheduled Cursor so it sweeps your mail, calendar and meeting notes into Koma on its own, the event feed and the REST API. Developers.