Verbit MCP connector
The Verbit connector brings Verbit transcription orders, jobs, transcripts, deliveries and insights to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so each person can place, track and read Verbit work from their AI assistant inside their own Verbit access.
- Connects with an API key
- Free 14-day trial
- No credit card
List Verbit orders still awaiting transcript delivery this week.
Working in Verbit with Elaichi
-
List all Verbit insights
-
List all Verbit orders
-
Get single Verbit order by ID
How to connect Verbit to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Verbit MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Verbit MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Verbit MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Verbit MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Verbit MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Verbit to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Verbit through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Verbit is logged.
-
Legal
Order a deposition transcript from chat
Send a recording to Verbit as a new order, add the exhibits and case notes it needs, and get the transcript back without opening another tab.
-
Media
Check where every caption job stands
Ask which Verbit jobs are still in progress, which are ready for delivery, and which orders are waiting on media before the broadcast deadline.
-
Education
Keep recurring lecture captioning on schedule
Adjust a Verbit recurrence when the class timetable changes, or cancel it at the end of term, and confirm each delivery arrived.
-
Marketing
Turn webinar recordings into transcripts
Upload the recording, create the Verbit job, and pull the finished transcript so the team can cut quotes and write the follow-up post.
-
Operations
Update a batch of orders at once
Change the status or details of many Verbit orders in one ask instead of clicking through each one, and add a backup record where a job needs it.
-
Research
Pull insights from finished transcripts
Generate Verbit insights across a set of interview transcripts and read the summary in plain language before the next round of analysis.
Try asking
- “List Verbit orders still awaiting transcript delivery this week.”
- “Summarize Verbit insights generated for last month's orders.”
- “Which Verbit recurrences are active and when do they run?”
What connecting Verbit gets you
6 screens from Elaichi, each doing one job for your Verbit account.
Ask Elaichi to work across your apps.
List Verbit orders still awaiting transcript delivery this week.
Summarize Verbit insights generated for last month's orders.
Which Verbit recurrences are active and when do they run?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Verbit orders in plain language.
Starter prompts answer from live Verbit orders, transcripts and deliveries.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Verbit.
One governed MCP endpoint for Verbit, no SDK and no shared API key.
Tool catalog
46 Verbit tools are ready to call.
Orders, transcripts, recurrences, deliveries and insights covered without custom code.
Toolboxes
Every team gets its own Verbit toolbox.
Curate one toolbox of Verbit tools per team and scope it there.
Shared connections
Teammates use Verbit without seeing credentials.
The connections table shows who connected each Verbit account and its sharing.
Audit log
Every Verbit call is on the record.
When, who, what happened, type and resource for each Verbit request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Verbit digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch orders
Verbit
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Verbit
Queued
Automations
A schedule runs your Verbit digest.
Six steps fetch Verbit orders, group them, draft a digest and await approval.
Verbit health
Refreshed 4 minutes ago · every 15 minutes · from the orders collection
Orders
1,284 ↓ 12%
Transcripts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Orders created
Last 14 days
By team
Share of activity
Production 34%
Captioning EMEA 27%
Client services 21%
Quality review 18%
Collections and dashboards
Verbit health, counted not generated.
Four metrics, 14 days of Verbit orders and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Verbit
All three can connect Verbit to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Verbit tools | Allow or restrict single Verbit tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Verbit call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Verbit tools for your AI agents
46 tools are ready to call through Elaichi's MCP endpoint the moment you connect Verbit, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Verbit to Claude?
Two steps. In Elaichi, choose Verbit and paste in your Verbit API key, since Verbit connects with a key rather than a sign-in screen, and there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Verbit is available in the conversation.
Does Verbit work with ChatGPT and Cursor as well as Claude?
Yes. Once Verbit is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Verbit once and every client you use picks it up.
What can an AI agent actually do with my Verbit data?
It can list your Verbit orders and jobs, create new ones, upload media and attach notes or exhibits, and pull back a finished transcript to read or summarize. It can also update order statuses in bulk, adjust or cancel a recurring captioning schedule, check whether a delivery arrived, and generate insights from transcripts. Verbit has a large set of actions, so short concrete asks such as "show me orders due this week" work better than long paragraphs.
Does connecting Verbit give the AI everything in my Verbit account?
No. Every request runs under the Verbit access of the person who signed in, so the AI sees only the orders, jobs and transcripts that person can already see in Verbit. Elaichi can narrow that further with restrictions on specific actions, but it can never widen it beyond what Verbit itself allows that person.
Can I stop an agent from deleting or changing things in Verbit?
Yes. In Elaichi you can restrict individual Verbit actions, such as cancelling a recurrence, updating order statuses or creating deliveries, while leaving read-only access to transcripts and job details open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Verbit connection when someone leaves?
Offboarding that person in Elaichi ends their Verbit access at once, in every client they used. If they shared a Verbit connection with a team, it keeps working for everyone else, and the API key never needs to be re-entered by anyone. If you want Verbit gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Verbit MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Verbit is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Verbit?
Yes. Both let Claude, ChatGPT or Cursor use Verbit. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Verbit call.
How is Elaichi different from Composio for Verbit?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Verbit: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Verbit in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot