Connect a client

About 5 minutesUpdated July 2026

Wire Qalyb into your AI assistant. claude.ai uses OAuth (no key to copy); header-based clients like Claude Code and Cursor use an API key.

claude.ai (no API key needed)

Add a custom connector

In claude.ai go to Settings → Connectors → Add custom connector and paste https://api.qalyb.ai/mcp.

Claude opens the Qalyb sign-in page (OAuth). Approve access — no key to copy, and every action is attributed to your user with your workspace role.

Ask away

Start a chat and ask about your tickets, agents, or analytics. Claude discovers the tools automatically.

Claude Code

Claude Code connects with an API key. Create one in the dashboard under Account → API keys (workspace admins only), then:

bash

claude mcp add --transport http qalyb https://api.qalyb.ai/mcp \
  --header "Authorization: Bearer sk-live-..."

Cursor / VS Code

json

{
  "mcpServers": {
    "qalyb": {
      "url": "https://api.qalyb.ai/mcp",
      "headers": { "Authorization": "Bearer sk-live-..." }
    }
  }
}

API keys act as workspace admin:

A key-authenticated connection has admin-level access to your workspace and no user identity — ticket actions (claim, reply, resolve) ask for an acting_member so they're attributed to a real teammate. Prefer the claude.ai OAuth flow for human-in-the-loop use.

Scope a connection

Narrow what a connection can do with URL parameters — useful for a reporting-only Claude project or a support-only connector:

text

https://api.qalyb.ai/mcp?toolsets=tickets,analytics&readonly=true

toolsets — comma list of core, agents, conversations, tickets, analytics, campaigns, knowledge
readonly=true — removes every tool that writes or deletes

Next: browse the tools & toolsets you just connected.

Was this guide helpful?

← Previous

Overview

Tools & toolsets