MCP

ScaliQ MCP exposes the same capabilities as the REST API as tools for Cursor, Claude, ChatGPT, and other MCP clients. It is a thin 1:1 wrapper over /public/v1 for one ScaliQ workspace — no product, docs, or pricing tools.

URL

Prefer the origin URL in client config (not /mcp):

https://mcp.scaliq.ai

/mcp is a compatibility alias for the same transport.

MCP clients must send Accept: application/json, text/event-stream for the Streamable HTTP transport.

Create keys at app.scaliq.ai/api-mcp.

Which client are you using?

Client	How you authenticate
Cursor (and most IDE MCP configs)	Put `X-API-Key` in `mcp.json` headers — see below
Claude.ai / Claude Desktop / ChatGPT	OAuth — Connect Claude / ChatGPT (paste key on ScaliQ’s consent page)

Connect (Cursor)

{
  "mcpServers": {
    "scaliq": {
      "url": "https://mcp.scaliq.ai",
      "headers": {
        "X-API-Key": "sk_live_..."
      }
    }
  }
}

Put the key in MCP client headers/config — do not paste API keys into chat.

Copy accountId from Accounts in the app for search / lookup / send.

You can inspect without a key (paste https://mcp.scaliq.ai/ into an LLM) before creating a key.

Connect (Claude.ai / ChatGPT)

Short version: Add custom connector with URL https://mcp.scaliq.ai only → skip Advanced → Connect → paste your API key on the ScaliQ page.

Step-by-step (what to type in each Claude field): Connect Claude / ChatGPT.

Inspect without a key

Anyone can open the MCP URL in a browser — or paste it to an AI — and get a short overview: what ScaliQ MCP is, how to connect, and one-line tool summaries. No API key required. Full argument schemas are only available after connecting as an MCP client (initialize + tools/list).

URL	Returns
`https://mcp.scaliq.ai/`	Short overview (JSON)
`https://mcp.scaliq.ai/.well-known/mcp.json`	Same
`https://mcp.scaliq.ai/llms.txt`	Same overview as plain text
`https://mcp.scaliq.ai/health`	Liveness check

Public discovery is intentionally slim (names + one-line summaries). It does not list full JSON Schemas, REST paths, or request bodies — and it does not return private workspace data. That detail comes from a real MCP connection.

Note: site footer llms.txt is the docs index (docs.scaliq.ai/llms.txt). The MCP host overview is https://mcp.scaliq.ai/llms.txt — different hosts.

Tools ↔ REST

MCP tool	REST
`get_credits`	`GET /credits`
`list_accounts`	`GET /accounts`
`list_campaigns`	`GET /campaigns`
`get_campaign`	`GET /campaigns/:campaignId`
`start_campaign`	`POST /campaigns/:campaignId/start`
`pause_campaign`	`POST /campaigns/:campaignId/pause`
`list_leads`	`GET /campaigns/:campaignId/leads`
`get_lead`	`GET /campaigns/:campaignId/leads/:leadId`
`add_lead`	`POST /campaigns/:campaignId/leads`
`update_lead`	`PATCH /campaigns/:campaignId/leads/:leadId`
`send_message`	`POST /inbox/messages`
`lookup_profile`	`POST /linkedin/profiles/lookup`
`search_linkedin`	`POST /linkedin/search`

Cost and safety hints

Tool	Cost	Notes
Reads (`get_credits`, `list_`, `get_`)	0 credits	Marked read-only — clients may run these without prompting
`lookup_profile`, `search_linkedin`	0 credits	Read-only, but each call spends LinkedIn daily quota
`add_lead`	1 credit per successful insert	Duplicates/rejects cost 0
`update_lead`	0 credits	—
`start_campaign`	0 credits	Real LinkedIn outbound — clients should confirm
`pause_campaign`	0 credits	Stops in-progress outreach
`send_message`	0 credits	Sends a real LinkedIn DM — irreversible; clients should confirm

Auth

Action	API key
Browse catalog (`GET /`, `/llms.txt`, `/.well-known/mcp.json`)	Not needed
Claude OAuth consent	Paste key on ScaliQ page
Call tools (tenant data)	Required (header or OAuth token)

Same plan gates and rate limits as REST.

Example config

See MCP connect example for a copy-paste Cursor / ChatGPT mcp.json snippet.