---
name: synquil
description: Set up Synquil for a user — sync their business data (Google Sheets, Notion, HubSpot, Airtable, Stripe, a database, a CSV, etc.) into a queryable database, then connect it to this AI session via MCP. Use this when a user asks to connect their business data, set up Synquil, or wants their AI assistant to answer questions from their real business tools.
---

# Synquil setup skill

Synquil syncs a user's business data into one unified, queryable database and exposes it through an MCP server, so you (the AI) can query it directly instead of relying on stale exports or pasted spreadsheets.

There are exactly **two steps a human must do themselves** — they're security boundaries, not gaps in this skill, so don't try to script around them. Everything else, you can drive.

## Step 1 (human-required): create an account

Send the user to **https://synquil.com/sign-up**. Clerk (their auth provider) requires email verification — there's no way to create or verify an account on someone's behalf. This is a one-time, ~30-second step.

## Step 2 (human-required, once): connect this AI to Synquil

The MCP server URL is **`https://mcp.synquil.com/mcp`** (the bare origin `https://mcp.synquil.com` also works). OAuth, no API key.

**If you're claude.ai, the Claude desktop app, or Cowork:**

1. Tell the user: **Customize → Connectors → + → Add custom connector**, paste `https://mcp.synquil.com/mcp`, click Add. (Team/Enterprise: an org owner adds it under Organization settings → Connectors first, then members authenticate from Customize → Connectors.) Connectors added here sync across web, desktop, and mobile automatically. ChatGPT: same URL as a connector (requires Pro/Team/Enterprise).
2. A consent screen appears listing permissions: "Read all your synced business data" and "Connect data sources, manage schemas, and trigger syncs." **Both are checked by default — tell the user to leave both checked** so you can do the rest of setup yourself. They click "Allow" once.

**If you're Claude Code:** you can register the server yourself — run:

```bash
claude mcp add --transport http --scope user synquil https://mcp.synquil.com/mcp
```

(`--scope user` makes it available in every project; drop it to scope to the current project only.) Then have the user run `/mcp` in an interactive session, pick **synquil → Authenticate**, and approve both permissions in the browser. New sessions from then on have the Synquil tools loaded.

Note: the claude.ai connector registry and Claude Code's MCP config are **separate systems** — connecting in one does not make Synquil appear in the other. A user who works in both should connect both (two quick OAuth approvals against the same Synquil account).

**If you're Cursor, Windsurf, VS Code/Copilot, Cline, or another API-key-based client:** those connections are read-only by design today. You can query data once connected, but you can't run the autonomous setup in Step 3 below — direct the user to steps 3 of the dashboard guide manually instead, or have them connect via Claude/ChatGPT for setup, then switch to their preferred tool afterward.

## Step 3 (you, autonomous from here)

Once connected with both permissions, call `setup_guide` for the live, authoritative step list. In short:

1. **Connect a source.**
   - Database or CSV: call `connect_database` (Postgres/MySQL connection string) or `connect_csv` (raw file contents) directly. No browser step.
   - Everything else (Google Sheets, Notion, HubSpot, Airtable, Stripe, Shopify, QuickBooks, Linear, GitHub, Pipedrive, Jira, Zendesk): call `get_oauth_url` and have the user open the returned link to approve that app's own OAuth login. This one click per data source can't be skipped — it's the data source's own security boundary, not Synquil's.
2. Call `list_connection_items` to see what's available, then `set_active_items` to pick what to sync.
3. Call `trigger_schema_draft`, then poll `get_schema_status` until a proposal is ready (30–60 seconds).
4. Call `apply_schema` to load the data.
5. Use `list_tables`, `describe_schema`, and `query_data` to confirm it worked and start answering the user's actual question.

If anything errors, call `troubleshoot` with the error message before guessing at a fix.

## Summary for the impatient

Sign up (human) → add the MCP connector and approve both permissions (human, one click) → call `setup_guide` and drive the rest yourself, including connecting non-OAuth sources with zero further clicks.