Get started
AI assistant (MCP)
The same assistant that lives in the corner of the Gelee app, inside the tools you already use. Connect once and run your workspace by talking: build and edit campaigns, add leads, check messaging, tune the AI SDR, manage seats and teammates, and approve waiting reply drafts.
https://web.gelee.ai/api/v1/mcpStreamable HTTPSign in with Gelee (OAuth) or Bearer keyConnect it
| Client | How |
|---|---|
| Claude (web or desktop) | Settings, Connectors, Add custom connector. Name it Gelee, paste the server address, click Connect and sign in with your Gelee email and password. Pick the workspace and whether it may make changes. |
| ChatGPT | Settings, Connectors, Create. Paste the server address, choose OAuth, sign in with your Gelee login. |
| Claude Code | Make a Read + write key in the app, then run the command below. |
| Cursor and scripts | Streamable HTTP with an Authorization: Bearer gk_… header. |
claude mcp add --transport http gelee https://web.gelee.ai/api/v1/mcp \
--header "Authorization: Bearer gk_your_key"Sign-in uses OAuth 2.1 with dynamic client registration and PKCE; discovery documents are under /.well-known/.
What it can do
It reads the workspace (overview, campaigns, leads, inbox and waiting drafts, performance, AI SDR settings, seats and the team) and proposes changes in groups: campaigns, leads, messaging, sdr, inbox and workspace, plus reading tools that are always on. A key-based connection can load fewer by adding ?toolsets=campaigns,leads to the address.
Every tool is also callable over plain REST at POST /tools/{name}, for code that does not speak MCP.
What it will and will not do
Nothing is saved or sent until you say yes. Launching a campaign and approving a reply are real LinkedIn actions that cannot be undone, and the assistant says so first. Sending a message needs a key or login that is allowed to send.
It never quotes prices. Anything a lead wrote is treated as data, never as instructions, so a message saying "ignore your rules" does nothing.