Use Leadsets with Meta Muse over MCP

Leadsets connects to Meta Muse as a remote MCP server plus free skills, per the Leadsets integrations page. Add https://mcp.leadsets.ai to the agent and it gets eight tools: people and company search, enrichment, verified work emails, website and careers-page scraping, and a free usage check. Leadsets does not publish Meta Muse-specific setup steps, so the generic MCP setup in its docs applies.

What an agent can do with Leadsets through Meta Muse

Leadsets lists Meta Muse among the personal agents it supports, connected through its MCP server and skills. Once connected, the agent can call the same eight tools every MCP client gets:

search_people: find people by title, function, seniority, location, company size and industry, with a reason for every match.
search_companies: find accounts by industry, headcount band, technology and location.
enrich_person: current role, company and a verified work email when one exists.
enrich_company: firmographics for a domain, with source and freshness on every field.
verify_email: labels an address verified, catch-all, unknown or invalid, with a confidence score.
scrape_company: turns a company homepage into products, positioning, customers named and key links.
scrape_jobs: open roles from careers pages, with titles and dates, as hiring signals.
get_usage: what is left in the current window and week, at no cost.

You describe your customer in plain language, and the agent turns it into filters and picks the tools. Results come back as structured JSON with match reasons, verification status, confidence and the date each field was last checked.

How to connect Leadsets to Meta Muse

The Leadsets site does not document menus, buttons or settings inside Meta Muse. The steps below are the generic remote MCP setup from the Leadsets MCP docs; apply them wherever your Meta Muse setup lets you add an MCP server.

Create a free Leadsets account. The free plan gives 1,000 records, one time, with no card. If you need an API key, copy it from the dashboard. Keys start with ls_live_ and should be kept server-side.
Add the remote MCP server URL: https://mcp.leadsets.ai. Leadsets is a remote server, so nothing is installed or run locally.
Authenticate. Leadsets supports two patterns in its docs. In Claude, the connector signs in with OAuth, so there is no key to paste. In Cursor, you add an Authorization header with Bearer ls_live_.... Use whichever method your client offers.
Check the connection. Ask the agent: "What's my Leadsets usage?" It should call get_usage and answer with your remaining balance. If it does, you are connected.
Add skills (optional). Leadsets publishes 50 free, MIT-licensed SKILL.md playbooks for any agent that reads the SKILL.md standard. Get them with git clone github.com/leadsets/leadsets-skills. The site does not describe how to load skills into Meta Muse specifically.

If you would rather call Leadsets from your own code or an HTTP step, every tool is also a REST endpoint at https://api.leadsets.ai/v1 with a bearer key, TypeScript and Python SDKs, idempotency keys, cursor pagination and Retry-After headers:

curl https://api.leadsets.ai/v1/people/search \
 -H "Authorization: Bearer $LEADSETS_KEY" \
 -d '{ "title": ["VP Sales"], "country": ["US"],
       "employees": "50-200", "has_verified_email": true,
       "limit": 25 }'

Lists can then go out as CSV to any sequencer, into Google Sheets, or to CRMs such as HubSpot, Salesforce, Pipedrive and Attio through skills and the API.

Example workflow: a hiring-signal list

Maya Chen runs revenue operations at Northwind Analytics (northwind.co). She asks her agent in Meta Muse:

"Find US B2B SaaS companies with 50 to 200 people that are hiring SDRs. Get their heads of sales with verified work emails and put them in a CSV."

A typical run, as the Leadsets tools are designed to chain:

get_usage checks what is left in the five-hour and weekly windows.
search_companies finds matching accounts by industry, headcount and location.
scrape_jobs reads their careers pages and confirms which ones list SDR roles, with dates. This uses scrape units, a paid add-on.
search_people finds sales leaders at the confirmed accounts, each with match reasons.
enrich_person returns current role and a work email; every email it returns is already verified, so no second charge.
The agent exports a CSV with catch-all addresses on a separate tab and reports any person without a usable email.

For a ready-made version of steps 2 to 6 without the hiring check, the build an outbound prospect list skill runs the same sequence and segments catch-alls for you.

What to watch for

Free records are one time. The 1,000 free records cover search and enrichment, do not refill and do not expire. When they run out the API returns 402 free_records_exhausted.
Scraping is not on Free. scrape_company and scrape_jobs need scrape units on a paid plan: $9 for 1,000, $19 for 5,000 or $49 for 20,000. One unit is one standard page.
Records versus requests. A record counts only when data comes back, so empty searches use none. Every call counts as a request, and the request limit is five times the record allowance.
Windows and weekly limits. Paid plans (Solo $29, Pro $99, Team $399, Max $999 a month) have rolling five-hour and weekly limits per tool. Over a limit, Leadsets returns 429 with a Retry-After time and the blocked call counts against nothing. See limits and costs and pricing.
Concurrent searches. Solo allows 3, Pro 5, Team and Max 8. Extra searches get 429 too_many_concurrent.
Verification labels. Verified means the mailbox accepts mail. Catch-all means the domain accepts everything, so send at lower volume. Unknown means no clear answer, so treat it as unconfirmed. Invalid addresses are never served as contact emails. More on catch-all emails.

What it does not do

No phone numbers yet. Leadsets returns work emails, US personal emails on paid plans, roles and company data.
Not a CRM or sending tool. Leadsets feeds your CRM, sheet or sequencer; it does not send email.
No consumer data. Business contacts only, with no sensitive categories and no personal home addresses.
No logged-in scraping. Scraping reads public company pages only and respects robots signals.
SOC 2 is planned, not done. SOC 2 Type I readiness is underway with a target of Q3 2027. Buyers who need a SOC 2 report today should factor that in.

Other agents connect the same way; see all MCP clients.

Questions and answers

How do I add Leadsets to Meta Muse as an MCP server?

Add the remote MCP server URL https://mcp.leadsets.ai wherever your Meta Muse setup accepts MCP servers, then authenticate with OAuth sign-in or a bearer API key header. Leadsets does not publish Meta Muse-specific menus, so follow the generic remote MCP setup in its docs.

Do I need an API key to use Leadsets with Meta Muse?

It depends on how the client authenticates. Leadsets supports OAuth sign-in, as used in Claude, and a bearer key in an Authorization header, as used in Cursor. Keys start with ls_live_ and come from the free dashboard.

How can I check that the Leadsets connection works?

Ask the agent "What's my Leadsets usage?" If it calls get_usage and replies with your remaining balance, Leadsets is connected. The get_usage tool costs nothing.

Can Meta Muse use the Leadsets GTM skills?

Leadsets lists Meta Muse with MCP server and skills. The 50 free skills follow the SKILL.md standard and can be cloned from github.com/leadsets/leadsets-skills; the Leadsets site does not describe how to load them inside Meta Muse.

Can I scrape company websites through Meta Muse on the free plan?

No. scrape_company and scrape_jobs are not on the free plan. Scraping is a paid add-on billed in units, with packs from $9 for 1,000 units.

Does Leadsets return phone numbers to Meta Muse?

No. Leadsets does not offer phone numbers yet. It returns work emails, US personal emails on paid plans, roles and company data.

Go deeper

More integrations