Do I need to install anything?

No. Point your MCP client at https://slide.synquic.com/api/mcp and authenticate with a Slide API key. There is no package to install and nothing to run.

Can an AI assistant message my customers by accident?

No. Every tool that sends a message, launches a campaign or places a call is withheld unless you explicitly enable writes on the connection. Read tools are always available. Even with writes enabled, an automation created through the API is always created paused.

Can the MCP server do more than my API key allows?

No. Every tool call is made with your own key and passes through the same checks a normal API request does. An endpoint your key's scopes do not cover returns a 403, exactly as it would from curl.

Slide

Get started

Resource hubGuides, customer stories and playbooks BlogWhat we are learning, as we learn it Case studiesWhat real teams changed, and what it moved DocumentationSet up every integration, step by step API referenceEndpoints, payloads and examples One APIEvery channel behind a single endpoint MCP serverRun Slide from Claude, Cursor or any AI assistant How it worksThe platform in four steps EnterpriseSecurity, scale and support PartnersRefer customers and earn 25%AboutWho we are and why we build this

Book a Demo

30 min · Product walkthrough with our team

Model Context Protocol

Run Slide from your AI assistant

Connect Claude, Cursor, or any MCP client to your Slide account with a URL and an API key. Ask it who signed up this week, why an automation did not fire, or to draft a campaign, and it works against your real data. Nothing to install.

Create an API key API reference

The whole setup

https://slide.synquic.com/api/mcp
Authorization: Bearer sk_live_...

What it can reach

Sixty-two tools across the platform. Reads are available immediately; anything that sends, spends or deletes waits for you to allow it.

Contacts and notes

Search the unified contacts hub, read a contact history, and leave notes an agent can pick up later.

Messaging

Read delivery logs and templates across WhatsApp, email, SMS and RCS. Send through one unified call, with fallback between channels.

Automations

List, read and build automation flows, inspect run history step by step, and diagnose why a flow did not fire.

Voice agents

Create and configure AI voice agents, read call records and transcripts, and review call analytics.

Commerce

Answer order status and delivery questions from connected store data, and check whether a discount code is still valid.

Everything else

A generic request tool reaches any endpoint the API exposes, so new capabilities are usable the day they ship.

Connect it

claude mcp add --transport http slide https://slide.synquic.com/api/mcp \
  --header "Authorization: Bearer sk_live_..."

Writes are off by default

Sending a message, launching a campaign, placing a call and deleting anything are all withheld until you add the writes header. A read-only connection cannot reach a customer.

Your key is still the boundary

Every tool call is made with your own key and passes the same checks a normal request does. An endpoint your scopes do not cover returns 403. Connecting an assistant grants it nothing extra.

New automations start paused

An automation built through an assistant is always created paused, whatever it asked for. Going live is a separate, deliberate step a person can review first.

Questions

It is an implementation of the Model Context Protocol that exposes Slide to an AI assistant. Once connected, Claude or Cursor can read your contacts, campaigns, message logs and analytics, and, when you allow it, send messages, build automations and manage voice agents.