
Connects your MCP client to the Bhagavad Gita through Pipeworx's gateway infrastructure. The source doesn't list specific tools, but this is part of Pipeworx's collection of 770+ data sources accessible via their unified gateway. You can query it using the ask_pipeworx natural language interface rather than calling tools directly. Reach for this if you're building an agent that needs to reference Vedic scripture or Hindu philosophical texts. Available over streamable HTTP, so no local installation required. You can add just this server or connect to the full Pipeworx gateway for access to their entire catalog.
Bhagavad Gita MCP — Hindu scripture / Vedic text.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
list_chapters | List all 18 chapters of the Bhagavad Gita (Hindu scripture / Vedic text). Returns chapter number, Sanskrit name, transliteration, English meaning, summary, and verse count. |
get_chapter | Get one chapter of the Bhagavad Gita (Vedic scripture) by number. Returns the Sanskrit name, transliteration, English meaning, summary, and verse count. |
get_verse | Get a single verse (sloka) of the Bhagavad Gita by chapter and verse number. Returns the Sanskrit verse in Devanagari, its transliteration, and English translations from multiple commentators (Sivananda, Purohit, Gambirananda, Adidevananda) plus commentary. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"bhagavad-gita": {
"url": "https://gateway.pipeworx.io/bhagavad-gita/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/bhagavad-gita/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Bhagavad Gita data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
curl -X POST https://gateway.pipeworx.io/v1/tools/list_chapters \
-H 'Content-Type: application/json' \
-d '{}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/list_chapters. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.