Artificial Intelligence
Verbit MCP connector
The Verbit connector brings Verbit transcription orders, jobs, transcripts, deliveries and insights to Claude, ChatGPT, Cursor and any MCP client, so each person can place, track and read Verbit work from their AI assistant inside their own Verbit access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
46 tools
How to connect
How to connect Verbit to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Verbit once
-
Open Connections, choose Add connection, and pick Verbit.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Verbit API key. One person generates a token in Verbit and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Verbit to 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.
Connect Verbit to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect Verbit to 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.
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.
Use cases
What teams do with Verbit through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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?”
AI tools
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.
See it in Elaichi
What connecting Verbit gets you
6 screens from the product, each doing one job for your Verbit account.
The agent
Ask about Verbit orders in plain language.
Starter prompts answer from live Verbit orders, transcripts and deliveries.
- orders
- transcripts
- deliveries
- insights
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Verbit.
One governed MCP endpoint for Verbit, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
46 Verbit tools are ready to call.
Orders, transcripts, recurrences, deliveries and insights covered without custom code.
- List all Verbit insights
- Verbit insights generate
- List all Verbit orders
- Create a Verbit order
ElaichiToolsToolboxes
Every team gets its own Verbit toolbox.
Curate one toolbox of Verbit tools per team and scope it there.
- Production
- Captioning
- Quality
- Client services
ElaichiToolboxesShared connections
Teammates use Verbit without seeing credentials.
The connections table shows who connected each Verbit account and its sharing.
- Production
- Captioning EMEA
- Client services
- Quality review
ElaichiConnectionsAudit log
Every Verbit call is on the record.
When, who, what happened, type and resource for each Verbit request.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs your Verbit digest.
Six steps fetch Verbit orders, group them, draft a digest and await approval.
Verbit digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Verbit
Queued
Collections and dashboards
Verbit health, counted not generated.
Four metrics, 14 days of Verbit orders and a team breakdown, refreshed on schedule.
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%
FAQ
Frequently asked questions
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, 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 blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.
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 and every other client at the same time.
Put Verbit in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.