Connect an AI assistant with MCP
Paste one server address into an AI assistant, approve Embers once in your browser, and work your lead queue by chat or voice with twelve actions.
An AI assistant connected to Embers can read your lead queue and act on it: “what should I work on today”, “draft an opener for her”, “mark him contacted and follow up Tuesday”. You paste one address, approve Embers once, and work from the conversation you are already in.
Connect an assistant
-
Open Connected apps
Open Connected apps (
/developer/connected-apps). Administrators reach it from Settings, then Developer. In the default view, everyone can also reach it from Integrations in the sidebar, through the MCP card. On Free the screen is shown locked, but the address below is the same for everyone. -
Copy the server address
The Connect an AI assistant card shows
https://mcp.useembers.com/mcp. Choose Copy. -
Add it to your assistant
Add it wherever your assistant lists remote MCP servers and paste the address. There is no API key to fill in. If your assistant shows optional OAuth Client ID and Client Secret fields, usually under advanced settings, leave them blank: the assistant registers itself with Embers.
-
Approve the connection
Your browser opens an Embers approval screen showing which application is asking, the web address its callback points at, and exactly what it will be able to do. Check the address against the assistant you are setting up, then choose Allow access.
What an assistant can do
Twelve actions, and nothing outside them:
| It can | Tool | Which means |
|---|---|---|
| List your workspaces | list_accounts | So it knows which one you mean, which destinations each has, and each configuration with its tool (provider) |
| Read today’s queue | today_queue | The same ranking as the Priority Queue, with the reason and a suggested action |
| Search your leads | search_leads | The leads list filters, up to 100 at a time |
| Open one lead | get_lead | Profile, score breakdown, recent engagement, notes, status |
| Draft an opener | write_opener | Saved as that lead’s draft, the same stored draft you see in the app, for you to send |
| Read your ICP | get_icp | The criteria every lead is scored against |
| Preview an ICP change | preview_icp_update | Saves nothing. Shows which leads the edit would drop or add |
| Update your ICP | update_icp | Asks first. Re-scores every lead |
| Record ICP feedback | icp_feedback | Your verdict on whether one lead fits, or withdraw one |
| Update a lead’s status | update_lead_status | Status, note, follow-up date, outcome, snooze |
| Push leads to a destination | push_leads | Asks first. Up to 100 leads to one connected destination |
| Block a company | block_company | Asks first, because it hides everyone at that company |
Approval grants three permissions, shown on the approval screen: Read leads and drafts (leads:read), Update leads (leads:write, for status, feedback, pushes, and blocks), and Edit your ICP (icp:write, for previewing and saving ICP changes).
What it never does
- Nothing is sent on LinkedIn. No action posts, messages, comments, connects, or follows. Sending an opener is yours.
- No action starts a scan. Saving an ICP change is the only action that can spend enrichment credits, and it says so and waits for your agreement.
- Nothing is deleted. Blocking hides a company’s people and dismisses the lead, and you can unblock the company later.
- Nothing leaves Embers unasked. A push asks every time and only reaches a destination the workspace already connected. HeyReach, Instantly, Smartlead, and Emelia do the sending on their side. Each destination’s delivery rules apply unless you tell the assistant to ignore them.
How it handles scores, workspaces, and changes
Embers gives each lead two numbers from 0 to 100, and the assistant is told to keep them apart. ICP match (icp_score, filtered with min_icp_score) is the ICP fit percentage the app shows, and what “80%+ leads” means; leads not yet classified are left out of that filter. Lead score (composite_score, filtered with min_score) blends engagement with ICP fit, as lead scoring explains, and is rarely what you mean.
With several workspaces, every action except listing them needs the workspace named. Names match whole, so “Acme” does not pick between “Acme HQ” and “Acme EU”.
Changes that affect more than one lead ask before they act. The assistant calls once to learn what would happen, tells you, and goes ahead only when you agree. Repeating a status update is safe: the note is saved once.
How a push picks the tool
push_leads names a channel, not a tool: automation is LinkedIn (HeyReach), email_outreach is email (Instantly or Smartlead), and multichannel_outreach is Emelia. A configuration_uuid picks one configuration, and with it the tool and the campaign.
With one email tool connected, a push to email_outreach without a configuration_uuid goes to its first switched-on configuration, as before. When both Instantly and Smartlead have configurations, it never guesses: the tool returns a configuration_required error, and data.configurations lists each configuration that could take the leads, with its uuid, name, provider, provider_label, target_name, is_enabled, and paused. The assistant should ask you which one and push again with that configuration_uuid.
How an ICP change works through an assistant
The assistant should preview the change first. Leads a rule would drop come back at once, with the rule named; the AI then re-judges a sample of up to 200 leads and reports the matches it would drop and the leads it would add. Nothing is saved yet.
When you agree, the assistant applies that preview, so the verdicts you saw are the ones saved, and it can keep any lead you name as a match. The confirmation lists what is added and removed, how many leads will be re-classified, and how many match today. A change that matches what the ICP already says is refused rather than re-scoring for nothing.
Undo it from Undo last change in the Change history card on the ICP screen: see change your ICP safely. To reverse feedback on one lead, ask the assistant to withdraw the verdict; the lead goes back to unclassified, as read and correct an ICP match describes.
Access, activity, and limits
Approval issues credentials that act as you and work only at the MCP address, not against the rest of Embers. Access lasts an hour at a time and renews in the background; the renewal credential lasts 30 days and is replaced every time it is used.
Connected apps lists each assistant under Authorized apps with its permissions and when it last used the connection. Revoke ends its access immediately. Recent activity records every action an assistant takes: which one, a short summary of what it was asked, whether it failed, which assistant, and when. Activity is kept for 90 days.
An assistant can make 300 calls an hour. Drafting an opener also counts against the app’s 60 per hour AI budget. Over a limit, the assistant is told how long to wait.
Troubleshooting
The approval screen says the request is not valid. The request expired or was already used. Start again from the assistant.
The assistant says it is not authorized. Access was revoked, or approval never finished. Reconnect from the assistant and complete the browser step.
It says you have several workspaces, or a workspace was not found. Tell it which one, by full name, or ask it to list your workspaces.
A tool says it requires a paid plan. The workspace, or a client workspace’s agency parent, is on Free. See change your plan.
A push is refused with configuration_required. Both Instantly and Smartlead have configurations, and the assistant did not say which one to use. Tell it which campaign; it retries with that configuration.
A push is refused with “configuration not found”. The configuration_uuid is unknown or stale, usually because the configuration was deleted. Ask the assistant to list your workspaces again and pick a current one.
A push is refused. The destination is not connected, or its configuration is paused. An administrator sets destinations up; start from choosing where Embers sends your leads.
The assistant cannot connect at all. Check the address is https://mcp.useembers.com/mcp. The older api.useembers.com address is refused by assistants that verify the server they connect to.
Related
Frequently asked questions
- Can an assistant message or connect with people on LinkedIn?
- No. No action posts, messages, comments, connects, or follows on LinkedIn. Drafting an opener saves a draft for you to send yourself.
- Does this spend enrichment credits?
- Only an ICP update can, because saving re-scores your leads and may enrich newly matched people. The assistant has to tell you that and get your agreement first. Nothing an assistant does starts a scan.
- How do I disconnect an assistant?
- Open Developer, then Connected apps, choose Revoke next to it under Authorized apps, then confirm with Revoke access. Access stops immediately.
- My assistant asks for an OAuth Client ID. Where do I find it?
- You do not need one. Leave the OAuth Client ID and Client Secret fields blank when you add the connector. The assistant identifies itself to Embers automatically, so there is nothing to look up or paste.
- Do I need an API key?
- No. You approve the connection in your browser and Embers issues the credentials itself. There is no key to copy or store.
Was this article helpful?
What went wrong?
Thank you. We read every answer.
Your first 2,000 engagers free
Every day Embers reads the public activity around your market, ranks the people who fit, and hands you a short list with the reason each one surfaced. You decide who to contact.
Start free trial- No card to start
- No LinkedIn login
- Cancel anytime