Conversational Intelligence
Sarvam MCP connector
The Sarvam connector brings translation, transliteration, speech to text, text to speech and document reading across Indian languages into Claude, ChatGPT, Cursor and any MCP client, so your team can ask for the work in plain language and it runs inside Sarvam.
-
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.
How to connect
How to connect Sarvam to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Sarvam once
-
Open Connections, choose Add connection, and pick Sarvam.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Sarvam API key. One person generates a token in Sarvam 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 Sarvam 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 Sarvam 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 Sarvam 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 Sarvam 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 Sarvam through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Transcribe a customer call in any Indian language
Upload the recording of a Hindi, Tamil or Marathi support call and get back a transcript, or an English translation of it, ready to paste into the ticket.
-
Sales
Translate a proposal before it goes out
Take the English proposal or follow-up note and turn it into the customer's language, then check which language a reply came back in before anyone answers.
-
Marketing
Turn one campaign into ten regional versions
Translate the copy, transliterate brand and product names so they read correctly in each script, and produce spoken versions for radio or in-app audio.
-
Content
Keep names pronounced the right way
Build and update pronunciation dictionaries so every generated voice clip says place names, people and product names the way your team does.
-
Operations
Pull the details out of a scanned form
Send a batch of invoices, applications or field reports through Sarvam document intelligence and get the contents back as text you can work with.
-
HR
Publish policies in every language staff speak
Translate a handbook update into the languages your workforce reads, and create an audio version for teams who work away from a desk.
Try asking
- “Summarize this week's Sarvam speech to text jobs.”
- “List our Sarvam pronunciation dictionaries and their entries.”
- “Translate the latest support transcripts into Hindi and Tamil.”
AI tools
Sarvam tools for your AI agents
28 tools are ready to call through Elaichi's MCP endpoint the moment you connect Sarvam, 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 Sarvam gets you
6 screens from the product, each doing one job for your Sarvam account.
The agent
Ask about Sarvam jobs in plain language.
Starter prompts pull live transcriptions, translations and pronunciation dictionaries from Sarvam.
- transcriptions
- translations
- pronunciation dictionaries
- speech jobs
Ask Elaichi to work across your apps.
Summarize this week's Sarvam speech to text jobs.
List our Sarvam pronunciation dictionaries and their entries.
Translate the latest support transcripts into Hindi and Tamil.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect Sarvam from any MCP client over OAuth, no SDK, no shared API key.
Copy the endpoint
Tool catalog
28 Sarvam tools arrive ready to call.
Speech to text, translation, transliteration and pronunciation dictionaries, with no custom code.
- Create a Sarvam chat completion
- Create a Sarvam text translation
- Create a Sarvam text transliteration
- Create a Sarvam text language identification
Toolboxes
Every team gets its own Sarvam toolbox.
Curate one toolbox per team so support, localisation and research see different Sarvam tools.
- Support
- Localisation
- Content
- Research
Shared connections
Teammates use Sarvam without seeing a key.
Each Sarvam connection shows who connected it and which teams and members it reaches.
- Support India
- Localisation
- Content Studio
- Research
Audit log
Every Sarvam call is written down.
When, who, what happened, type and resource for each transcription, translation and dictionary edit.
- When
- Who
- What happened
- Type
Launching 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 turns Sarvam transcripts into a digest.
Six steps fetch transcriptions, group them, draft a digest, wait for approval, post back.
Sarvam digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch transcriptions
Sarvam
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
Sarvam
Queued
Collections and dashboards
Sarvam health arrives before anyone asks.
Four metrics, 14 days of speech jobs and a team breakdown, refreshed on schedule.
Sarvam health
Refreshed 4 minutes ago · every 15 minutes · from the transcriptions collection
Transcriptions
1,284 ↓ 12%
Translations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Transcriptions created
Last 14 days
By team
Share of activity
Support India 34%
Localisation 27%
Content Studio 21%
Research 18%
FAQ
Frequently asked questions
How do I connect Sarvam to Claude?
First connect Sarvam in Elaichi, which asks for your Sarvam API key and nothing else. 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 https://api.elaichi.ai/mcp. Sign in when Claude asks, and Sarvam translation, speech and document tools are ready to use.
Does Sarvam work with ChatGPT and Cursor as well as Claude?
Yes. Once Sarvam is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, the Elaichi Agent and any other MCP client. You connect Sarvam once and every client your team uses picks it up.
What can an AI agent actually do with Sarvam?
With Sarvam connected, an agent can translate text between Indian languages and English, transliterate names into another script, and tell you which language a message is written in. It can transcribe audio, translate speech straight into English text, and produce spoken audio from written text. It can also read scanned documents into text, and manage the pronunciation dictionaries that control how names are spoken.
Does connecting Sarvam give the AI everything in my Sarvam account?
A Sarvam connection can only do what the Sarvam API key it was created with is allowed to do, and each person still signs in to Elaichi as themselves so every request is tied to a named user. Elaichi can narrow that access further, for example to translation and transcription only, but it can never widen it beyond what Sarvam itself permits.
Can I stop an agent from deleting or changing things in Sarvam?
Yes. Restrictions in Elaichi apply per action, so you can block deleting or updating pronunciation dictionaries while leaving translation and speech to text available. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.
What happens to a Sarvam connection when someone leaves?
When you offboard someone in Elaichi, their access to Sarvam ends at once across every client they used. A shared Sarvam connection keeps working for everyone else on the team. If you want Sarvam gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Sarvam in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.