The Qalyb MCP server

About 4 minutesUpdated July 2026

Connect Qalyb to Claude, Cursor, or any MCP client and run your whole workspace by asking — build agents, answer tickets, launch campaigns, and pull analytics without touching the dashboard.

The Model Context Protocol (MCP) is how AI assistants connect to external products. Qalyb ships a native MCP server that exposes your workspace as a set of typed tools — list_tickets, create_agent, get_analytics_overview, search_transcripts, and dozens more — so instead of clicking through screens you just say what you want:

  • "Any urgent tickets? Assign the WhatsApp ones to Sara and tell the customers we're on it."
  • "How did the Riyadh campaign do this week vs last? Retry the failed calls."
  • "Create a bookings agent for the clinic, feed it our FAQ page, and pause the old one."

The server lives at a single connector link, https://api.qalyb.ai/mcp — everything an org member or admin manages: agents, conversations, tickets, analytics, campaigns, knowledge bases, and the UI components your agents render in chat.

Next step:
Head to Connect a client to wire up Claude, Cursor, or claude.ai in a couple of minutes.

What you can do

The server groups its tools into toolsets you can enable per connection: agents, conversations, tickets, analytics, campaigns, knowledge, components, and core. See the full tools & toolsets reference. Prefer code? The same operations are available over the REST API.

Was this guide helpful?