Onsa MCP MCP server

The Onsa MCP server enables AI assistants to automate B2B lead generation and LinkedIn outreach. It allows agents to find scored leads based on Ideal Customer Profiles, monitor campaign performance and replies, and send approved outreach messages directly to prospects.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Onsa

MCP endpoint (Streamable HTTP)

https://api.onsa.ai/api/mcp

Vendor documentation

What you can do with it

Find scored B2B leads matching specific ICP criteria
Read campaign replies and analyze prospect sentiment
Rewrite and send approved LinkedIn outreach drafts

Tools advertised by the last live check:

preview_shortlist
create_shortlist
revoke_shortlist
find_leads
fetch_leads
list_campaigns
get_campaign
get_campaign_leads
continue_campaign
list_pending_outreach
get_lead_memo
rewrite_outreach
send_outreach
list_replies
list_next_steps
get_campaign_stats

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http onsa-mcp https://api.onsa.ai/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add onsa-mcp --url https://api.onsa.ai/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable onsa-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "onsa-mcp": {
      "url": "https://api.onsa.ai/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "onsa-mcp": {
      "type": "streamableHttp",
      "url": "https://api.onsa.ai/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start onsa-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "onsa-mcp": {
      "type": "http",
      "url": "https://api.onsa.ai/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http onsa-mcp https://api.onsa.ai/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "onsa-mcp": {
      "url": "https://api.onsa.ai/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "onsa-mcp": {
      "serverUrl": "https://api.onsa.ai/api/mcp"
    }
  }
}

See all 347

Do you run Onsa MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing