For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
CommunityAPI StatusAPI PricingSign Up
DocumentationAPI ReferencesCookbookIntegrationDeveloper Tools
DocumentationAPI ReferencesCookbookIntegrationDeveloper Tools
    • MCP Server
    • Markdown & llms.txt
LogoLogo
CommunityAPI StatusAPI PricingSign Up
On this page
  • Server details
  • Connect your assistant
  • Try it
  • MCP vs. llms.txt
  • Related pages

MCP Server

||View as Markdown|
Was this page helpful?

Markdown & llms.txt

Next
Built with

The Sarvam docs expose a Model Context Protocol (MCP) server. Connect it to your AI coding assistant and the assistant can search the live documentation on demand — so the code it writes uses the right models, parameters, and endpoints instead of guessing from stale training data.

Server details

FieldValue
Server namesarvam-docs
TransportStreamable HTTP
Endpointhttps://docs.sarvam.ai/_mcp/server
ToolsearchDocs — semantic search over the documentation

Connect your assistant

1{
2 "mcpServers": {
3 "sarvam-docs": {
4 "url": "https://docs.sarvam.ai/_mcp/server"
5 }
6 }
7}

Try it

Once connected, ask your assistant something that requires current docs, for example:

“Using the Sarvam docs, write a Python script that transcribes audio.wav with the latest speech-to-text model.”

The assistant calls searchDocs, pulls the relevant page, and writes code against the current API.

Prefer zero setup? Every page has Ask AI and Open in Claude / ChatGPT / Cursor actions in the toolbar at the top — no configuration required.

MCP vs. llms.txt

The MCP server is best when you want an assistant to fetch docs on demand during a coding session. If you instead want to hand an LLM the entire documentation up front (for retrieval, fine-tuning context, or offline use), use llms.txt.

Related pages

  • llms.txt & Markdown docs
  • SDKs & Libraries
  • Errors & Troubleshooting