MCP is live — OAuth, no API keys
Put everything Onvoi knows inside your AI tools.
Meetings, tasks, projects, files, your second brain — one connection and Claude Code, Cursor or any MCP client can read them, then file the work back. Or route your own app's model calls through Lasso and let your users carry the AI bill.
Fastest start
Three steps, one terminal. Works in any repo — or add it globally and forget about it.
01
Add the server
One command registers Onvoi as an MCP server in your client. Nothing to paste, no keys to store.
02
Approve in the browser
The first tool call opens the consent page. Sign in, click Approve — access mirrors exactly what you can already see.
03
Ask for the work
“Check my last meeting with the client and spec out what we discussed.” The playbook ships with the connection.
zsh — ~/your-repo
$ claude mcp add --transport http onvoi https://api.onvoi.ai/api/mcp ✓ Added MCP server "onvoi" (http)
Pick your client
Anything that speaks MCP over Streamable HTTP with OAuth 2.1 connects. These have one-paste setups.
Surface 01
Connect your AI tools
Your tool reads the client meeting, walks it back to the task, pulls the project files, specs the work, and files the results back into Onvoi. No copy-pasting transcripts ever again.
Setup guides →Surface 02
Build apps on Onvoi
Push a Claude Code project to Onvoi like you push to GitHub. It gets sign-in, a database, secrets, AI without an API key, and tools your agents can use — then share it with other teams.
Push an existing project →Surface 03
Lasso — make your app a harness
Bill model spend to your users' own Onvoi accounts instead of your API key. Switch providers freely, ride price drops, give CFOs one dashboard. ≈5-minute integration.
Explore Lasso →