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.
@hiing
基本情報
概要はまだありません
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"cbeta": {
"command": "node",
"args": [
"./mcp-bridge.js"
],
"env": {
"SERVER_URL": "https://cbetamcp.hiing.net/mcp"
}
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
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.
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).
mcp-bridge.js to convert HTTP transport to stdio for MCP clientslocalhost:8787The Cloudflare Workers `*.workers.dev` domain cannot be accessed reliably in many network environments, so a custom domain bound in Cloudflare is required.
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.
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`).
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.
It uses the CBETA API at `https://api.cbetaonline.cn/`. You do not need to manage your own database.

A free remote MCP server for The Living Bread. Bible passages read word for word from a stored public domain text with an evidence label, keyword search and cross references, real churches, gatherings and prayer groups w
🚀 The fast, Pythonic way to build MCP servers and clients.

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.
Painless E2E Automation for Mobile and Web
A curated list of references for MLOps
コメント