All agents

Connect Koma to Muse

Muse sees what's due, adds what you mention, and knows what's next.

How to connect

An official Koma connector for Muse is on its way. The prompt connects it today.

Send Muse this prompt. It connects, opens the sign-in for you to approve, and then asks what to do with your tasks.

Connect to Koma, my task app, as an MCP server at https://koma.ac/api-preview/mcp (Streamable HTTP, OAuth 2.1 with PKCE and dynamic client registration; the first call answers 401 with the discovery address). Create a Custom Connector for a remote MCP server with that URL and Auth: OAuth, on your own cloud computer, and keep it in your Secure Credentials Store so it is there next time. Before you open the sign-in link, tell me what will happen: I sign in and approve in my browser, and if the page after that does not load, I copy that page's link and paste it back to you; and if the sign-in window does not open at all, I just tell you, because some setups block it and there are other ways to connect. Then open the link. If I say it did not open, give me the link to open myself. Read https://koma.ac/llms-full.txt for how the tools work. Once connected: 1) call get_context and tell me in a few lines what you can see and what you can do for me from now on; 2) look through our recent conversations for anything I still need to do, show me the list, and only after I confirm add them to my Tasks list in one call with create_items; 3) ask whether Koma should be my task list from now on, and if I say yes, save this in your memory or instructions: always use Koma for my tasks, add anything I mention needing to do to Koma, answer "what should I work on next" from Koma, and as we work, check in now and then whether something we discussed should become a task in Koma.

  1. Paste the prompt into Muse. It creates the connector on its own cloud computer and shows a Connect button.
  2. Press Connect, sign in to Koma, and approve.
  3. Muse confirms, keeps the connector in its Secure Credentials Store for next time, and asks whether Koma should be its to-do list. Say yes.

How to use it

Once connected, talk to Muse 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 Muse 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.

The connect prompt above already asks Muse for this. To set it again in a new conversation, send this once:

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 Muse 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.

Muse 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 when you press Connect, some setups block it; tell Muse, and it gives you the link to open yourself. If the page after you approve shows a link to copy, paste it to Muse. If Muse asks for a key instead, create one in Koma under Settings, then Connections, and paste it only into Muse's secure credential prompt, never into the chat itself.

Muse Code, the terminal agent, takes the server in ~/.config/muse/settings.json:

json
{
  "schema_version": 1,
  "mcp_servers": {
    "koma": { "transport": "streamable_http", "url": "https://koma.ac/api-preview/mcp" }
  }
}

Then muse mcp login koma for the sign-in. It reads an AGENTS.md, where a standing line like "use Koma for my tasks" lives.

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 Muse so it sweeps your mail, calendar and meeting notes into Koma on its own, the event feed and the REST API. Developers.