Skip to content

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

https://mcp.useembers.com/mcp

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

claude mcp add embers --transport http https://mcp.useembers.com/mcp

Desktop and web

https://mcp.useembers.com/mcp

Same address for Claude Code, Claude Desktop, and claude.ai.

  1. In a terminal, run the Claude Code command below. It adds Embers and opens the browser.
  2. 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.
  3. On the approval screen, check the address, then choose Allow access.

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.”
Agent session Completed
You

What should I work on today?

Assistant today_queue
  • Nicolas ColePosted about declining LinkedIn reach94%
  • Oskar KwasniewskiPosted a recent founder lesson88%
  • Ben ShafiiShared a recent product launch update81%

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
The tool boardPick one to see what it does

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.

FAQ

Before you
connect.

Which assistants work, what they can change, and who on the account can approve them.

Read the setup guide

Any 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.

Connect once

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