What the Revo MCP server is

MCP, the Model Context Protocol, is an open standard for connecting AI assistants to real systems. Revo runs an MCP server. You point your assistant at it once, sign in with your normal Revo account, and from then on the assistant can look things up in your workspace and take action there.

What that looks like on a normal working day, and note how little you have to say:

• “Draft my OKRs for next quarter.”
• “Build a gap-analysis deck for the platform migration. Use what engineering has actually said about it.”
• “Write the PRD for tap-to-pay. Pull in the decisions from the last three calls.”
• “Is another team working on something adjacent to this? I don't want to rebuild it.”
• “What did we decide about the launch date, and who pushed back?”

None of those needed a briefing. No attachments, no explaining which project you mean, no pasting last Thursday's call into the chat. That's the difference: the first draft starts most of the way there instead of at a blank page, because who was in the room, what was agreed and what has shipped since are already known.

The assistant calls the right Revo tools, gets structured data back, and answers. Everything runs as you: the same account, the same workspace, the same permissions you have in the Revo app. If you can't see something in Revo, the assistant can't see it either.

What connects to it

Anything that supports remote MCP servers over Streamable HTTP with OAuth. That includes Claude (desktop, web and Claude Code), Cursor, VS Code with GitHub Copilot, Windsurf, Zed, and a growing list of others. Section 2 has the exact steps for each.