Zapier, Make and n8n
Give an AI agent in Zapier, Make or n8n read-only access to your meetings through VoiceCap's AI connector.
Zapier, Make and n8n can each connect an AI agent to a remote MCP server. Point that step at
VoiceCap's AI connector, https://voicecap.ai/api/mcp, and while a workflow runs the agent can
search your meetings and read their summaries, decisions, action items and transcripts. It's the
same connector, login and consent screen that Claude and ChatGPT use.
This page covers the AI connector, which you use when an AI agent step in a workflow needs to read your meetings. That workflow starts from whatever trigger you pick on the platform, such as a schedule or a form submission, and the agent asks VoiceCap from there.
Before you start
AI connectors are on for every organization by default. An Owner or Admin can turn them off for the whole organization at Settings > Integrations. While they're off, you can still sign in and click Allow access, but every VoiceCap step fails with "MCP access disabled by your organization admin."
You don't need an API key or a token from VoiceCap. Each platform signs you in to VoiceCap and shows VoiceCap's consent screen, where you click Allow access. Under "Approving sends the connection to", the consent screen shows the address the connection goes to. It should be the platform you're connecting, or your own n8n address. If it isn't, click Deny.
Connecting from Zapier
Zapier connects to VoiceCap through its MCP Client integration, which Zapier marks as beta.
- In Zapier, go to the Apps page and click + Add connection.
- Search for and select MCP Client, then click Add connection.
- On the Connect an Account page, enter
https://voicecap.ai/api/mcpas the Server URL, set Transport to Streamable HTTP and OAuth to Yes. Leave Bearer Token empty. - Click Yes, Continue to MCP Client.
- In the tab that opens, log in to VoiceCap if you're not already logged in, and click Allow access on the consent screen.
- Rename the connection in Zapier to something like "VoiceCap", so you can tell it apart from other MCP servers later.
VoiceCap's tools are then available through MCP Client's Run Tool action and its Run Read-Only Tool search, in a Zap or in Zapier Agents. Every VoiceCap tool is read-only, so either one works.
Connecting from Make
Make connects to VoiceCap through its MCP Client app, which Make marks as open beta.
- Open your agent in Make AI Agent (New) and click Add MCP, or add an MCP Client module to a scenario.
- Click Create a connection.
- In the MCP Server field, click + New MCP Server and enter
https://voicecap.ai/api/mcpin the URL field. Leave API Key / Access token empty. - Click Save.
- When prompted, log in to VoiceCap and click Allow access on the consent screen.
In an agent, VoiceCap appears on the canvas as an MCP Client > MCP Tools module. In a scenario, the Execute an action with AI module lets the AI choose which VoiceCap tools to call for a task you describe, and Call a tool runs one tool with the arguments you map.
Connecting from n8n
n8n connects an agent to VoiceCap with the MCP Client Tool node, attached to an AI Agent node as one of its tools.
- In your workflow, add a tool to the AI Agent node and choose MCP Client Tool.
- Enter
https://voicecap.ai/api/mcpas the endpoint. If the node asks for a transport, choose the streamable HTTP option. - Under Authentication, choose the OAuth2 option and create a new credential. Leave Use Dynamic Client Registration on. There is no client ID or client secret to paste.
- Connect your account from the credential, log in to VoiceCap, and click Allow access on the consent screen.
- Under Tools to Include, keep All, or pick only the VoiceCap tools this agent needs.
If you host n8n yourself, the OAuth Redirect URL shown in the n8n credential must start with
https:// or point at localhost, or the VoiceCap sign-in won't finish. The consent screen shows
that same address. If it isn't the address you open n8n at, fix n8n's public URL setting before
you approve.
What the agent can and can't do
The connector is read-only. An agent can search and read meetings, but it can't create, edit or delete anything in VoiceCap. The tools it gets are the ones listed under What the tools do.
The agent sees exactly the meetings that the person who signed in can open in VoiceCap, and nothing more. The connection keeps that person's access, so anyone who can run or edit a workflow using it in your Zapier, Make or n8n account, or anyone the connection is shared with, reads meetings as that person. Connect with your own VoiceCap login only where you're comfortable sharing what you can see.
Meeting text can contain wording aimed at an AI. A transcript is what people said, and anyone in the room can say something that reads like a command to the agent. If the same agent can also send email, post messages or update records, give it only the tools it needs, and review what it prepared before you send it.
Transcripts are in the language the meeting was held in. An agent that searches only in English can miss a meeting held in another language, such as Lithuanian, so tell it to search in the meeting's language too.
Tool calls are rate-limited per user: 60 a minute and 2,000 a day, shared across every AI client you've connected, Claude and ChatGPT included. A workflow that runs every few minutes can use the day's quota on its own, so schedule it no more often than you need. Tool calls don't use transcription minutes.
Disconnecting
The platform appears in Settings > Profile under "Connected AI clients", by the name it gave itself when it connected. Each connection you create on the platform is its own entry, so the same name can show up more than once. Click Disconnect on the ones you no longer use. Workflows that use a disconnected connection stop working on their next VoiceCap call, and you have to sign in and approve access again to reconnect.
If a workflow's VoiceCap step starts failing with a sign-in or authorization error, reconnect the connection on the platform. You can then disconnect the old entry under "Connected AI clients".
An Owner or Admin can also click Disconnect all members to cut off every member's AI clients at once, or turn AI connectors off for the whole organization, from Settings > Integrations.