Unstuck Engine is an MCP server — your assistant can read your signals, ICPs, audiences, leads and insights, and change configs when you ask it to. Everything it does goes through the same API as the app, under your account's permissions and plan. It always asks before changing anything.
There are two ways to connect. Pick by what your assistant supports:
| Remote server (recommended) | Local server | |
|---|---|---|
| Address | https://mcp.unstuckengine.com/mcp |
unstuck.mcpb (Claude Desktop) or npx -y @unstuckengine/cli mcp |
| Sign-in | Your Unstuck account — a browser window asks you to allow the connection | An API key (Settings → API keys) |
| Install | Nothing | Node.js 20+ (for npx), or the one-click .mcpb |
| Works in | Claude (web, Desktop, mobile), ChatGPT, Gemini CLI, Le Chat, Claude Code, Cursor, … | Claude Desktop, Claude Code, Cursor, any client that launches a command |
Steps below reflect each product's UI as of 2026-09. Labels move; the two facts that do not: the URL above, and that the first connection opens an Unstuck sign-in + consent page. Where a step is marked (verify), our own test of that client is pending — see the bottom.
Claude
Claude.ai (web) and the Claude apps. Settings → Connectors → Add
custom connector → name it Unstuck Engine, paste
https://mcp.unstuckengine.com/mcp → Add. Click Connect: a browser tab
opens on Unstuck, sign in if needed, review what the connector may access, and
allow. Back in a chat, enable the connector from the tools menu (the ⚙/+ button)
and ask, for example, "Which signals are running and what did they find this
week?". Custom connectors are available on Pro, Max, Team and Enterprise
plans; on Team/Enterprise an admin may need to enable them first.
Claude Desktop — one click. Download unstuck.mcpb from the
latest release
and open it (double-click, or Settings → Extensions → install). Paste an
API key when asked (create one in Unstuck: Settings → API keys), leave the
API URL as is, done. Requires Node.js 20+ on the machine
(Claude Desktop tells you if it is missing). The remote connector above also
works in Desktop and needs no install.
Claude Code.
claude mcp add --transport http unstuck https://mcp.unstuckengine.com/mcp
then in a session run /mcp and follow the sign-in for unstuck. Prefer a key
(CI, shared machines)? claude mcp add --transport http unstuck https://mcp.unstuckengine.com/mcp --header "Authorization: Bearer unstk_…",
or run it locally: claude mcp add unstuck -e UNSTUCK_API_KEY=unstk_… -- npx -y @unstuckengine/cli mcp.
ChatGPT (verify)
ChatGPT connects to custom MCP servers through Connectors (Settings →
Connectors; on some plans the option is under Advanced → Developer
mode). Create → name Unstuck Engine, MCP server URL
https://mcp.unstuckengine.com/mcp, authentication OAuth → Create. The
first use opens the Unstuck sign-in + consent page. In a chat, add the
connector from the tools (+) menu. Availability depends on the plan (Plus, Pro,
Team, Enterprise, Edu) and, on workspace plans, on an admin enabling connectors.
Gemini (verify)
Gemini CLI. Add to ~/.gemini/settings.json:
{ "mcpServers": { "unstuck": { "httpUrl": "https://mcp.unstuckengine.com/mcp" } } }
Start gemini, run /mcp auth unstuck and complete the sign-in. Key
alternative: add "headers": { "Authorization": "Bearer unstk_…" } instead of
signing in.
Gemini app (web/mobile). Custom remote MCP connectors are being rolled out per plan; when the Add connector / custom MCP option is present, paste the URL above and sign in the same way. Until then, use Gemini CLI.
Cursor, Windsurf, VS Code, Zed and other coding tools
Remote (sign-in) — Cursor ~/.cursor/mcp.json (or Settings → MCP → Add):
{ "mcpServers": { "unstuck": { "url": "https://mcp.unstuckengine.com/mcp" } } }
Local with a key:
{ "mcpServers": { "unstuck": { "command": "npx", "args": ["-y", "@unstuckengine/cli", "mcp"], "env": { "UNSTUCK_API_KEY": "unstk_…" } } } }
Le Chat, Perplexity, Grok and any other MCP-capable assistant
If the product lets you add a custom MCP connector / remote MCP server,
paste https://mcp.unstuckengine.com/mcp and sign in when asked. If it only
runs local servers, use the npx -y @unstuckengine/cli mcp command with an API
key. Nothing Unstuck-specific is required beyond that.
What your assistant can do
19 tools (unstuck tools lists them; the machine-readable list is
mcp-tools.json): check the connection (whoami); list
and save signal configs and run a signal now; list and save ICPs/personas;
list and save audiences, connect an audience to a destination and push it;
search leads and companies, and list who is in an audience; insights, billing summary; read and update
workspace settings; list destinations. Write tools ask for your confirmation
first, and the platform validates every change exactly as the app does.
Disconnecting
Remove the connector in your assistant's settings. To cut access on the Unstuck side: Settings → API keys — revoke the key (local server), or sign the connected app out of your Unstuck account (remote server; a token revocation page is on the roadmap). Revoking takes effect on the next call.