Public · read-only · no account

Connect Dhamma data

Dhamma data lets an AI assistant research the Pāli Tipiṭaka and Theravāda literature through passages, attributed translations, dictionaries, commentaries, sub-commentaries, parallel references, and public library material. The connection is public and read-only. No Dhamma data account, API key, or payment is required.

The remote MCP address is https://dhamma.fly.dev/mcp. Choose HTTP or Streamable HTTP when a client asks for a transport, and choose no authentication.

Open app-specific setup →

Fastest generic setup

  1. Open your assistant’s tools, connectors, or MCP settings.
  2. Add a remote server named “Dhamma Data” with URL https://dhamma.fly.dev/mcp.
  3. Select HTTP or Streamable HTTP and No Auth if those choices appear.
  4. Save or connect it, then start a new conversation and enable Dhamma Data from the available tools.
  5. Ask the assistant to list Dhamma Data tools before beginning research.
{
  "mcpServers": {
    "dhamma_data": {
      "type": "http",
      "url": "https://dhamma.fly.dev/mcp"
    }
  }
}

Command-line clients

Run the appropriate command once, then restart or refresh the client if it was already open.

# Codex
codex mcp add dhamma-data --url https://dhamma.fly.dev/mcp

# Claude Code
claude mcp add --transport http --scope user dhamma-data https://dhamma.fly.dev/mcp

ChatGPT and Claude

In ChatGPT, create an app or custom MCP connection named “Dhamma Data”, paste the MCP address, select No Auth, connect it, then enable Dhamma Data in a new normal chat. Availability can depend on account and workspace policy.

In Claude, open Customize → Connectors, add a custom connector named “Dhamma Data”, paste the remote MCP address, leave OAuth fields empty, and enable the connector in a new chat. Managed organizations may require administrator approval.

What to ask first

A useful first request is: “Find passages concerning sati in the early discourses and their commentaries. Keep primary text and commentary separate, quote sparingly, and link every passage.”

If the tools do not appear

Ask the client to refresh or list its tools. Confirm that the server is enabled and that the URL ends in /mcp. If a managed workspace blocks custom tools, its administrator must allow the connection.

The developer page documents the REST alternative, transport, response bounds, provenance, and source-attribution rules.