Vendo AI MCP Server

by vendo-ai Your server? Claim it

answering

Vendo AI is answering right now. Last checked 59 min ago. It exposes 149 tools.

Autonomous AI sales: agents, signal-based prospecting, outreach, CRM — 149 tools.

Uptime history 48 days of history · worst day 0%

48 days agonow

100.0%

Uptime 24h

22 of 22 checks

149

Tools

read from the server

179 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Vendo AI every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 59 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.vendo-ai]
url = "https://api.vendo-ai.com/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 149

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

sdr

get_sdr_email_capacity

How many SDR sender email addresses the account has (included + purchased extras) and the estimated daily email throughput. Read-only.

sdr_activate_search

Set status=active and fire-start all enabled hunters. Reversible via `sdr_pause_search`.

sdr_activity_feed

Recent discovery + outreach events for one SDR search, newest first — the same ticker the dashboard shows. Read-only, free.

sdr_company_heat

Composite "heat" ranking — companies with the strongest live signal in the workspace.

sdr_create_search

Create a Signal Search and immediately activate the configured hunters. Required: name, agent_id. Optional: enabled_sources, target_regions (ISO-2 country codes), pre-edited profile fields from `sdr_preview_search`.

sdr_delete_outreach

Delete the SDR outreach campaign. The Signal Search and its hunters CONTINUE running. Only call after `sdr_preview_delete_outreach`.

sdr_delete_search

Permanently delete a Signal Search. Hunters are paused first, then the search and all its contacts/personas are removed. NOT reversible.

sdr_export_people_csv

Export the contacts of an SDR search as CSV text (name, title, email, LinkedIn, location, company). Contacts ONLY — deliberately carries no scores or signal reasoning, because this file leaves the platform. Returns the raw CSV; can be large. Read-only, free.

sdr_export_personas_to_audience

Take the personas matched by a Signal Search (optionally filtered by role / having email / specific IDs) and export them into a custom audience that can then be attached to any campaign.

sdr_generate_agent_signal_profile

Run Claude on the agent's knowledge to (re)generate its signal profile. Persists onto the agent so later Signal Searches reuse it.

sdr_get_agent_signal_profile

Read the agent's current signal profile (ICP, offer summary, hunter weights). Returns { exists: false } when nothing's generated yet.

sdr_get_outreach

Read the SDR outreach campaign — channels enabled, ready/queued/sent counts, current content config.

sdr_get_outreach_content

Read the configured email subject/body templates and LinkedIn invite template for SDR outreach.

sdr_get_person_detail

Full provenance for one person found by SDR: which hunter found them, what query fired, what signal triggered the pick, and the scoring breakdown. Use this to explain to a customer WHY a contact is in their list. Read-only, free.

sdr_get_search

Fetch one Signal Search by id, including its profile, hunters, and contact counts.

sdr_health

Operator-level health view: states, signals/contacts produced, credits spent, recent events, learning insights for a single search.

sdr_launch_outreach

Launch SDR outreach. Contacts will start receiving emails and/or LinkedIn invites. Credits spent per message. Only call after `sdr_preview_launch_outreach` and explicit user approval.

sdr_learning_insights

Learned weights per signal type and conversion stats based on real outreach outcomes.

sdr_list_personas

List the people Vendo SDR has discovered for a given Signal Search. Filterable by company, role, min_relevance.

sdr_list_searches

List active Signal Searches in this workspace. Optionally filter by agent.

sdr_outreach_summary

Per-channel sent and queued counts for one SDR search. Read-only, free.

sdr_pause_outreach

Stop sending new messages on this SDR campaign. Reversible.

sdr_pause_search

Pause hunters. Existing data stays; no new contacts surface. Reversible via `sdr_resume_search`.

sdr_persona_stats

Aggregate stats: total personas, by_role, top_companies, daily count series, credits_spent, quality_blocked.

sdr_preview_delete_outreach

Show what would happen. The Signal Search ITSELF is NOT deleted, only the outreach campaign.

sdr_preview_delete_search

Show what would happen if you delete the Signal Search. Nothing is deleted.

sdr_preview_launch_outreach

Show what would happen if you launch SDR outreach for this search — recipient counts per channel. NOTHING IS SENT. ALWAYS call first and surface the counts to the user.

sdr_preview_outreach_content

Render an example personalized email/LinkedIn message for a specific contact. Costs ~1 Claude call.

sdr_preview_run_now

Show what would happen if you trigger an immediate hunter run. Useful because some sources are paid (ai_web_hunter, g2_reviews, tech_stack — Anthropic + web_search credits).

sdr_preview_search

Run Claude on the agent's script and return the auto-generated ICP profile (offer summary, ideal customer profile, relevant topics, LinkedIn queries) WITHOUT persisting anything. Use to review/edit before calling `sdr_create_search`.

sdr_recent_signals

Last N signals across all Signal Searches in the workspace. Useful for the "is it working?" check.

sdr_regenerate_search

Re-run Claude on the agent's current knowledge to regenerate the entire ICP profile and hunter configuration. Useful after the agent's script changed significantly.

sdr_resume_outreach

Resume a paused SDR outreach campaign.

sdr_resume_search

Clear paused state and restart all hunters.

sdr_run_now

Fire-and-forget kick of one (or all) hunters for this Signal Search. Spends Anthropic + web_search credits for paid sources. Call after `sdr_preview_run_now`.

sdr_run_states

Per-source map of run state (running / paused / idle) for a Signal Search.

sdr_signal_stats

Signals collected by source over the last N days (max 90, default 30).

sdr_update_outreach_content

Edit email/LinkedIn templates for this SDR outreach. Takes effect on new sends.

sdr_update_search

Edit a Signal Search — name, enabled_sources, target_regions, or profile fields. Partial updates fine.

crm

crm_add_comment

Internal team note on the lead card (not visible to the lead). Supports @mentions via user ids.

crm_communication_cards

One card per campaign and per SDR search, with outbound counters. This is the FULL outbound stream — everyone contacted, whether or not they replied (CRM leads only contains people who answered). Read-only, free.

crm_communication_history

Every outbound touch for one campaign or SDR search, filterable by channel, reply status and date. Use `crm_communication_cards` first to get the id. Read-only, free.

crm_communication_thread

The complete message thread with one contact inside a card. `key` comes from a `crm_communication_history` row (an email address or LinkedIn chat id). Read-only, free.

crm_create_calendar_event

Add a custom event to the CRM planner. Write operation, no credit cost. Does NOT send invites to anyone — it only records the event on the internal calendar.

crm_create_lead

Add a lead card to the New stage. ALL fields optional — provide whatever is known (at least one non-empty). Side-effect: a card appears on the customer board.

crm_create_stage

Add a custom kanban column (name, optional hex color). Inserted before the terminal stages (Won/Lost).

crm_delete_calendar_event

Remove a custom calendar event. Unlike deleting a lead or a stage this destroys no history and needs no preview step, but it cannot be undone.

crm_enrich_from_linkedin

Fetch name / title / current employer / avatar / location for a linkedin.com/in/... URL (same lookup the SDR hunters use). May also suggest an email as an UNVERIFIED pattern guess (email_confidence=pattern_guess). Costs one profile view from the workspace's shared daily LinkedIn budget — do not loop over big lists.

crm_get_conversation

The full message thread with this lead on their source channel (LinkedIn / email / widget / telegram / phone transcript). Read-only.

crm_get_lead

Full lead card: identity, source ("why is this person here"), company enrichment, activities, comments, assignments. Read-only.

crm_get_settings

Read CRM settings, including the notify_* toggles that control which events send an email/notification. Read-only, free.

crm_list_calendar_events

List custom calendar events (meetings, reminders) in the CRM planner for a date range. Note: SDR sending windows also appear in the UI calendar but are derived from the search schedule — read those via `sdr_get_search`. Read-only, free.

crm_list_leads

List leads in the CRM pipeline. Filters: stage (stage id), source (e.g. linkedin_outreach_reply, email_reply_real, widget_chat, manual), q (name/company/email search), range (24h|7d|30d|90d|180d|1y|all), limit/offset. Read-only. Great first call for "who replied to me?".

crm_list_linkedin_accounts

List the LinkedIn accounts connected to this workspace, as shown in the CRM. Useful to see which account owns a conversation. Read-only, free.

crm_list_notifications

List CRM notifications (new lead, new reply, stage change). Read-only, free.

crm_list_stages

Ordered kanban columns for this workspace (id, name, color, is_terminal). Read-only. Call before moving leads.

crm_list_workspace_agents

List the AI agents in this workspace that CRM leads can be attributed to. Read-only, free.

crm_list_workspace_members

List the people in this workspace who can own a CRM lead. Use before `reassign_crm_lead` to get valid owner ids. Read-only, free.

crm_mark_all_notifications_read

Clear the CRM notification badge by marking everything read.

crm_mark_notification_read

Mark a single CRM notification as read. Write operation, no credit cost.

crm_move_lead

Drag-and-drop equivalent: move a lead to a different pipeline stage by stage_id (get ids from crm_list_stages). Reversible.

crm_reply_to_lead

Sends a REAL LinkedIn message or email reply to the lead on their source channel, from the customer's own account. Also moves the lead to the "Manager Dialog" stage. ALWAYS show the drafted text to the human and get approval BEFORE calling this.

crm_stats

Counts per stage, new today/this week, stale leads. Read-only.

crm_update_calendar_event

Edit an existing custom calendar event. Write operation, no credit cost.

crm_update_lead

Patch lead attributes (name, company, title, email, phone, notes, tags, deal_value). Reversible.

crm_update_settings

Change CRM settings — e.g. mute new-lead or new-reply notifications while an integration drives the CRM itself. Write operation, no credit cost. Turning notifications off means the human stops being alerted, so confirm with the user first.

crm_update_stage

Rename or recolor a stage. System stages (New, Manager Dialog) cannot be renamed.

delete_crm_lead

Soft-delete a lead — it disappears from the pipeline (restorable by support only). Only call after the user reviewed `preview_delete_crm_lead` output and explicitly approved.

delete_crm_stage

Delete an EMPTY, non-system pipeline stage. Only call after the user reviewed `preview_delete_crm_stage` and explicitly approved.

preview

preview_agent_email

Render a sample outreach email from this agent — no sending, no credit cost. Useful to check tone/script before launching.

preview_buy_audience_set

Dry-run of purchasing an audience set — shows what would be bought and what it costs, WITHOUT spending credits. ALWAYS call this first and show the cost to the human.

preview_deep_scan

Show what would happen if you run `deep_scan_agent`. The scan is NOT executed. ALWAYS call this first and confirm the cost (15 credits) and duration with the user.

preview_delete_agent

Show what would happen if you delete an agent. The agent is NOT deleted. ALWAYS call this first and surface the result to the user before calling `delete_agent`.

preview_delete_campaign

Show what would happen if you delete a campaign. The campaign is NOT deleted.

preview_delete_crm_lead

Dry-run of deleting a CRM lead — shows who would be removed from the board. ALWAYS call this first and show the result to the human.

preview_delete_crm_stage

Dry-run of deleting a pipeline stage. Deletion is refused downstream if the stage still holds leads or is a system stage.

preview_disconnect_linkedin_account

Dry-run of removing a LinkedIn account, showing the capacity that would be lost. ALWAYS call this first.

preview_launch_audience_set

Dry-run of buying a set AND starting outreach against it. Shows the cost without spending anything. ALWAYS call this first.

preview_launch_campaign

Show what would happen if you launch the campaign: recipient count, channels, daily limit. NOTHING IS SENT. ALWAYS call this first and surface the result to the user (recipient count, channels) before calling `launch_campaign`. This is required by Vendo AI policy and protects the user from a launch they did not intend.

preview_linkedin_followup

Render a sample first follow-up (after the connection is accepted). No sending, no cost.

preview_linkedin_invite

Render a sample LinkedIn connection request from this agent. No sending, no cost.

preview_reconnect_linkedin_account

Dry-run of re-authenticating a LinkedIn account. Explains the side-effects without doing anything. ALWAYS call this first — reconnecting changes the account id upstream and can orphan existing outreach history.

agent

create_agent

Create a new AI sales agent. Costs 1 credit. The agent is created in DRAFT status and does not start contacting anyone — you still need to attach it to a campaign and launch the campaign. Required: name + description. Company info (name/website/description) is required BEFORE generating a sales script, so you can either pass it here OR call `set_agent_company` later.

delete_agent

Permanently delete an agent. NOT reversible. Only call after the user has reviewed `preview_delete_agent` output and explicitly approved.

get_agent

Fetch the full details of a single agent by id.

get_agent_plan_limits

How many agents can the user create (base plan + purchased extra slots) vs how many they have. Read-only.

list_agent_connections

See every channel attached to this agent: widgets, telegram, phone, presentations, etc.

list_agent_presentations

Each agent can host one or more interactive presentations. Read-only list.

set_agent_avatar_from_url

Set the agent avatar from a publicly-reachable image URL (jpg, png). The MCP server downloads the image and uploads it on your behalf — you do not need to handle multipart yourself.

set_agent_company

Required before `generate_agent_script` will work. Set the company the agent represents — its name, website, and what it sells.

set_agent_contact_channels

Set the meeting link, email, phone, WhatsApp and Telegram that the AI agent gives out when a visitor asks how to get in touch or book a call. Omitted channels are cleared, so always send the full set you want the agent to have. Write operation, no credit cost.

set_agent_status

Change agent status. Allowed values: ACTIVE, PAUSED, ARCHIVED, DRAFT.

set_agent_voice

Set agent voice settings: voice_type (e.g. "11labs-Anthony"), language, speed, temperature, backchannel. Call `list_retell_voices` first to see what is available.

update_agent

Update an agent's basic info (name, description, company info). Partial updates are fine — only include the fields you want to change.

credit

get_credit_transactions

Credit deductions + grants, newest first. Optional filters: type (e.g. EMAIL_SENT, LINKEDIN_INVITE, SDR_CONTACT), date range, pagination.

get_credit_usage_by_agent

Total credit spend per agent in the workspace. Identifies the most expensive agents.

get_credit_usage_by_type

Per-session credit spend grouped by connection type (email_outreach, linkedin_outreach, phone_call, widget, sdr_contact, etc.). Useful for analytics.

get_credit_usage_for_agent

Total credits spent by one specific agent.

get_credit_usage_for_agent_connections

Per-channel credit spend (widget, telegram, phone, etc.) for one agent. Identifies the costliest channels.

get_credit_usage_monthly

Calendar-month breakdown of credit spend across all categories.

audience

get_audience

Read one saved audience with its filters and contact count. Read-only, free.

get_audience_set

Details of one marketplace set by slug: size, description, freshness. Use the contact count here to work out the purchase cost (2 credits per contact). Read-only, free.

get_audience_set_contacts

Paginated preview of the contacts inside a marketplace set. Contact details stay masked until the set is purchased. Read-only, free.

list_audience_sets

Browse pre-built, ready-to-use audiences available for purchase, plus their categories. Browsing is free; buying costs credits. Read-only.

search_audience

Search the people graph for prospects matching filters (countries, industries, positions, tags, must-have-email, etc.). PREVIEW only — returns aggregate counts and a small sample. Does not save anything, does not contact anyone, does not spend credits.

campaign

create_campaign

Create a new campaign in DRAFT status. The campaign is NOT launched — nobody is contacted until you call `launch_campaign`. Needs an audience id and an agent id.

delete_campaign

Permanently delete a campaign. NOT reversible. Only call after the user has reviewed `preview_delete_campaign` output and explicitly approved.

get_campaign

Fetch full details of a single campaign: status, sequence, channel paused flags, today stats.

update_campaign

Update a campaign before or after it has started. Partial updates allowed (only include fields you want to change).

connect

connect_google_meet

Returns a Google OAuth URL. The user MUST open this URL in a browser and grant consent — the MCP cannot complete OAuth on its own.

connect_linkedin_account

Returns a hosted URL that a HUMAN must open in a browser to authorise a LinkedIn account. This tool cannot complete the connection itself — give the link to the user. No account exists until they finish the flow.

connect_telegram_bot

The user creates a bot with @BotFather, gets the HTTP API token, and passes it here. After that, all messages to the bot are answered by the agent.

disconnect

disconnect_google_meet

Revoke Google Meet for this agent. Existing meetings stay in the user's calendar.

disconnect_linkedin_account

Remove a LinkedIn account from the workspace. Any campaign or SDR search sending from it stops immediately and daily capacity drops. Only call after the user reviewed `preview_disconnect_linkedin_account` and explicitly approved.

disconnect_telegram_bot

Detach the bot from this agent. Bot keeps existing in Telegram but stops responding.

agents

list_agents

List all AI agents in the account. Read-only.

list_agents_with_stats

Same as `list_agents` but includes per-agent stats (connections, credits spent, status).

balance

get_balance

Get the current credit balance for the account. Read-only, no side-effects, no cost.

get_balance_full

Richer than `get_balance` — returns balance, total subscription credits, total purchased, total spent, free-trial credits, email/workspace info.

generate

generate_agent_description

Use AI to draft a 2-3 paragraph company description. Costs 1 credit. Requires `company_website` already set.

generate_agent_script

Generate the agent's full sales script (8 stages) and email_script (for email/LinkedIn channels). Requires `company_name` AND `company_description` already set on the agent — call `set_agent_company` first. Costs 1 credit. Re-running OVERWRITES the existing script.

launch

launch_audience_set

SPENDS CREDITS and STARTS REAL OUTREACH to real people: buys the snapshot, then runs a campaign against it. The most consequential tool in this list. Only call after the user reviewed `preview_launch_audience_set` and explicitly approved.

launch_campaign

Launch the campaign — contacts will start receiving outreach immediately. SPENDS CREDITS continuously while the campaign runs. Only call AFTER the user has reviewed `preview_launch_campaign` output and explicitly approved the recipient count and channels.

narrator

get_narrator_analytics

Views, sessions, conversion to lead, drop-off by slide.

list_narrator_leads

Anonymized lead list from CTA forms in presentations.

pause

pause_campaign

Pause a running campaign across every channel. Reversible — call `launch_campaign` to resume.

pause_channel

Pause a single channel (email, linkedin, phone_call, voice_call) on a running campaign. Other channels keep going.

save

save_audience

Save a searchable audience using the same filter set as `search_audience`. The audience is named and can then be attached to a campaign. No outreach happens here.

save_scan_data

Save the output of a deep scan onto the agent (company description, people, contacts).

subscription

get_subscription

Plan, status (ACTIVE/CANCELLED/PAST_DUE/EXPIRED/TRIALING), period dates, currency, amount, Stripe IDs.

get_subscription_limits

Base + purchased extra agent slots. Useful to check "can I create another agent?" before calling `create_agent`.

get_telegram_analytics

Read-only stats: chats, messages, voice-call duration.

get_telegram_bot_info

See the connected bot username + settings.

Endpoints

URL	Transport	State	Latency	Checked
https://api.vendo-ai.com/mcp	streamable-http	answering	213 ms	59 min ago

Alternatives to Vendo AI

same job, measured the same way

Eesier — AI Lead Prospecting

by eesier

Autonomous B2B lead prospecting — 36 tools for campaigns, leads, and email outreach.

answering

Hilead

by hilead

Signal-based B2B prospecting: find leads with buying intent, run email and LinkedIn outreach.

answering

Sf MCP

by signal-found

Reddit outreach at scale — find prospects, send 1000s of DMs/day, and manage your CRM via AI agents.

62 installs/wk local only

Diversz Commons

by parkschun79

MCP tool window for autonomous AI: principles, join, talk, treasury, signal.

14 tools answering

Agentic Endpoints

by oliverkiss

Pay-per-call tools for autonomous agents, settled in USDC on Base via x402.

20 tools answering

Fintalio LinkedIn MCP

by fintalio

LinkedIn outreach MCP server — 19 tools for AI agents to prospect, sequence, and manage contacts.

answering

Kairon

by heykairon

Build prospecting lists from buying signals, enrich them, and run LinkedIn outreach.

answering

NVIDIA Elements

by nvidia

NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.

318 installs/wk local only

Vendo AI — questions

Answers built from our own checks of this server.

What can Vendo AI do?

It exposes 149 tools, read directly from the server on our last check. Among them: archive_campaign, buy_audience_set, connect_google_meet, connect_linkedin_account, connect_telegram_bot, create_agent and 143 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Vendo AI mostly used for?

Its tools cluster around sdr, crm and preview. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Vendo AI working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 22 of 22 checks got a reply (100.0%), average response time 179 ms. The bar chart above shows every period we have measured.

How do I connect Vendo AI?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Vendo AI need an API key?

No. Vendo AI completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 149 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Vendo AI?

It answers our handshake in 179 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.