Dhamma.Gift — Pāli Canon MCP Server

What the code does

We read the source, 1 h ago · tools taken from the live server · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

            try { tree = JSON.parse(fsSync.readFileSync(file, 'utf8')); } catch (e) { tree = null; }

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const raw = fs.readFileSync(path.join(LEGACY_ROOT, 'assets', 'texts', page.src), 'utf8');

        translationInput.value = beforeCursor + textToInsert + afterCursor;

            require('child_process').execFileSync(process.execPath, [path.join(__dirname, 'build-icons.js')], { stdio: 'inherit' });

    <script async src="https://cse.google.com/cse.js?cx=c184c71e0fe5d4c93"></script>

    document.getElementById('clearHistoryBtn').innerHTML = translations[lang].button;

    try { names = fsSync.readdirSync(VINAYA_AUDIO_DIR).filter(n => /^[\w.+-]+\.(pli|ru|en)\.json$/.test(n)).sort(); }

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

claude mcp add pali-canon --transport http https://api.dhamma.gift/mcp

https://api.dhamma.gift/mcp

[mcp_servers.pali-canon]
url = "https://api.dhamma.gift/mcp"

{
  "mcpServers": {
    "pali-canon": {
      "url": "https://api.dhamma.gift/mcp"
    }
  }
}

{
  "servers": {
    "pali-canon": {
      "type": "http",
      "url": "https://api.dhamma.gift/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints