For AI agents · 13 assistants
Connect your AI agent to your LinkedIn pipeline.
Paste one address, approve Embers once, and ask for today's queue. No API key. It cannot act on LinkedIn, and it cannot start a scan.
Server address
Solo and above · OAuth, no API key · revoke any time
Setup
Pick your assistant. Copy one thing.
Every assistant uses the same address. The copy is the whole setup; approval happens in your browser.
Claude Code takes one command. Claude Desktop and claude.ai use Settings, then Connectors.
Claude Code
Desktop and web
Same address for Claude Code, Claude Desktop, and claude.ai.
- In a terminal, run the Claude Code command below. It adds Embers and opens the browser.
- Or open Settings, then Connectors, then Add custom connector, and paste the server address. Leave the OAuth Client ID and Client Secret under Advanced settings blank: Claude registers itself. There is no API key.
- On the approval screen, check the address, then choose Allow access.
Add a remote server in Cursor Settings, then Tools and MCP, and click Connect.
Config
Cursor starts the OAuth flow when you click Connect.
- Open Cursor Settings, then Tools and MCP, then Add Custom MCP. Or edit ~/.cursor/mcp.json.
- Paste the config below. The url is the only field you need.
- Click Connect and approve Embers in the browser.
Add the remote server with the Codex CLI, then log in so the browser can approve Embers.
Command
After the add command, run: codex mcp login embers
- Run the command below to add Embers as a streamable HTTP server.
- Run codex mcp login embers and approve Embers in the browser.
Add a remote HTTP server in mcp.json, or run MCP: Add Server from the Command Palette.
Config
VS Code uses a servers block, not mcpServers.
- Open the Command Palette and run MCP: Add Server, or create an mcp.json in your profile or .vscode folder.
- Set type to http and url to the server address, as in the config below.
- Start the server and approve Embers when the browser opens.
Turn on Developer mode, add Embers as a remote MCP app with OAuth, and approve it in the browser.
Server address
Custom MCP apps in ChatGPT need Developer mode turned on.
- On the web, turn on Developer mode in Settings. It is available on Plus, Pro, Business, Enterprise, and Education. A workspace admin may need to allow it first.
- Create an app for a remote MCP server, paste the server address, and choose OAuth. There is no API key.
- Approve Embers in the browser, then pick Embers from the Developer mode tools in a chat.
Add a remote server with serverUrl, then authenticate from Agent settings.
Config
Servers that support dynamic client registration need no client id.
- Open Agent settings, then Customizations, or edit mcp_config.json.
- Add a remote server with serverUrl set to the address. Antigravity uses serverUrl, not url.
- Click Authenticate and approve Embers in the browser.
Add a personal connector for a custom MCP server, choose OAuth, and approve Embers in the browser.
Server address
Lovable uses the same remote address and the browser approval.
- Open Settings, then Connectors, and under Personal connectors add a new MCP server.
- Paste the server address and choose OAuth. There is no API key.
- Approve Embers in the browser.
Add a custom MCP server from the Integrations pane and approve Embers in the browser.
Server address
Use the remote URL. Do not paste an API key.
- Open the Integrations pane and add a custom MCP server.
- Paste the server address. Replit starts OAuth when the server supports dynamic client registration.
- Approve Embers in the browser.
Add a URL server under Settings, then Agents, then MCP servers, and approve Embers in the browser.
Config
Browser sign-in works in the Warp app. Warp cloud agents do not support OAuth servers yet.
- Open Settings, then Agents, then MCP servers, and click Add.
- Paste the config below. Leave out the headers block: there is no API key.
- Approve Embers when the browser opens.
Add a custom remote server under context_servers, then approve Embers in the browser.
Add a remote server in opencode.json, then approve Embers in the browser.
Config
Type remote, plus the address, is the whole config.
- Open opencode.json in your project or user config.
- Add Embers as a remote server with the address below.
- Approve Embers in the browser when OpenCode connects.
Add Embers with hermes mcp add and auth set to OAuth, then approve it in the browser.
Command
Use OAuth. There is no API key to store in the config.
- Run the command below. It adds Embers as a remote HTTP server with OAuth, not a bearer token.
- On first connect, or with hermes mcp login embers, a browser window opens. Approve Embers.
- On your own machine, Hermes listens on localhost for the callback. On a remote host, forward that port over SSH first.
Add a custom connector at grok.com/connectors, paste the address, and approve Embers in the browser.
Server address
Grok uses the same hosted address as every other client on this page.
- Go to grok.com/connectors, click New Connector, then Custom.
- Paste the server address. There is no API key.
- Approve Embers in the browser.
What your assistant can do with Embers
- Read today's ranked queue, and why each lead surfaced
- Search leads with the same filters as the app
- Open a lead: score, engagement, notes, status
- Draft an opener, saved for you to send
- Update statuses, follow-ups, and outcomes
- Preview an ICP change before anything is saved
- Change your ICP or block a company, after asking
- Push leads to a tool you connected, after asking
Then just ask
One sentence, real work back.
Your assistant picks the right Embers tool, reads your queue or updates the lead, and replies in the chat. No dashboard, no export step, and nothing sent on LinkedIn.
- “What should I work on today?”
- “Draft an opener for Nicolas Cole and save it on the lead.”
- “Mark Ben Shafii contacted and set a follow-up for Tuesday.”
What should I work on today?
today_queue
Nicolas ColePosted about declining LinkedIn reach94%
Oskar KwasniewskiPosted a recent founder lesson88%
Ben ShafiiShared a recent product launch update81%
Draft an opener for Nicolas Cole and save it on the lead.
get_lead write_opener Hi Nicolas, your post on declining LinkedIn reach matched what we hear from founders every week.
Saved as a draft on his lead. Nothing was sent.
Mark Ben Shafii contacted and set a follow-up for Tuesday.
search_leads update_lead_status Push the two above 85% to HubSpot.
today_queue push_leads Push 2 leads to HubSpot?
Nicolas Cole and Oskar Kwasniewski, to the HubSpot an administrator connected.
Illustrative examples from verified public profiles. No affiliation implied.
12 tools
Twelve actions, and nothing outside them.
Read tools change nothing. Write tools save one lead. The three that reach further, editing your ICP, blocking a company, and pushing leads, tell you what would happen and wait for you.
- Drafts are saved for you to send yourself
- No action starts a scan
- Every action is logged for 90 days
Read6
Write3
Asks first3
today_queue The ranked list of leads that need action, with the reason each one surfaced.
Security and data
Connects to your account, touches nothing else.
-
OAuth, no API key
You approve Embers in the browser. Embers issues the credentials. There is no key to copy or store.
-
Asks before bulk changes
Editing your ICP, blocking a company, or pushing leads tells you what would happen and waits for your agreement.
-
Cannot act on LinkedIn
No posts, messages, comments, connection requests, or follows. Nothing an assistant does starts a scan.
-
Audit log, revoke any time
Developer, then Connected apps lists every action and keeps that history for 90 days. Revoke cuts access off immediately.
-
300 actions an hour
An assistant is limited to 300 actions an hour on this address. That covers a conversation and stops one stuck in a loop.
-
Bound to one address
Credentials last an hour, renew quietly for up to 30 days, and work only against the Embers MCP address.
Full details in the MCP setup guide, the security page, and the Privacy Policy.
Before you
connect.
Which assistants work, what they can change, and who on the account can approve them.
Read the setup guideAny assistant that can add a remote MCP server and sign in with OAuth. The clients on this page all use the same address. Embers does not require a particular one.
No. Assistant access is included on Solo and above. A Free workspace is refused the first time an assistant calls a tool. Connecting does not add a separate charge.
No. Embers never posts, messages, comments, connects, or follows on LinkedIn, and no assistant can make it. Drafting an opener saves a draft for you to send yourself. Nothing an assistant does starts a scan. A push to HeyReach hands the lead to HeyReach, which is what sends on LinkedIn, and the assistant asks before that push.
Any signed-in member can open Developer, then Connected apps, and approve an assistant. The plan check runs on the first tool call, not when you open the screen.
On a client workspace, the plan that counts is the agency parent's. If that parent is on Free, the first tool call is refused.
Your queue, in the
chat you already have.
Paste one address and approve Embers. Assistant access is included on Solo and above.
Solo and above · OAuth, no API key · No LinkedIn actions · Revoke any time