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. Anything you can click in the app works here too: campaigns, leads, replies, LinkedIn accounts, the calendar and integrations, settings, reports and LinkedIn posts.
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/.
Your first campaign
New to Gelee? Say so. The assistant calls get_started, which tells it what is already set up (a LinkedIn account, who you sell to, your booking link, what the AI SDR knows, whether replies are on, a first campaign) and what to do next. Then it sets a campaign up the way the app does, one question at a time:
| Step | What happens |
|---|---|
| Who | Who you sell to: titles, places, industries, company sizes. It starts from the ideal customer you saved, or from what you type. |
| How to find them | Find people by search, watch LinkedIn accounts or topics, or upload a list. |
| Check the people | It shows the first page the search would reach (campaign_check_people), marks anyone already in a campaign, messaged before or blacklisted, and asks if they look right. Say which ones are wrong and it suggests a title to skip. |
| Goal | What a yes should lead to: book a call, visit a page or fill a form, plus anything the AI SDR must never say for this campaign. |
| Messages | An invite note and two or three short messages. It can start from a template, from the messages that got you the most replies (performance best_copy), or write new ones. |
| InMail, senders, timing | Only if a seat has InMail; which accounts send; days and hours in your time zone; how long an unanswered invite waits. |
| Review and launch | It reads the whole thing back, and launches only after you say yes. Everything can be changed later. |
What it can do
Anything you can click in the Gelee app. Every button has a tool, and a test in our code fails if a new one ships without one. A few things stay in the app on purpose: billing, making API keys, uploading files from your computer, and pasting a CRM or calendar key (the assistant gives you the link to that card instead).
| Group | What it covers |
|---|---|
| Always on | The set-up checklist (get_started), overview, campaigns, leads, inbox, performance (including your best past messages), AI SDR settings, where things are in the app, your plan, the change history, and request_feature. |
| campaigns | Create, edit (copy, waits, A/B variants, InMail, seats, schedule, the reply goal, invite timeout), filter, launch and pause campaigns, templates, and a campaign's LinkedIn search. |
| leads | Add people, CSV or Google Sheet uploads, LinkedIn search, check who a campaign's search would reach before adding anyone, Watch LinkedIn accounts and Watch topics, outcomes, fields and tags, the blacklist. |
| messaging | Check, preview and write copy, A/B variants, and AI variables for one campaign or the whole workspace. |
| sdr | How the AI SDR replies: mode, knowledge base, objections, follow-ups, test replies. |
| inbox | Read and send in conversations, approve, skip or rewrite reply drafts, have the AI SDR write a reply, follow-up suggestions, insight reports, starred replies. |
| workspace | Connect LinkedIn accounts (a login link, or the account's cookie), reconnect, disconnect, seat limits and warm-up, past seats, the team. |
| health | A campaign's Health and Activity tabs: lead health checks, search and topic runs, watched posts, account vetting, swapping tapped-out accounts, enrichment, intake URL, send order, delete. |
| integrations | The calendar and integrations: what is connected, their settings, test, sync and backfill, disconnect, and the link to connect one. |
| settings | Time zone, ICP, intent keywords, insight reports, each seat's persona and voice, what the AI SDR learned, message templates, saved filter sets. |
| reports | Conversions, qualified calls, the weekly recap, autopilot log, message performance, your posts, one seat's activity, invitations, monthly reports. |
| content | LinkedIn posts: the schedule, posts written in a seat's voice, bulk posts, publishing now, review comments, photos, carousels and images. |
Claude and ChatGPT see the everyday groups and reach the rest through more_tools and use_tool, which keeps the tool list short. A key-based connection can load exactly the groups it wants by adding ?toolsets=campaigns,leads,content to the address; calling a tool from a group that is not loaded answers with the group to add, and a made-up argument answers with the ones the tool accepts.
Every tool is also callable over plain REST at POST /tools/{name}, for code that does not speak MCP.
Connecting LinkedIn accounts
Ask the assistant to connect an account and it returns a Gelee login link (seat_connect); log in there with your password or your cookie. If you already have the account's li_at cookie, it can connect with that directly (seat_connect_cookie), and finish LinkedIn's code check if one comes up (seat_connect_code). The cookie is your LinkedIn login and stays in your chat history, so the link is the safer way. Gelee never stores or logs it. New accounts start warming up on their own.
Asking for something Gelee does not do
When you ask for something no tool can do, the assistant says so and offers to send it to us with request_feature. Our team reads every one. If it turns out Gelee already does it, the answer tells you where.
What it will and will not do
Small edits (a setting, a field, a tag) save right away and can be undone. Anything that sends, spends, launches, publishes, deletes or cannot be undone shows you a preview first and waits for your yes, and the assistant says when there is no undo. 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.