Your Onvoi context, inside your AI tools
Connect once and your tool can read the client meeting, walk it back to the task it came from, pull the project context and files — then spec the work, file new tasks, save deliverables into the project, and mark things done.
One command, in any repo — or add it globally and forget about it.
$ claude mcp add --transport http onvoi https://api.onvoi.ai/api/mcp
/mcp inside Claude Code and authenticate from there.What it can do
Access mirrors your own — a connected tool never sees anything you can't see in the app.
- Meetings — summaries, decisions, and full transcripts, including live, in-progress meetings
- Tasks — with links back to the meeting or project they came from
- Projects — objectives, tasks, files, meetings, sub-projects
- Files — including live documents from the Onvoi editor
- Your second brain — vault pages and the knowledge graph
- Role textbooks
- Create, edit, and complete tasks (project progress rolls up)
- Create and organize projects
- Save deliverables as files and attach them to projects
- Dispatch your Onvoi agents
- Write to your second brain
- See anything you can't see in the app
Managing connections
Every connection appears in Settings → Connected dev tools with its last-used time. Revoking cuts access on the very next request. Access tokens expire hourly and refresh automatically while a connection is active; idle connections expire after 30 days. The connection playbook — how to walk task → meeting, when to save files back — is delivered to your tool automatically at connect time, so vague instructions still get the detailed job done.