MCP Server

Raqi's MCP Server lets Claude (or any MCP-compatible AI) operate your workspace through chat. Read contacts and conversations, list and toggle workflows, and spin up new automations from templates — without opening a dashboard. Works with Claude.ai's custom-connector UI and Claude Code CLI.

What you can do with Claude today

With the Raqi connector installed in Claude, you can ask things like *"list my last-week contacts"* or *"turn on my Instagram comment-to-DM workflow"*. The current tool surface:

• List, search, and inspect contacts
• View conversation history with channel and lifecycle context
• List, get, toggle, publish, and archive workflows and automations
• Create new automations from pre-built templates (e.g. Comment-to-DM auto-reply) without leaving the chat
• List your AI agents
• Inspect workspace stats (contact, conversation, agent, and channel counts)

Coming next

Contact CRUD (create, update, tag), conversation status and lifecycle control, scheduled post creation, analytics queries, broadcast campaigns, and image + video generation through the Ad Studio — all driven from Claude. These are in active development.

Setup (Claude.ai)

Wire Raqi into Claude.ai in four steps:

• Open claude.ai/settings/connectors → click *Add custom connector*
• Paste https://api.raqi.io/api/mcp as the URL. Leave OAuth Client ID/Secret blank — we support dynamic client registration, so Claude.ai self-registers.
• Click Add → your browser redirects to raqi.io/oauth/consent. Log in if needed, pick the workspace to expose, click Allow.
• In any Claude chat: *"Use the raqi_ping tool"* to confirm. Then ask anything from the list above.

Setup (Claude Code CLI)

For terminal use, generate an API key on the Private API page and run:

claude mcp add raqi --transport http https://api.raqi.io/api/mcp \
  --header "Authorization: Bearer rq_live_your_key"

Permissions and revocation

Each connector asks for granular permissions on the consent screen — workspace, contacts, conversations, workflows, and more — so you approve exactly what each app can do. To revoke access, open Settings → Workspace → Developer → MCP connections and click Revoke on the connection.

Security

Access tokens are short-lived JWTs (1-hour TTL). Refresh tokens are SHA-256 hashed at rest with a 30-day lifetime. Tool calls are scoped to a single workspace via the token claim — a token for workspace A cannot touch workspace B's data even if a contact ID is guessed.

Tool name format

All tools are exposed with underscore-separated names per the MCP spec — for example raqi_contacts_list, raqi_workflows_toggle, raqi_workflow_templates_list. Reference these exact names when prompting Claude for predictable results.