Your meetings, wherever
your AI already works
ReVoice runs a standards-compliant MCP server, so Claude and other MCP clients that accept a Bearer token can query your meetings, transcripts and Company Knowledge directly - no exporting, no copy-paste, no extra tab to keep open.
Everything your AI needs to know what actually happened
list_meetings, get_transcript, get_knowledge and get_action_items cover the full loop: find the meeting, read what was said, and check what's still open. The other three round out the seven: search and fetch follow the Deep Research tool contract (ChatGPT sign-in via OAuth is not available yet), and list_spaces lists which Spaces a connection can reach. Every write - like confirming a Fortnox draft - still has to happen in ReVoice itself, with a human holding the approval.
Ask any AI, get a real answer
list_meetings, get_transcript and get_knowledge return actual, cited results pulled from your meeting history, not a guess from a stale export.
Every call re-authenticates
There's no session to hijack. Each request carries its own API key and is re-scoped to your workspace every time - tenant isolation enforced end to end.
Read-only by design
The MCP connector can list, search, and read your meetings, transcripts, and Company Knowledge - it can't write anything back. Approving a drafted action, like a Fortnox quote, always happens in an authenticated ReVoice session, never through a connected AI client.
Enterprise: bring your own MCP server too
Point ReVoice at your own internal MCP server so Matilda can pull from your company's other tools during a meeting, not only from ReVoice's own data.
Most AI notetakers only open the door one way
The usual MCP server
- Publishes an MCP server so your AI can read their meeting notes
- One direction only - meetings out, nothing else in
- A session your admin can't see re-authenticated per call
- No way to bring your own tools into the meeting itself
ReVoice MCP
- Publishes an MCP server - Claude and other MCP clients can query your meetings
- Enterprise teams can also connect their own MCP server into ReVoice
- Every call re-authenticates and re-scopes to your workspace
- Sensitive tools like knowledge search stay behind the same Gatekeeper as the rest of the product
Connected in three steps
Create an API key
Generate a scoped ReVoice API key from your account settings.
Point your MCP client at ReVoice
Add the ReVoice MCP endpoint to Claude or any MCP client that accepts a Bearer token, with your API key as the bearer token. ChatGPT sign-in (OAuth) is not available yet.
Ask about your meetings
"What did we agree with Northwind last week?" - your AI calls ReVoice's tools and answers with the real transcript behind it.
"I stopped switching tabs to check what we decided. I just ask Claude - it already has ReVoice connected."
Bring ReVoice into the AI you already use
The ReVoice MCP server is available on the Business plan. Enterprise teams can also connect their own MCP server directly into ReVoice.