Use Releavo from your AI apps
Claude Code, Cursor, VS Code, Claude, ChatGPT or any app that speaks MCP: it works with your projects as you, builds stories in your repo and keeps Releavo current.
Claude Code, Cursor, VS Code, Claude, ChatGPT or any app that speaks MCP: it works with your projects as you, builds stories in your repo and keeps Releavo current.
Releavo is an MCP server, so any AI app that supports MCP can work in it: the coding tools your developers already use, and the chat apps the rest of the team uses. It works as you, with your roles in each project.
Releavo's address is https://releavo.app/mcp. Every app signs in the same way: it opens Releavo in your browser, you choose what it may do (Read and act, or Read only) and where (all your projects, or the ones you pick), and you Allow it.
Apps that run on your computer, and Claude, ChatGPT and VS Code for the web, connect straight away. An app on any other website (your team's n8n or LibreChat, say) shows a warning first: Releavo can't tell who runs it, so you tick that you trust that site, and Releavo emails you once it's connected. If someone sends you a sign-in link you didn't start yourself, don't allow it.
In a terminal, once (--scope user makes it work in every repository):
claude mcp add --transport http --scope user releavo https://releavo.app/mcp
Then start claude, run /mcp, pick releavo and Authenticate.
Claude Code on the web (claude.ai/code) runs in the cloud, so a server added with claude mcp add on your computer doesn't reach it. Add Releavo to Claude instead: Settings → Connectors → Add custom connector, with the address above. Claude Code on the web uses the same connector; keep it switched on in the session's connectors. A repository can also commit Releavo to its .mcp.json (claude mcp add --scope project …).
A story's Implement button checks that the Claude Code you pick is connected to Releavo, for that project, and shows you how if it isn't.
Add it to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (this one):
{ "mcpServers": { "releavo": { "url": "https://releavo.app/mcp" } } }
Cursor's MCP settings then show releavo with a button to sign in.
Add it to .vscode/mcp.json, then Start it from that file and sign in when VS Code asks. Copilot's agent mode can use it.
{ "servers": { "releavo": { "type": "http", "url": "https://releavo.app/mcp" } } }
Add a custom connector with the address:
Windsurf, Zed, Codex, Gemini CLI, Goose and the rest: add a remote MCP server (Streamable HTTP) with the address. The app needs to support MCP's sign-in (OAuth); most do.
Ask for it: "build VD-35 from Releavo". The app fetches the story with everything around it (acceptance criteria, its epic, the architecture and UX spec, comments, risks), moves it to In progress if it's yours, builds it on a branch named after it, and when it's done comments with what changed and moves it to In review.
Apps that show an MCP server's prompts list five from Releavo. In Claude Code they're commands:
/mcp__releavo__implement VD-35 builds the story, as above./mcp__releavo__review VD-35 checks this branch against the story's acceptance criteria./mcp__releavo__standup writes your stand-up from your stories and what's waiting for you./mcp__releavo__write-tests VD-35 writes test cases from the story's acceptance criteria, edge cases included, and adds them for QA./mcp__releavo__raise-change writes a change request: what the change touches in every doc and story, and the options.Not for code? Chat apps are just as useful: "what's blocked in this sprint?", "will we make the March release?", "draft a story for the export bug", "what does the interview PDF in research/ say about pricing?", "ask Releavo whether the PRD covers refunds". Docs and stories can be attached as resources where the app supports it.
| Read only | Read and act | |
|---|---|---|
| Projects, docs, stories, backlog, search | Yes | Yes |
| Uploaded files (PDF, Word, PowerPoint, spreadsheets, pictures) | Read them | Read them |
| Sprints, velocity, releases and their forecast | Yes | Yes |
| Releavo's coding sessions | See them | Start, steer and stop them |
| Stories and epics | Move, assign, plan into sprints and releases, create (as drafts) | |
| Test cases | See them | Add them; QA records pass or fail |
| Release checklist | See it | Check items off, add items |
| Docs | Propose edits, as drafts | |
| Comments and risks | Add them | |
| Ask Releavo | Yes, as in its chat |
It always has your roles, nothing more: a developer's app moves the developer's own stories, and a client stakeholder's app reads approved versions only.
It never holds your Releavo sign-in: its token only works on Releavo's MCP server.
Your account menu → Connected AI apps lists every app you've connected, what it may do, and when it was last used. Disconnect stops it at once.
Reading and updating are free. Asking Releavo and its coding sessions use the workspace's AI credits, as they do in Releavo.