MCP server

Connect Claude or ChatGPT to your VoiceCap meeting archive over MCP, read-only and filtered by what you can already see.

VoiceCap runs a remote MCP server at https://voicecap.ai/api/mcp. Connect it to Claude or ChatGPT to ask questions about your meetings from inside those apps instead of the VoiceCap dashboard. AI connectors are on for every organization by default; an Owner or Admin can turn them off for the whole organization at Settings > Integrations, and while they're off, every tool call fails with "MCP access disabled by your organization admin."

What it is

The server is read-only. It has no tool that creates, edits or deletes anything in VoiceCap. Every result is filtered by the same rule the VoiceCap app itself uses: you see over MCP exactly what you'd see logged in, based on your role, your groups, and any meetings shared with you directly. Nothing more. An empty result means you can't see that meeting, not that it doesn't exist.

Recordings are transcribed Lithuanian-first, so a Claude or ChatGPT search that comes back thin is worth retrying with Lithuanian terms as well as English ones.

Connecting from Claude

AI connectors are on by default, so anyone in your organization can connect a client without waiting on an admin. An Owner or Admin can see who's connected, and turn AI connectors off entirely, from Settings > Integrations.

On a Claude Team or Enterprise plan, have your workspace admin add the connector once, for everyone:

In Claude's workspace settings, add a custom connector with the URL https://voicecap.ai/api/mcp.
Each member still connects individually the first time they use a VoiceCap tool: Claude sends them to log in to VoiceCap and approve access on VoiceCap's own consent screen.

One connector added once, and access still follows each person's own VoiceCap login and permissions.

On Claude Pro or Max, add the same URL yourself from your own connector settings.

Either way, the first time you use a VoiceCap tool, Claude opens VoiceCap's login page if you're not already signed in, then shows a consent screen: "[client name] wants access to your meetings." It states what the client will be able to read (meetings, transcripts, decisions and action items you can see) and what it can't do (change or delete anything, or see meetings you don't already have access to). Click Allow access to finish, or Deny to stop here.

Connecting from ChatGPT

Add the same URL, https://voicecap.ai/api/mcp, as a custom connector in ChatGPT. The org-level toggle above applies here too: if an Owner or Admin turns AI connectors off, ChatGPT stops on its next tool call the same as Claude.

Outside developer mode, ChatGPT's deep research calls exactly two tools by name, search and fetch. VoiceCap's server ships that pair, so deep research works against your archive without switching ChatGPT into developer mode.

What the tools do

Tool	What it does
`search_meetings`	Finds moments across every meeting you can access. Searches transcript text, summaries, decisions and titles together, and returns short excerpts.
`list_meetings`	Lists which meetings exist, with title, date and length, without any of what was said in them.
`get_meeting`	Returns one meeting's full record: the summary, key topics, decisions, action items and participants.
`get_transcript_section`	Reads the exact words spoken in one window of a meeting, up to 15 minutes at a time, with speaker names and timestamps.
`list_decisions`	Lists decisions recorded across your meetings, each with the context it was made in.
`list_action_items`	Lists action items across your meetings, with owner and completion state.

Every result carries a link back to the meeting in VoiceCap. A result tied to a moment, like a search hit or an action item, links straight to that point in the recording instead of only the meeting page.

search_meetings and list_meetings only cover meetings that belong to your own organization: a meeting shared with you directly from someone else's organization won't show up in a search or a list, but you can still open it with get_meeting if you already know it exists.

Managing access

At Settings > Profile, the "Connected AI clients" card lists every AI client that currently has access to your account, when you approved it and when it last connected. Click Disconnect to cut one off. Access stops immediately: every token it holds is deleted, not merely expired. To use that client again, you reconnect and approve access from scratch.

An Owner or Admin can also disconnect every member's AI clients at once, or turn AI connectors off for the whole organization, from Settings > Integrations. Turning connectors off stops all of them on their next tool call while keeping each member's individual connection in place, so switching back on restores access without anyone reconnecting.