On this page
Connect Claude (and ChatGPT)
Use this page when connecting Claude.ai, Claude Desktop, or ChatGPT to ScaliQ MCP.
These apps use OAuth. Prefer Sign in with ScaliQ — you should not need to create or paste an API key for Claude/ChatGPT.
Before you start
- Use a paid ScaliQ workspace — free/trial cannot mint API access.
- Use MCP URL
https://mcp.scaliq.ai.
What to type in Claude
In Customize → Connectors → Add custom connector:
| Field | What to enter |
|---|---|
| Name | ScaliQ (any label is fine) |
| Remote MCP server URL | https://mcp.scaliq.ai |
| Advanced → OAuth Client ID | Leave blank — skip Advanced |
| Advanced → OAuth Client Secret | Leave blank — skip Advanced |
Then click Add, then Connect.
After Connect (preferred)
Your browser opens ScaliQ at /mcp-authorize.
- Click Sign in with ScaliQ and complete sign-in.
- Review Allow access? — confirm the assistant name and redirect host look right, then click Allow. Click Deny if you did not start this connect.
- We mint or rotate a workspace key named
MCP OAuthand finish OAuth (secret never appears in the page URL). - You’re redirected back to Claude — the connector is ready.
Only click Allow if you started Connect from your AI assistant. Deny never mints a key.
You do not paste a key into Claude’s Advanced settings. The secret never appears in the page URL.
Team note
Reconnecting rotates the shared MCP OAuth key for the workspace. Other teammates’ Claude connectors that still hold the old secret will need to reconnect. Cursor/mcp.json keys are separate — leave them alone.
Paste-key fallback (temporary)
If sign-in is unavailable, use paste fallback: either ?consent=paste on /authorize, or the Paste API key link on /mcp-authorize (opens MCP GET /oauth/paste). Paste a key from app.scaliq.ai/api-mcp. Prefer Sign in when it works; paste will be removed in a later release. Cursor users should keep using /api-mcp keys (see below).
Do not do this
| Don’t put this… | …in this Claude field |
|---|---|
Your API key (sk_live_…) | OAuth Client ID or Secret |
The text X-API-Key | OAuth Client ID |
Authorization or Bearer … | OAuth Client ID |
The MCP OAuth key | Cursor mcp.json |
Those Advanced fields are for a rare pre-registered OAuth app identity. They are not ScaliQ request headers. Filling them with a key breaks the connection.
Cursor users
Cursor does not use this OAuth / Sign-in flow. Create a separate API key on API & MCP (any name other than MCP OAuth) and use the mcp.json snippet on MCP with headers.X-API-Key.
Never put the OAuth-minted MCP OAuth key in mcp.json — reconnecting Claude rotates it and would break Cursor.
First campaign (one prompt)
After connect, you can ask Claude to fetch Agent setup and start your first campaign. If no LinkedIn is connected yet, it will give you a connect link and stop until you finish LinkedIn login in the browser.
Troubleshooting
| Symptom | Fix |
|---|---|
Page shows JSON “Not found” at /authorize | Wrong MCP URL, or OAuth not available yet — retry with https://mcp.scaliq.ai |
| Claude asks for Client ID | Leave Advanced empty and Connect again |
| Sign-in says plan required | Upgrade to a paid plan, then Connect again |
| Connect link expired / invalid | Close the window and Connect again from Claude |
| Consent paste rejects the key | Create a fresh key on /api-mcp; use sk_live_ with prod MCP URL |
| Tools fail after connect | Confirm the connector is enabled in the chat (“+” → Connectors) |