CallChatSyn MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@CallChatSyn MCP Server Do you have any open appointments this week, and can you book one for me?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
| No (read-only) | Answers from the business's FAQs and order data (English/Chinese); flags booking and "talk to a person" requests |
| 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 |
| Yes, creates a booking | Books one of those times and returns its |
| Yes, cancels a booking | Cancels a booking by |
Related MCP server: Main Street MCP
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):
https://callchatsyn.com/api/mcpWithout 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:
{
"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.
Available Tools
3 toolsanswer_customer_questionAnswer a customer questionAInspect
Answer a customer's message using the business's own FAQs and order data (English or Chinese). Returns intent (faq, order_status, appointment, human_handoff), the reply, and matched=false when no FAQ fit.
Inputs: message (required).
book_appointmentBook an appointmentAInspect
Book one of the open times from list_open_times. Needs the exact 'start' value, a service, and the customer's email or phone. Confirm details with the customer before calling.
Inputs: start (required), service (required), name, email, +2 more.
list_open_timesList open appointment timesBInspect
List the next open appointment times (labels in the business's time zone), plus its services and locations.
Inputs: lang.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
The three tools have distinct core purposes: answering informational queries, listing available times, and booking appointments. However, answer_customer_question returns an 'appointment' intent that might tempt an agent to use it for scheduling queries instead of list_open_times, creating a mild boundary overlap.
All tool names use snake_case and follow a verb-first pattern (answer_customer_question, list_open_times, book_appointment). The convention is consistent and predictable.
Three tools are well-scoped for a focused customer chat and appointment booking server; each tool serves a clear, non-redundant role and the set avoids bloat.
The surface covers answering FAQs/orders and booking appointments, but lacks tools for canceling or rescheduling appointments and for actually performing a human handoff. These are notable gaps for a customer service lifecycle.
Maintenance
Related MCP Connectors
Run a local business from your AI app: bookings, customers, inbox, website, posts and payments.
Verified local businesses, bookable by AI agents: services, prices, availability and appointments.
Run a service business from your AI agent: CRM, leads, scheduling, invoicing, jobs and more.
AI phone agents for service businesses: answer calls, book appointments and win back customers.
Related MCP Servers
- AlicenseAqualityBmaintenanceBook a table, an appointment or a place in a class at a real local business. Live availability, instant confirmation, no account and no API key. Eight tools: search, fetch, get_business, check_availability, create_booking, check_booking, cancel_booking and request_listing. Guest emails in eight languages. Hosted at https://g-guest.app/api/mcp810 npmMIT
- AlicenseAqualityBmaintenanceEnables small-business AI assistants to answer customer questions about hours, offerings, FAQs, staff, and booking from a single business.yaml config, with industry-specific tools and guardrails.2101 npmMIT
- AlicenseNot gradedqualityCmaintenanceTurns a local business's menu, hours, and booking rules from one JSON config into voice-callable tools, so an Alexa+ assistant can answer questions, quote and place pickup orders, check order status, and book appointments with customer confirmation. Works for restaurants, barbershops, salons, and clinics as a self-hosted Streamable HTTP server with a live owner dashboard.MIT
- AlicenseNot gradedqualityBmaintenanceEnables small local businesses to offer Alexa+ voice booking from one self-hosted, multi-business deployment with strict per-business isolation. It supports finding businesses, searching slots, two-step booking, rescheduling and cancellation with deposits, cross-session memory, bookings for people you care for, agentic waitlist recovery, notifications, and an owner dashboard.MIT