CallChatSyn

com.callchatsynv0.1.0更新於 Oct 6, 2026

Answer small-business customer questions from FAQs, list open appointment times, and book them.

已驗證Streamable HTTP可網頁執行Business & Commerce Productivity & Workflow

概覽

AI 產生的概覽

讓助理依據小型企業的常見問題解答回答客戶提問，並預約可用的時段。

功能: CallChatSyn 提供三個面向小型企業櫃檯的工具。answer_customer_question 依據企業的常見問題解答與訂單資料，以英文或中文回覆，並標記預約或轉接真人請求。list_open_times 依企業所在時區回傳未來七天內最多五個空閒時段，以及服務與地點資訊，資料來自 CallChatSyn 營業時間或已連接的 Cal.com。book_appointment 為其中某個時段建立預約並通知企業。
適用情境: 適合讓助理在無人介入的情況下處理小型企業的例行客戶詢問與預約。適用於已在 CallChatSyn 維護常見問題解答與營業時間，或已連接 Cal.com 進行真實預約的企業。
執行需求: 遠端 Streamable HTTP 端點，無需安裝。未提供憑證時使用公開示範企業，預約為試跑。若要為真實企業操作，需在 Authorization 標頭送出 CallChatSyn 儀表板的 Bearer 權杖，或以 npx 套件並設定 CALLCHATSYN_API_KEY 環境變數。實際使用需要 CallChatSyn 帳號並設定常見問題解答與營業時間。

安裝前請注意

Authorization 標頭或 CALLCHATSYN_API_KEY 是代表單一企業操作的密鑰，須妥善保管。book_appointment 會寫入資料：建立預約、通知企業，並可能在已連接的 Cal.com 建立預約；此操作不具冪等性，重試可能產生重複預約。回覆來自規則式常見問題比對，而非自由生成。

安裝

在 SourceWeft 中

開啟儀表板中的 CallChatSyn，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "callchatsyn": {
      "type": "http",
      "url": "https://callchatsyn.com/api/mcp"
    }
  }
}

README

CallChatSyn MCP server

Let an AI assistant (Claude, Cursor, any MCP client) answer customer questions and book appointments for a small business, using that business's own FAQs and opening hours on CallChatSyn.

Free for the first 1,000 businesses (founder offer: 100 API calls a day, 2,000 a month).

Tools

Tool	Changes data?	What it does
`answer_customer_question`	No (read-only)	Answers from the business's FAQs and order data (English/Chinese); flags booking and "talk to a person" requests
`list_open_times`	No (read-only)	Next open times (up to 5, next 7 days) in the business's time zone, plus services and locations; from CallChatSyn hours or the business's connected Cal.com
`book_appointment`	Yes, creates a booking	Books one of those times; the business is notified and, with Cal.com connected, the booking is created there. Not idempotent. Demo key = dry run

Remote server (nothing to install)

Add this URL as a custom connector (Claude: Settings → Connectors → Add custom connector; Cursor and others: a Streamable HTTP server):

Without a key it uses the demo business. To act for your own business, send the header Authorization: Bearer ccs_live_.... Also listed in the official MCP Registry as com.callchatsyn/callchatsyn.

Local setup (npx)

Create a CallChatSyn account, add FAQs and opening hours, then Dashboard → Developers → claim founder access → create an API key.
Add to your MCP client config:

json

{  "mcpServers": {    "callchatsyn": {      "command": "npx",      "args": ["-y", "github:oneappsworld/callchatsyn-mcp"],      "env": { "CALLCHATSYN_API_KEY": "ccs_live_..." }    }  }}

{  "mcpServers": {    "callchatsyn": {      "command": "npx",      "args": ["-y", "github:oneappsworld/callchatsyn-mcp"],      "env": { "CALLCHATSYN_API_KEY": "ccs_live_..." }    }  }}

Keep the key private; it acts for one business.

No key yet? Leave CALLCHATSYN_API_KEY out and the server uses the public demo key (ccs_demo_public): answers come from a demo business and bookings are dry runs, so you can try every tool before signing up.

Notes

Answers are rule-based FAQ matching (fast, predictable), not free-form generation.
API docs and OpenAPI spec: https://callchatsyn.com/developers · https://callchatsyn.com/openapi.json

MIT licensed.

來源：README.md，提交 f2c2dc0

工具

工具後設資料尚未被收錄。

版本歷史

v0.1.0最新Oct 6, 2026