All agents

Connect Roma to Grok Bot

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

Connect

Grok Bot is xAI's always-on Bot, a different app from Grok the chat. It has no settings screen for a server of your own: in the Bot's chat, send it https://api.roma.app/mcp and ask it to add Roma as a custom MCP server. It shows a card to confirm, then a Connect card: press it and sign in to Roma. The Bot signs in with OAuth; a key would go into a masked field it opens, never into the chat.

Tell Grok Bot how to use Roma

One message, saved once, makes Roma the to-do list Grok Bot keeps for you and the record of the work you do together.

Send it to your Bot as a message and ask it to remember it.

From now on, Roma is my to-do list and my work ledger. Please look through our recent conversations for anything I still need to do, show me the list, and add it to Roma once I confirm. Going forward: add anything I mention needing to do; answer "what should I work on next" from Roma; and whenever we work on a real work topic, find its item in Roma or make one, keep the result in the item, bring it up to date before we wrap up, and tell me in one line which item you updated. If Roma is not connected, say so.

How to use it

Once connected, talk to Grok Bot the way you already do. Roma 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."

What Grok Bot can do in Roma

  • Context. See where you are: what is due, your lists, recent notes, and what you asked Roma 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.
  • Triggers. Be woken instead of polling: a trigger tells your agent when an item changes, a status moves, you reply to it in a task chat, or a run finishes, and where to ring.

Grok Bot only ever acts as you, on your own workspace, and asks before anything changes.

Good to know

A Bot keeps its own instructions and memory, so tell it once how you want Roma used. Its routines can start from a webhook: open the routine in the desktop app (the phone apps do not show this yet) and its Webhook section shows the address to POST to and the key, which the Bot itself never sees; a 200 means a run started, and the run can use Roma's tools. The Bot can claim a mail inbox of its own, the name permanent once claimed, and a routine can wake on mail to it; mail it sends goes out on a card for you to approve unless you tell it to skip that.

If the sign-in window does not open at all, a pop-up blocker, an ad blocker or Safari is stopping it. Tell the app it did not open and ask for the sign-in link as plain text, then open it in a tab of your own. What can go wrong has the rest.

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 Grok Bot so it sweeps your mail, calendar and meeting notes into Roma on its own, triggers that wake it the moment something changes (a webhook, or a poll for an agent with no address), and the REST API. Developers.