Skip to main content
Glama
CallChatSyn MCP Server

CallChatSyn MCP Server

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 and returns its id; the business is notified and, with Cal.com connected, the booking is created there. Not idempotent. Demo key = dry run

cancel_appointment

Yes, cancels a booking

Cancels a booking by id (also in Cal.com if connected). To reschedule: cancel, then book a new time. Demo key = dry run

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/mcp

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)

  1. Create a CallChatSyn account, add FAQs and opening hours, then Dashboard → Developers → claim founder access → create an API key.

  2. 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

MIT licensed.

Available Tools

3 tools
answer_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

    A3.7/5.0

    Scored across 3 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Book 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/mcp
      8
      10 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      2
      101 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Turns 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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