Dalil is now Vetta. Read the storyThe story

Vetta

Vetta MCP

Run your sales from Claude.

Vetta MCP hands Claude, ChatGPT, Cursor and any MCP client 95+ tools on your workspace. Find leads, write and run the outreach, read every reply, report on the pipeline, keep tasks moving and set up the CRM itself, all from one chat.

Book a demoConnect in a minute

Included in every plan. Works with Claude, ChatGPT, Cursor and more.

One prompt, four tools
ClaudeVetta MCP · connected · 95+ tools

Reply to Claude

Vetta MCPClaude Opus 5.5
native tools
95+
tool groups
9
channels: email, LinkedIn, WhatsApp
3
URL, no API key
1

What it can do

Ask for the outcome. It picks the tools.

You never name a tool. Describe the job the way you would to a colleague and the client chains the calls itself. Here are real requests across the whole sales motion, with every call they make.

Describe who you sell to. The agent turns it into signals and an ICP, and explains itself when it finds nobody.

Build a scouting agent from one sentence

8 tool calls

Build a Lead Scout agent that finds Heads of RevOps at 50 to 500 person SaaS companies in the UK and Germany who talk about CRM migrations or are hiring SDRs.

  1. manage_business_context_documentRead “What we sell”, 2,140 words
  2. vet_lead_scout_keyword12 keywords measured, 7 with real comment volume
  3. create_lead_scout_agentRevOps scout created
  4. create_scout_sourceScout linked to your business context
  5. upsert_lead_scout_signal9 signals: 7 keywords, 1 competitor, hiring SDRs
  6. search_lead_scout_icp_optionsMatched “Software Development”, “IT Services”
  7. upsert_lead_scout_icpHead of RevOps · 51 to 500 · UK, Germany
  8. finalize_lead_scout_agentScouting ready, outreach not set up

RevOps scout is set up with 9 active signals and starts scanning on its next cycle. I dropped 5 keywords that get posts but almost no comments, like “revenue operations framework”, because the scout finds people in the comment sections. One thing before anyone is contacted: its sequence has no messages or sender yet. Want me to build the outreach?

Find out why an agent went quiet

3 tool calls

Why has the Fintech founders agent found nobody this week?

  1. get_lead_scout_agentActive · 11 signals · last run 3h ago
  2. get_lead_scout_runs6 runs · 1,284 people examined · 0 new leads
  3. get_lead_scout_analysis71% rejected on the location check

The signals are working: six runs read 1,284 people in the comments. The ICP is turning them away. 71% failed on location, because it requires the company HQ to be in the UK and most of these founders run Delaware companies from London. Switching the location check from company HQ to where the person lives would have kept 38 of them. Should I change it?

People, companies and figures in these examples are illustrative. The tools and what they do are real.

The tool catalog

95+ tools, discovered on connect.

Your AI client reads this list the moment it connects, so you never have to learn it. It is here so you can see exactly what it can reach.

Reads only Reads only 31Changes something Changes something 66

Lead finding

Build Lead Scout agents that watch LinkedIn for buying signals, then judge and tune what they find.

18 tools · 7 read · 11 change

  • Changes something

    Create a lead agent and the sequence it feeds

    create_lead_scout_agent
  • Changes something

    Give the agent a scout, tied to your business context

    create_scout_source
  • Changes something

    Add or edit a signal: keyword, competitor, creator, job change, hiring

    upsert_lead_scout_signal
  • Changes something

    Set the ICP: roles, industries, company size, locations, exclusions

    upsert_lead_scout_icp
  • Reads only

    Look up the exact roles, industries and locations LinkedIn accepts

    search_lead_scout_icp_options
  • Reads only

    Measure whether a keyword will surface real conversations before using it

    vet_lead_scout_keyword
  • Changes something

    Validate the setup and mark the agent ready

    finalize_lead_scout_agent
  • Changes something

    Pause or activate an agent or one of its sources

    set_lead_scout_agent_status
  • Reads only

    Read an agent end to end, with a readiness verdict

    get_lead_scout_agent
  • Reads only

    List leads with fit and intent bands and the post that surfaced them

    get_lead_scout_leads
  • Changes something

    Sample the leads the current ICP would find

    preview_lead_scout_leads
  • Changes something

    Scan one signal now instead of waiting for its turn

    run_lead_scout_signal
  • Reads only

    Read each run as a funnel: posts, comments, people, leads

    get_lead_scout_runs
  • Reads only

    When each signal runs next, and why it is waiting

    get_lead_scout_schedule
  • Reads only

    Why a signal is or is not producing leads, and what the ICP rejects

    get_lead_scout_analysis
  • Changes something

    Turn people already in the CRM into an agent’s leads

    add_people_to_lead_agent
  • Changes something

    Enrol an agent’s leads into its sequence

    enroll_lead_scout_person
  • Changes something

    Restore a lead the agent was told to never surface again

    clear_lead_scout_tombstone

Read-only tools are marked so your client can run them without asking. Everything else runs as you, in the workspace you signed into. Raw HTTP requests and the sandboxed code interpreter are deliberately not exposed; they stay inside Vetta’s own agents.

Built for agents

Safe to hand a model the keys.

Most CRM servers wrap their API and hope the model reads the docs. Vetta’s tools carry the rules with them, so the client knows what costs money, what goes out to a lead and what is still unfinished.

One Vetta guide checks the other’s harness and locked carabiners before handing over the rope
01

Drafts first, sends on purpose

Drafting and sending are separate tools, and new sequences start as drafts. Nothing goes out to a lead until you say publish or send.

02

It reports readiness, not just success

Agents and sequences come back with a plain verdict: will this find anyone, will anyone be contacted, and what is still missing.

03

Spend is announced before it happens

Tools that use credits or add a paid scout say so in their contract, so your client tells you before calling them.

04

The rulebook is built in

A knowledge base tool explains how the engine actually behaves. Clients read it before building, so sequences and agents come out right the first time.

05

Scoped to you and your workspace

You sign in with your Vetta account. Every call runs with your permissions, in that workspace only, and moving to another one is an explicit switch.

06

Read-only tools are marked

Clients can run lookups and reports freely and ask before anything that writes. Raw HTTP and code execution are not exposed at all.

Compared

Other MCP servers cover half the motion.

CRMs expose their records. Outreach tools expose their campaigns. Vetta MCP covers the whole climb from one server: finding the lead, writing to them, reading the reply, moving the deal and automating what comes next.

  • HubSpot

    CRM

    Where they are strong

    The broadest ecosystem, and its MCP can create pipelines and properties as well as records.

    Why teams pick Vetta

    HubSpot’s MCP stops at the CRM and reads its inbox. Vetta’s also finds new leads, builds and runs email, LinkedIn and WhatsApp sequences, and builds workflow automations.

  • Attio

    CRM

    Where they are strong

    A flexible data model, with meeting transcripts and semantic search over email and notes.

    Why teams pick Vetta

    Attio’s MCP has no outreach and no LinkedIn or WhatsApp. Vetta’s finds the leads, writes to them on three channels, reads every reply and can reshape the CRM’s fields too.

  • lemlist

    Outreach

    Where they are strong

    The benchmark for multichannel sequences, with deliverability and warm-up tools in its MCP.

    Why teams pick Vetta

    lemlist’s MCP has contacts but no deals or pipelines. In Vetta the reply, the deal, its tasks and notes live behind the same server, so one prompt can act on all of them.

  • Apollo

    Data and outreach

    Where they are strong

    The largest contact database here, with enrichment and buying intent behind it.

    Why teams pick Vetta

    Apollo’s LinkedIn steps are manual tasks and its MCP reads no conversations. Vetta’s agents find people by what they post and comment on, then run LinkedIn and WhatsApp outreach and read the replies.

  • HeyReach

    LinkedIn outreach

    Where they are strong

    LinkedIn outreach at scale across many sender accounts, built and launched from a prompt.

    Why teams pick Vetta

    HeyReach covers LinkedIn only and is not a CRM. Vetta adds email, WhatsApp, the pipeline and workflow automations, and connects with a normal sign-in instead of a workspace key.

Capability by capability

What each vendor’s MCP server lets an AI client do
MCP server canVettaAI Sales OSHubSpotCRMAttioCRMlemlistOutreachApolloData and outreachHeyReachLinkedIn outreach
Connection
Hosted MCP server, built by the vendor
Yes
Yes
Yes
Yes
Yes
Yes
Sign in with OAuth, no key to paste
Yes
Yes
Yes
Yes
Yes
Not in its MCPWorkspace MCP key
Lead finding
Finds new leads
YesSignal agents on LinkedIn
PartlyIntent signals on known records
Not in its MCP
YesLead database search
YesContact database search
Not in its MCP
Outreach
Builds outreach sequences
YesEmail, LinkedIn, WhatsApp
Not in its MCP
Not in its MCP
YesMultichannel
PartlyEmail; LinkedIn steps are manual tasks
PartlyLinkedIn only
Writes the copy for each lead
YesFrom the signal behind each lead
Not in its MCP
Not in its MCP
YesAI variables
Not in its MCP
Not in its MCP
Conversations
Reads conversations
YesEmail, LinkedIn, WhatsApp
YesHubSpot inbox
PartlyEmail
YesCampaign replies
Not in its MCP
YesLinkedIn replies
Meeting notes and transcripts
Yes
PartlyMeeting records
Yes
Not in its MCP
Not in its MCP
Not in its MCP
CRM
Records, tasks and notes
Yes
Yes
Yes
PartlyContacts and companies
PartlyContacts, deals, tasks
Not in its MCPNot a CRM
Moves deals through pipelines
Yes
YesCan also create pipelines
Yes
Not in its MCP
PartlyCreate and view deals
Not in its MCP
Adds and edits custom fields
YesCreate, edit, delete
PartlyCreate
Not in its MCP
Not in its MCP
Not in its MCP
Not in its MCP
Automation
Builds and runs workflow automations
YesBuild, publish, run, debug
Not in its MCP
Not in its MCP
Not in its MCP
Not in its MCP
Not in its MCP
Reporting
Campaign analytics
YesFunnel, steps, reply sentiment
PartlyMarketing email
Not in its MCP
Yes
Not in its MCP
PartlyCampaign performance
Exposed in its MCP Partly Not in its MCP server, even where the product has it

Based on each vendor’s public MCP documentation, checked October 2026: HubSpot, Attio, lemlist, Apollo, HeyReach. MCP servers change fast. If something here is out of date, tell us and we will fix it.

Connect

One URL. No API key.

Add the URL to your client and sign in with your Vetta account. The client discovers every tool on its own, and you can start asking straight away.

https://api.usedalil.ai/mcp
  1. 1Add the URL as a custom connector or MCP server
  2. 2Sign in with your Vetta workspace
  3. 3Ask in plain language

Works with

  • Claude
  • Claude Code
  • ChatGPT
  • Cursor
  • Cline
  • Continue
  • Zed
  • any MCP client
  1. 1Open Settings → Connectors in claude.ai or Claude Desktop
  2. 2Click Add custom connector
  3. 3Name it Vetta and paste the URL
  4. 4Click Connect and sign in with your Vetta account

The same snippet lives in the app under Settings → AI → Set up MCP.

Questions

MCP, answered.

The full reference lives in the docs.

Seven days on the whole platform, free.

Invite your team, connect your channels and see real replies before your first invoice. If Vetta is not the right fit, cancel during the trial.

Book a demo

7 days free · Then $99 a month · Cancel anytime