›Plan the implementation for ROOMIE-167
Reads the ticket, finds the three related messages in #engineering and the client's email, and writes the plan underneath. You skipped fifteen minutes of context gathering.
Roomie runs an MCP server. Claude, Codex, ChatGPT, Cursor, Kimi: if your AI speaks MCP, it can read your tasks, messages, emails, and calendar. No plugins. No API keys to manage.
We got tired of copy-pasting task descriptions into AI chats. So we built a way for the AI to just... look it up itself.
Run in your terminal:
claude mcp add --transport http roomie-workspace \ https://app.roomie.work/v1/api/mcp
Authorize with your Roomie account. That's it.
What it can do→MCP stands for Model Context Protocol. Think of it as a universal plug between your AI and the apps you use. Instead of the AI being stuck reading only what you paste into the chat, MCP lets it query live data from your workspace on its own - your tasks, messages, emails, and calendar.
Anthropic introduced MCP in late 2024, and every major AI tool now supports it: Claude Code, Codex, ChatGPT, Cursor, Kimi and Antigravity. It's an open standard, and the list keeps growing.
The practical upside: when you ask Claude “what's blocking the Acme deal?”, it doesn't need you to paste tasks or emails. It opens the right tool on its own and answers. You spend less time gathering context for your AI.
Ask “what happened with the Acme deal this week?” and it reads the messages, the tickets and the mail to answer: and it can write back, so a wiki page or a blog post is something it edits, not something it hands you to paste.
Real sentences, typed into whichever client you connected. Nothing pasted in first.
›Plan the implementation for ROOMIE-167
Reads the ticket, finds the three related messages in #engineering and the client's email, and writes the plan underneath. You skipped fifteen minutes of context gathering.
›Create a task from the last support email
Finds the thread, opens a ticket on the right board, assigns it, sets the priority from the tone and links the original mail. About three seconds.
›Update the onboarding page with the new VPN steps
Opens the space, finds the page, rewrites that one section and leaves the rest alone: the wiki is a live document to it, not a search result.
›Draft a launch post about the new office and publish it
Writes the post into your blog collection, sets its SEO title and description, and publishes to your domain. You review it as a page, not as a draft in a chat.
›Summarize #product this week
Forty-seven messages, twelve task updates and three meetings, in something you can paste into a standup doc. Useful on a Monday.
›Brief me on Acme Corp before my 2pm
Two weeks of messages mentioning Acme, the open tickets and the contract thread. You walk in knowing what happened rather than pretending to remember.
MCP is different because the AI lives where you already work - your terminal, your IDE, the ChatGPT app, and Roomie is just one of its data sources. You pick the model. You pick the tool. Roomie gives it the data. Here's how it stacks up.
Automations are deterministic. You pre-define triggers and actions. MCP is conversational, the AI decides what to query based on your question. No workflows to design; no triggers that stop firing when you rename a field.
Those only work inside their own app, with the vendor's model, on the vendor's terms. MCP works in your terminal, your IDE, or any client, and swaps models without vendor lock-in.
A custom build means maintaining the integration, the auth, and the tool-schema glue for every model you support. MCP is a single open protocol: the server advertises its tools, and every compliant client uses them. Ship once, support every model.
Pick your client below. Sign in to Roomie first so OAuth has something to authorize against, then run the command and approve the browser prompt.
Run in your terminal:
claude mcp add --transport http roomie-workspace \ https://app.roomie.work/v1/api/mcp
Authorize with your Roomie account. That's it.
What it can do→If it does not pick the server up
app.roomie.workand run it again.MCP stands for Model Context Protocol. It's an open standard introduced by Anthropic in late 2024 that lets an AI agent read live data from an external app on its own, instead of relying on what you paste into the chat. Roomie runs an MCP server, so any MCP-compatible AI can query your tasks, messages, emails, and calendar directly.
Anything that speaks MCP. Today that includes Claude Code, Codex, ChatGPT, Cursor, Kimi and Antigravity; a generic JSON config covers everything else. When a new MCP client ships it works with Roomie automatically. Nothing to update on your side.
No. For Claude Code, Codex and Kimi it is a single terminal command. For ChatGPT it is pasting a URL into Settings, and for Cursor a short JSON block in a config file. The setup card on this page has all of them. Most people are connected in under two minutes.
The AI only sees what you, the logged-in user, can see. Authentication happens over OAuth with your Roomie account, no API keys to manage or leak. The AI cannot send messages, delete data, or act on your behalf unless you explicitly ask it to and approve the action.
Zapier runs deterministic workflows. You define triggers and actions in advance. MCP is the opposite: the AI decides what to look up, when, based on your question. No automations to design. You ask something, the AI figures out which Roomie tool to call and does it.
No. MCP is model-agnostic. Roomie works equally well with Claude, Codex, ChatGPT, Cursor, Kimi, and any future client that supports the protocol. You pick the model based on cost, speed, or capability · Roomie just provides the data.
Every plan, including the free one. There is no add-on fee and no separate subscription: what differs between plans is the monthly AI token allowance, not whether your own agent may connect.
Yes. The AI respects the same permission model as the rest of Roomie: private channels, DMs, and restricted projects are invisible to it unless the authenticated user has access. You can also revoke an MCP connection from the settings page at any time, which immediately cuts off the agent.
Both. The hosted server runs at app.roomie.work, and a self-hosted instance runs its own MCP endpoint on your domain alongside the rest of the workspace, so an agent can reach it without anything leaving your network.
After authorizing, ask your AI something like "summarize my open tasks" or "what did the team discuss in #product yesterday?" If it returns real data from your workspace, you're connected. If it asks you to paste things in, it didn't pick up the server, check the setup config and re-run the command.
Still stuck? Send us a message. We reply within a day.
Connect your AI to Roomie. It can look things up on its own.
Free for up to 3 users, then $2 a user. MCP is on every plan.