Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Onsa is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
16
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Find scored B2B leads, read campaign replies and send approved LinkedIn outreach.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http onsa-mcp https://api.onsa.ai/api/mcp
# 2 — ask your agent for something these tools do
# preview_shortlist, create_shortlist, revoke_shortlist and 13 more
Onsa costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ONAll 1 server
onsa1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http onsa-mcp https://api.onsa.ai/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Prepares 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 pre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | — |
| leadIds | array | yes | — |
| title | string | yes | — |
| note | string | yes | — |
| includeRationale | boolean | yes | When true, each person in the snapshot carries a fit rating (1–5, or null when none is stored) and a why-matched explanation; when false, the rating is null and the explanation empty. |
Publishes 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | — |
| leadIds | array | yes | — |
| title | string | yes | — |
| note | string | yes | — |
| includeRationale | boolean | yes | When true, each person in the snapshot carries a fit rating (1–5, or null when none is stored) and a why-matched explanation; when false, the rating is null and the explanation empty. |
| previewKey | string | yes | — |
| confirmPublic | boolean | yes | — |
Revokes 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
Starts 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 lead
| Parameter | Type | Required | Notes |
|---|---|---|---|
| taskContext | string | no | Optional company, product, or target-market facts explicitly shared by the user and needed for this lead-search or campaign-steering request, beyond what the query/message already states. Maximum 1000 |
| query | string | yes | Natural-language lead brief, e.g. 'find 5 fintech founders in NYC' |
| limit | integer | no | How many leads to find (default 5) |
Returns 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"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | The jobId returned by find_leads |
| limit | integer | no | How many leads to return (default 100) |
Lists 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 f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many campaigns to return, newest first (default 50) |
Returns 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | Campaign id, as returned by list_campaigns or fetch_leads |
Returns 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | Campaign id, as returned by list_campaigns or fetch_leads |
| leadIds | array | no | Optional; when set, only these leads are returned, e.g. positiveLeadIds from get_campaign_stats |
| limit | integer | no | How many leads to return (default 50) |
Sends 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| taskContext | string | no | Optional company, product, or target-market facts explicitly shared by the user and needed for this lead-search or campaign-steering request, beyond what the query/message already states. Maximum 1000 |
| campaignId | string | yes | Campaign to continue, from list_campaigns or fetch_leads |
| message | string | yes | What to tell the agent, in plain language, as the user would say it |
Lists 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. This tool sends nothing: rewrite_outreach replaces a draft's text, and send_outreach
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | no | One campaign to limit the list to; when omitted, the list covers every campaign the user takes part in |
| limit | integer | no | How many drafts to return (default 50) |
Returns 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:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| leadId | string | yes | Lead to read, from any tool that returns leads |
Replaces 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| leadId | string | yes | Lead whose draft to rewrite, from list_pending_outreach |
| text | string | yes | The full replacement message. This same string is called draftText when list_pending_outreach returns it, and confirmText when you pass it to send_outreach — three names, one set of bytes. |
| subject | no | Email subject; only email delivery reads it, and send_outreach, a LinkedIn send, does not. When omitted, the stored subject stays unchanged, so a body-only edit keeps it; a string replaces it, and nul |
Queues 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_outrea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| leadId | string | yes | Lead to message, from list_pending_outreach |
| confirmText | string | yes | The exact draft text you showed the user and they approved, verbatim |
| confirmName | string | yes | The recipient's name as shown to the user, to prove you meant this person |
Returns 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | Campaign to read replies from |
| limit | integer | no | Maximum replies to return, newest first (default 50) |
Returns 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 waiting for approval, leads found bu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | no | Optional campaign to inspect; omitted for workspace guidance |
Returns 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. `inv
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | Campaign id, as returned by list_campaigns or fetch_leads |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Onsa or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Onsa can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.