Cbetamcp

What is Cbetamcp?

Cbetamcp is a Cloudflare Workers server that provides MCP tools for the CBETA Buddhist scripture database. It is a port of the Python FastAPI version of CbetaMCP to Cloudflare Workers, built for developers and researchers who need programmatic access to CBETA content.

How to use Cbetamcp?

You must deploy it yourself to Cloudflare Workers and bind a custom domain (the *.workers.dev domain cannot be used). Fork the repo, clone, run npm install, npx wrangler login, then npm run deploy. After binding a custom domain, configure your MCP client using the provided mcp-bridge.js bridge script, setting the SERVER_URL environment variable to your custom domain (e.g., https://cbeta.yourdomain.com/mcp).

Key features of Cbetamcp

• Self-hosted on Cloudflare Workers infrastructure
• Requires a custom domain – workers.dev domains are blocked in some networks
• Uses mcp-bridge.js to convert HTTP transport to stdio for MCP clients
• Offers search, catalog, and work lookup tools for CBETA scriptures
• Supports local development via localhost:8787

Use cases of Cbetamcp

• Search Buddhist texts by keyword, work title, author, or category
• Browse scripture catalogs organized by author or dynasty
• Retrieve full content and table of contents of a specific work
• Integrate CBETA data into AI assistants (Claude, Cursor, Cline, etc.)

FAQ from Cbetamcp

Why must I use a custom domain instead of workers.dev?

The Cloudflare Workers *.workers.dev domain cannot be accessed reliably in many network environments, so a custom domain bound in Cloudflare is required.

How do I configure an MCP client to use Cbetamcp?

Add a new MCP server entry with command node, args pointing to the mcp-bridge.js file, and environment variable SERVER_URL set to your custom domain (e.g., https://cbeta.yourdomain.com/mcp). Optionally set MCP_BRIDGE_PATH to the absolute path of the bridge script.

What tools does Cbetamcp provide?

It provides search tools (search_cbeta_keyword, search_cbeta_work, search_cbeta_author, search_cbeta_category), catalog tools (catalog_cbeta_sutra, catalog_cbeta_author, catalog_cbeta_dynasty), and work tools (work_cbeta_info, work_cbeta_content, work_cbeta_toc).

Can I test Cbetamcp locally before deploying?

Yes, after running npm run dev, the server listens at http://localhost:8787. In your MCP client config, set SERVER_URL to http://localhost:8787/mcp for local testing.

Where does Cbetamcp get its data?

It uses the CBETA API at https://api.cbetaonline.cn/. You do not need to manage your own database.