Onsa MCP server
Yes. Onsa publishes an official MCP server at https://api.onsa.ai/api/mcp. It's hosted. It offers 16 tools. We last checked it on 22 Nov 2026.
Official: published in the official MCP Registry as ai.onsa/onsa, a name only the owner of onsa.ai can publish under. Checked 22 Nov 2026. Maintained by Stuart Brameld.
Key facts
As of 22 Nov 2026, Onsa's official MCP server scores 72/100 (provisional) on MartechDB's Agent Readiness Index (v1.1). It answered 55 of our 55 checks in the last 90 days and lists 16 tools.
How the Agent Readiness Index works · Wrong? Suggest a correction
Onsa MCP server review
72/100
Onsa's Onsa scores 72/100 on MartechDB's Agent Readiness Index: easy to connect an AI agent to, with a few gaps.
The good
Hosted by Onsa: connect by URL, with nothing to install
Documented, with 16 tools known
Published to the official MCP Registry
Answered 100% of our checks in the last 90 days
Free trial
The bad
Nothing we've found.
Not checked yet: how you sign in. Anything not checked scores nothing.
Official MCP server
Onsa
Find scored B2B leads, read campaign replies and send approved LinkedIn outreach.
- Address
- https://api.onsa.ai/api/mcp
- Runs
- Hosted
- Sign-in
- Vendor docs
- Cost to use
- Official MCP Registry
-
Listed as
ai.onsa/onsa· published 8 Sep 2026 - How we know it's official
-
- Published in the official MCP Registry as ai.onsa/onsa, a name only the owner of onsa.ai can publish under.
- Documentation
- onsa.ai/mcp
- Tools
- 16 tools · listed 22 Nov 2026
- First seen
- 8 Sep 2026
- Last checked
-
Reachable ·
16 Nov 2026: reachable17 Nov 2026: reachable18 Nov 2026: reachable19 Nov 2026: reachable20 Nov 2026: reachable21 Nov 2026: reachable22 Nov 2026: reachable
- Uptime
- 100% · 55 of 55 checks reachable since 1 Oct 2026
Onsa tools (16)
As the server lists them. Names and descriptions are the vendor's own.
-
preview_shortlistPreview a shareable listPrepares a preview of 1–50 selected prospects from a campaign the user takes part in, and publishes nothing. The snapshot holds a list title, which is the campaign's name, the note, and for each person only a name, role, company, LinkedIn profile and, when includeRationale is true, a fit rating and why-matched explanation. The preview returns the complete snapshot a link would expose, with the previewKey that create_shortlist requires; a created link stays viewable for 30 days by anyone who has it, and can be revoked with revoke_shortlist.
-
create_shortlistCreate a public list linkPublishes a preview_shortlist snapshot as a link. It requires the previewKey that preview_shortlist returned, and confirmPublic: true. The server itself requests no confirmation from the user: confirmPublic: true records the caller's statement that the user reviewed this snapshot and confirmed publishing it. The server rebuilds the snapshot and creates nothing when the selection or the snapshot no longer matches that previewKey: a different campaign, selection or order of leadIds, a different note, an includeRationale value that changes the snapshot, a prospect changed or removed, or the campaign renamed since the preview. The link makes the snapshot viewable by anyone who has it for 30 days unless it is revoked with revoke_shortlist. This does not share the conversation or invite anyone into the workspace. Returns the URL, list id and expiry to the requester; sending it to another person is a separate user action.
-
revoke_shortlistRevoke a list linkRevokes a list link by the id create_shortlist returned; only the user who created the link can revoke it. Future views stop immediately; previously copied or downloaded information cannot be recalled.
-
find_leadsFind leadsStarts a live B2B lead search with Onsa's agent, matching real people (with LinkedIn profiles) against the workspace's ICP. Takes a natural-language brief - titles, company type, geography, e.g. 'find 5 fintech founders in NYC'. Returns a jobId immediately, with campaignUrl and a `progress` note. The search itself runs in the background and keeps running after the conversation moves on. First leads arrive within 5 minutes in half of searches and within 9 minutes in 9 of 10. More can arrive until the final report, typically about 10 minutes after the start (9 of 10 within 15). Its status and results are read with fetch_leads, with the same jobId at any later time. Hosts that render MCP Apps show a live card that follows the search and lists leads as they arrive. `limit` is a target the agent aims at rather than a cap, so it often returns more than asked. Every lead it finds counts against the workspace's prospect allowance.
-
fetch_leadsFetch search resultsReturns the status and any results of a find_leads or continue_campaign job, by jobId. Status values are "pending", "completed" and "stalled", and `leads` can hold a partial list while "pending". For a find_leads job: "pending" while it has no leads, the agent has not answered and it is under about 15 minutes old, and also while it has leads, until a reply carrying leads completes it; "completed" once the agent posts a reply carrying leads while this is the oldest open job on its campaign, usually its final report (`total` can still change afterwards); "stalled" as soon as the agent answers without any leads (a question, or none found), or when no lead has arrived after about 15 minutes - derived on each read, so a lead that lands later turns it back to "pending". For a continue_campaign job: "pending" while `newLeads` is 0 and it is under about 15 minutes old, even after the agent has replied (if that reply confirms a settings-only change, the request is done), and while `newLeads` i…
-
list_campaignsList campaignsLists the campaigns (past lead searches) in this workspace that the user takes part in, newest first. Returns the newest `limit` of them, default 50; `returned` against `total` shows whether older campaigns were omitted. Each entry has id, title, leadsTotal, hasIcp, tags, createdAt and updatedAt. An id is accepted by get_campaign for its ICP, get_campaign_leads for its people, get_campaign_stats for its outreach funnel, list_replies for what prospects wrote back, and list_next_steps for what the campaign still needs a human to do. Searches started over MCP often share a generic title, so the ICP and the dates distinguish cohorts more reliably than the title alone. A campaign row exists from the moment a search starts, so the newest entry is frequently still empty, with leadsTotal 0.
-
get_campaignGet campaignReturns one campaign's ICP - the ideal-customer profile the agent derived and scores leads against - plus its outreach template and settings. The ICP comes back exactly as stored, in snake_case: `perfect_lead` and `reachable_market` are one-line summaries, while `company` and `person` hold the rules that actually drive scoring, each an object with `critical` and `preferential` rule lists. `product` and `owner` describe the seller. The two summary strings are not the scoring criteria; `company.critical` and `person.critical` are. No key is guaranteed present. `outreachTemplate` shows how much personalization the messages allow: a template whose only placeholders are [FIRST_NAME] and [COMPANY_NAME] produces near-identical mail-merge copy for every lead.
-
get_campaign_leadsGet campaign leadsReturns the leads of any campaign by campaignId, with the same fields as fetch_leads, including score and scoreExplanation. It covers campaigns not started in this session, which fetch_leads cannot reach because fetch_leads requires a jobId from a find_leads call in the same session. Passing `leadIds` resolves the reply buckets from get_campaign_stats back into named people. A lead carries `signal` only when the search asked for a need signal.
-
continue_campaignSteer a campaignSends an instruction to the agent inside an existing campaign and returns a jobId to read with fetch_leads. This is the tool that grows or steers a cohort in place - 'find 5 more like these', 'look at Singapore and the Gulf instead of US institutions', 'focus on funds over $5bn AuM'. find_leads always creates a separate campaign with its own ICP, which splits the funnel and leaves the two cohorts incomparable. The agent sees the campaign's existing leads and ICP, so they can be referred to. It cannot answer back through this API, so a question sent here gets no response. New leads count against the prospect allowance, and de-duplication is per workspace, so a request for 5 more can yield fewer when the agent rediscovers people already in the workspace. It does not remove or skip leads: 'drop the bad ones' takes nothing out of the cohort or out of the outreach queue.
-
list_pending_outreachList pending outreachLists outreach messages the agent has drafted that are waiting for a human to approve - the 'a message for X is ready' queue. Each entry carries the draft text, the lead it is for, and why that lead scored as it did. Without campaignId, the list covers every campaign in this workspace that the user takes part in. Each entry has `kind`: first_message, or follow_up (a LinkedIn follow-up for someone who did not reply, carrying the message it follows up in `followsUp`). This tool sends nothing: rewrite_outreach replaces a draft's text, and send_outreach queues one for delivery.
-
get_lead_memoGet lead research memoReturns the research memo Onsa's agent wrote about one lead: role history, company size and stage, what they have said publicly, and the angle on them. It is usually far richer than scoreExplanation, and it is the source material for outreach built on a specific, checkable fact rather than a generic opener. Most leads have no memo - Onsa writes one only for prospects it has researched - so `memo: null` is the common case and not an error, and scoreExplanation is the remaining source in that case.
-
rewrite_outreachRewrite outreach draftReplaces the text of an outreach draft that is waiting for approval. The current draft and the lead's scoreExplanation come from list_pending_outreach; get_lead_memo carries the richer research on that person. The rewritten draft stays in the approval queue, and this tool sends nothing. LinkedIn follow-up drafts (kind: follow_up) cannot be rewritten here: they are edited in Onsa, or approved as written with send_outreach.
-
send_outreachSend outreach messageQueues one already-approved outreach draft for delivery to a real person on LinkedIn. It requires `confirmText`, the draft body character-for-character as stored, and `confirmName`, the recipient's name: drafts are often near-identical between people, so matching the body alone does not identify which one was meant. A mismatch is refused without returning the stored text, which list_pending_outreach supplies. The server additionally requires a confirmation from the person at the keyboard, rendered by the MCP client and quoting the draft as stored; that approval is single-use and bound to one recipient and one draft. A client that cannot render such a confirmation receives a refusal carrying a link to approve inside the Onsa app, and nothing is queued. On success the message is queued rather than delivered: Onsa sends it on its own schedule, subject to daily pacing limits. A follow-up draft (kind: follow_up) goes into the same LinkedIn thread as the first message and is cancelled if th…
-
list_repliesRead prospect repliesReturns the text of what prospects replied, for every lead in the campaign that answered, paired with the outbound message it answers. get_campaign_stats counts replies and labels them; this returns the words. `sentiment` is Onsa's own label, written once per lead on their first reply - later replies never change it, and a reply Onsa has not scored yet comes back as `sentiment: null`, which means unscored rather than neutral. Those unscored replies are absent from get_campaign_stats entirely, so this tool can return more replies than the funnel counts. Three derived fields come with the reply. `awaitingOurReply`: the prospect spoke last and no sent message followed. It is structural only - a flat 'no thanks' satisfies it too - and Onsa sees only what Onsa sent, so a reply made by hand inside LinkedIn is invisible to it; what the data supports is 'no reply recorded here'. `daysSinceLastReply` is elapsed whole days rather than time-unanswered: it is populated even where we did answer, s…
-
list_next_stepsWhat to do nextReturns read-only guidance for what to do next. Without campaignId, it returns the first-search question, active search progress, or campaign names and statuses to choose from. A single accessible campaign is resolved automatically. With campaignId, it returns a ranked to-do list: people who replied, people who accepted an invite but were never messaged, drafts and LinkedIn follow-ups waiting for approval, people with no reply for 7+ days while follow-ups are off, leads found but never contacted, and setup that is missing. It answers 'what should I do about this campaign today', where get_campaign_stats answers 'how is it doing'. For replies specifically, list_replies is the better source: its `awaitingOurReply` compares timestamps, while the `replied` bucket here covers only leads whose sentiment was scored and does not know whether we have since answered. `leadIds` passed to get_campaign_leads resolves the buckets into named people. Limits of the data: Onsa does not record whether w…
-
get_campaign_statsGet campaign funnelReturns the outreach funnel for one campaign: invites sent, invites accepted, messages sent, and replies split into positive / negative / other by sentiment. LinkedIn and email are merged, as on Onsa's Overview page. These count leads rather than actions - a lead invited twice counts once - so where a lead was re-invited they read slightly lower than the Overview widget, which counts actions. `invitesSent` can exceed `leadsTotal` without anyone having been invited twice: the counters are already de-duplicated by lead, and the gap means a lead who was contacted has since been skipped or deleted, which action rows survive and leadsTotal does not count. Onsa stores no post likes or emoji reactions at all, so 'LinkedIn reactions' in this data means the replies people sent; list_replies returns their text, and this tool only counts them. `rates` carries acceptancePct, replyPct, positivePct and negativePct, each already computed over its own correct denominator; leadsTotal is not one of tho…
Connect your AI to Onsa
Add the official Onsa MCP server to Claude, ChatGPT or your editor.
Connect Onsa MCP to Claude
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it Onsa, paste the address below and click Add.
Connect Onsa MCP to ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it Onsa and paste the address below.
ChatGPT usually only connects to servers with self-serve sign-in or none.
Connect Onsa MCP to Cursor
Opens Cursor if it's installed. If nothing happens, use the JSON below.
Connect Onsa MCP to VS Code
Opens VS Code if it's installed. Otherwise add the JSON settings from the Cursor tab to your .vscode/mcp.json.
Onsa MCP server questions
Does Onsa have an official MCP server?
Yes. Onsa publishes its MCP server itself. It's in the official MCP Registry under Onsa's own domain. MartechDB only lists servers a vendor publishes, never community copies.
What is the Onsa MCP server URL?
The address is https://api.onsa.ai/api/mcp.
How do I connect Onsa MCP to Claude, ChatGPT or Cursor?
In Claude, add https://api.onsa.ai/api/mcp as a custom connector (Customize, Connectors, Add custom connector). In Cursor, use the Add to Cursor link on MartechDB's page, or paste the JSON settings into your mcp.json. In Claude Code, run: claude mcp add --transport http onsa https://api.onsa.ai/api/mcp
What can the Onsa MCP server do?
It offers 16 tools, including preview_shortlist, create_shortlist, revoke_shortlist, find_leads and fetch_leads (as listed on 22 Nov 2026). 10 are marked read-only and 6 can delete or overwrite data.
Is the Onsa MCP server in the official MCP Registry?
Yes, as ai.onsa/onsa.
Is the Onsa MCP server working?
Yes. It answered our most recent check. We last checked it on 22 Nov 2026.
What are the alternatives to Onsa's MCP server?
In Prospecting & lead data, the most agent-friendly alternatives with an official MCP server are Boomerang (97/100), Seamless.ai (94/100), Poggio (94/100), Crossbeam (94/100) and Scalelist (94/100). Onsa scores 72/100 on the same index.
Alternatives to Onsa's MCP server
Vendors in Prospecting & lead data with an official MCP server, the most agent-friendly first. Onsa scores 72/100.
Boomerang
getboomerang.ai
Seamless.ai
seamless.ai
Poggio
poggio.io
Crossbeam
crossbeam.com
Scalelist
scalelist.com
Use with AI
Connect your AI to MartechDB
Then ask it about Onsa, or any of the 1,850 marketing tools with an official MCP server. Free, no sign-in.
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it MartechDB, paste the address below and click Add. There's no sign-in.
The free plan allows one custom connector. On Team and Enterprise plans, an owner adds the connector first.
Claude Code
Run this in your terminal:
ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it MartechDB, paste the address below and choose No authentication.
Developer mode is on Plus and Pro plans, and on Business, Enterprise and Edu if an admin allows it.
API
The same data as JSON, with no sign-in. See the OpenAPI description for every endpoint and field.
CLI
Search the directory and print the command to connect a vendor's server, from your terminal. Needs Node 18 or later. View on npm
Show that your MCP server is verified
If you work at Onsa, add this badge to your MCP docs or README. It's free, it's the same for every vendor, and it updates from our daily checks: it shows uptime while the server responds, and says so if it stops.
Something wrong or out of date? Suggest a correction or email us, and we'll check it against the evidence. Every correction we make is listed on Corrections.