MisarReach MCP Server

Official27 toolsLive

by Misar-AI · TypeScript

Find and enrich leads, run multi-channel outreach, and manage the sales pipeline.

MisarReach MCP Server (io.github.Misar-AI/misarreach-mcp)

The MisarReach MCP server supports lead-focused sales workflows: find leads, enrich and score them, run multi-channel outreach, and manage the sales pipeline “from any AI assistant.” It is provided as an MCP server with 27 tools, alongside prompts and resources, and is listed for use with major AI editors and assistants.

🛠️ Key Features

Lead finding, enrichment, and scoring
Multi-channel outreach
Sales pipeline management
27 tools (plus 5 prompts, 4 resources, 4 agent skills)
Mentions compatibility with Claude and Cursor

🚀 Use Cases

Prospecting and lead generation
Cold email and outreach execution
Sales automation and CRM-adjacent pipeline handling

⚡ Developer Benefits

Model Context Protocol (MCP) server for automation workflows
Tooling count: 27
Topics indicate areas such as deliverability, email verification, and TypeScript

⚠️ Limitations

Source material only specifies capabilities at a high level; it does not define tool behavior or integration depth beyond named assistants (Claude, Cursor)

Topics

ai-agentautomationclaudecrmlead-generationmcpmcp-servermodel-context-protocoloutreachsalesaicold-emailcursordeliverabilityemail-verificationprospectingsales-automationtypescriptmisarreach

Captured live from the server via tools/list.

list_leads

List leads already saved to the account, newest first, with paging and search. Use this to work with leads you already have. It does NOT find new ones — that is search_leads, which starts a job and costs credits. Narrow to one search job with job_id when you want just that job's results. Reads only and costs no credits. Requires an API key. Returns saved lead records with contact and company fields plus enrichment and score where present. An empty page is a normal answer, not an error.

Parameters4

page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20, max 100)
search	string	optional	Search term to filter by name, email, or company
job_id	string	optional	Filter leads by a specific search job UUID

Raw schema

{
  "type": "object",
  "properties": {
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20, max 100)"
    },
    "search": {
      "type": "string",
      "description": "Search term to filter by name, email, or company"
    },
    "job_id": {
      "type": "string",
      "description": "Filter leads by a specific search job UUID"
    }
  }
}

search_leads

Start an AI lead-search job and return its jobId immediately. This is ASYNCHRONOUS: results are not in the response. Poll get_search_job_status with the jobId until it reports completion, then read the leads with list_leads filtered by that job_id. Use it to find NEW leads; use list_leads for ones already saved. CONSUMES SEARCH CREDITS on every call, and each call starts a separate job — do not retry it as a way to check progress. Requires an API key. Setting useAI additionally spends AI credits to enrich and score the results as they arrive.

Parameters3

query	string	required	Search query describing the ideal lead (2-200 chars)
useAI	boolean	optional	Use AI to enrich and score results (default false)
filters	object	optional	Optional filters

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query describing the ideal lead (2-200 chars)"
    },
    "useAI": {
      "type": "boolean",
      "description": "Use AI to enrich and score results (default false)"
    },
    "filters": {
      "type": "object",
      "description": "Optional filters",
      "properties": {
        "location": {
          "type": "string",
          "description": "Geographic location"
        },
        "role": {
          "type": "string",
          "description": "Job title or role"
        },
        "industry": {
          "type": "string",
          "description": "Industry sector"
        },
        "companySize": {
          "type": "string",
          "description": "Company size range (e.g. '10-50')"
        }
      }
    }
  },
  "required": [
    "query"
  ]
}

get_search_job_status

Poll one lead-search job for its progress and results. This is the companion to search_leads: call it repeatedly with the jobId you were given until the job reports it has finished. Leave a few seconds between polls — searches take a while, and polling harder does not make them faster. Reads only and costs no credits, however many times you call it. Requires an API key. Returns the run state, progress, and the leads found so far; a job still running is a normal answer, not an error.

Parameters1

jobId

string

required

Lead search job UUID

Raw schema

{
  "type": "object",
  "properties": {
    "jobId": {
      "type": "string",
      "description": "Lead search job UUID"
    }
  },
  "required": [
    "jobId"
  ]
}

submit_lead_feedback

Record whether an AI-generated outreach message for a lead was good or bad, as training signal for future generations. Use it when the user judges a drafted message — it improves later output rather than changing anything now. It does not edit, resend, or delete the message, and it sends nothing to the lead. Writes a feedback record; sending the same verdict twice is harmless. Requires an API key. Costs no credits.

Parameters3

jobId	string	required	Lead search job UUID
leadEmail	string	required	Email address of the lead
feedback	string	required	Feedback sentiment

Raw schema

{
  "type": "object",
  "properties": {
    "jobId": {
      "type": "string",
      "description": "Lead search job UUID"
    },
    "leadEmail": {
      "type": "string",
      "description": "Email address of the lead"
    },
    "feedback": {
      "type": "string",
      "enum": [
        "positive",
        "negative"
      ],
      "description": "Feedback sentiment"
    }
  },
  "required": [
    "jobId",
    "leadEmail",
    "feedback"
  ]
}

discover_companies

Find COMPANIES matching firmographic criteria via Hunter.io, optionally pulling contact emails for each. This is company-level discovery — reach for it when the user is targeting organisations by industry, location, headcount or tech stack. When they want named people, use search_leads. Filters combine with AND, so stacking many narrows results sharply. Requires an API key. Setting fetch_emails=true performs email lookups and COSTS CREDITS; leaving it false is a plain company search. Returns matching companies with firmographics. No lead is saved to the account by this call.

Parameters8

query	string	optional	Free-text company search query
industry	array	optional	Industry filters (max 10)
location	array	optional	Location filters (max 10)
headcount_min	number	optional	Minimum employee count
headcount_max	number	optional	Maximum employee count
technology	array	optional	Technology stack filters (max 10)
fetch_emails	boolean	optional	Also fetch contact emails for discovered companies (default false)
limit	number	optional	Max companies to return (1-100, default 20)

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text company search query"
    },
    "industry": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Industry filters (max 10)"
    },
    "location": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Location filters (max 10)"
    },
    "headcount_min": {
      "type": "number",
      "description": "Minimum employee count"
    },
    "headcount_max": {
      "type": "number",
      "description": "Maximum employee count"
    },
    "technology": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Technology stack filters (max 10)"
    },
    "fetch_emails": {
      "type": "boolean",
      "description": "Also fetch contact emails for discovered companies (default false)"
    },
    "limit": {
      "type": "number",
      "description": "Max companies to return (1-100, default 20)"
    }
  }
}

enrich_lead

Fill in a saved lead's missing person and company detail — seniority, department, LinkedIn, phone, company size, industry. Use it on one lead at a time, after list_leads has given you its id, and typically before writing outreach that needs context. Check the lead first: enriching one that already has these fields spends credits for nothing. CONSUMES ENRICHMENT CREDITS per call. Requires an API key. Updates the stored lead in place and returns it; it does not create a new record, and running it twice does not duplicate the lead — but it does bill twice.

Parameters1

leadId

string

required

Lead UUID from list_leads

Raw schema

{
  "type": "object",
  "properties": {
    "leadId": {
      "type": "string",
      "description": "Lead UUID from list_leads"
    }
  },
  "required": [
    "leadId"
  ]
}

verify_emails

Check whether email addresses are deliverable, one or up to 20 at a time. Run this before a send to protect sender reputation — bouncing a campaign off dead addresses is what gets a domain blocked. Pass either `email` for one or `emails` for a batch, not both. CONSUMES VERIFICATION CREDITS per address checked, so a 20-address batch costs 20. Requires an API key. Returns a deliverability verdict per address; 'undeliverable' is a successful result, not an error. Nothing is sent to the addresses.

Parameters2

email	string	optional	Single email to verify (use this OR emails array)
emails	array	optional	Batch of emails to verify (max 20)

Raw schema

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "Single email to verify (use this OR emails array)"
    },
    "emails": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Batch of emails to verify (max 20)"
    }
  }
}

score_leads

Queue AI qualification scoring for leads — either every unscored lead in a search job, or a specific set of ids. Pass jobId OR leadIds, not both. This runs in the BACKGROUND: it returns a count immediately and the scores appear on the leads afterwards, so re-read them with list_leads rather than expecting scores in this response. CONSUMES AI CREDITS per lead scored. Requires an API key. Passing leadIds rescores leads even if they already have a score, which bills again — pass jobId to score only what is unscored. Caps at 200 ids per call.

Parameters2

jobId	string	optional	Score all unscored leads for this job UUID (use this OR leadIds)
leadIds	array	optional	Specific lead UUIDs to (re)score (max 200, use this OR jobId)

Raw schema

{
  "type": "object",
  "properties": {
    "jobId": {
      "type": "string",
      "description": "Score all unscored leads for this job UUID (use this OR leadIds)"
    },
    "leadIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Specific lead UUIDs to (re)score (max 200, use this OR jobId)"
    }
  }
}

list_lead_lists

List the Hunter.io lead lists connected to this account. Use it to find a listId before sync_lead_list, or to check whether a list already exists before create_lead_list makes a duplicate. These are Hunter.io's lists, which are separate from the leads stored locally — list_leads shows those. Reads only, costs no credits, takes no parameters. Requires an API key and a connected Hunter.io account. An empty result means no lists exist yet.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

create_lead_list

Create a new, empty lead list in Hunter.io. Creating the list does not put anything in it, and it does not import anything locally — sync_lead_list does that. Call list_lead_lists first: each call creates a NEW list and nothing deduplicates by name. Requires an API key and a connected Hunter.io account. Costs no credits. Returns the created list with the id that sync_lead_list needs.

Parameters1

name

string

required

List name (1-200 chars)

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "List name (1-200 chars)"
    }
  },
  "required": [
    "name"
  ]
}

sync_lead_list

Import a Hunter.io lead list into local lead records so the rest of these tools can work with it. Run it after create_lead_list, or on any existing list from list_lead_lists, to pull its contacts in. Until a list is synced its contacts are invisible to list_leads, enrich_lead and send_to_campaign. Writes local lead records. Re-syncing the same list refreshes rather than duplicating, so it is safe to repeat. Requires an API key and a connected Hunter.io account. Costs no credits; enrichment and verification are billed separately.

Parameters1

listId

string

required

Hunter.io list ID (integer as string)

Raw schema

{
  "type": "object",
  "properties": {
    "listId": {
      "type": "string",
      "description": "Hunter.io list ID (integer as string)"
    }
  },
  "required": [
    "listId"
  ]
}

preview_message

Draft a sample AI-personalised outreach message for a named person, to show what the agent would say. This is a PREVIEW: nothing is sent, saved, or attached to a lead or campaign. Use it to check tone before committing to a sequence. The person does not need to exist as a lead — pass their name and, if known, role and company. This is the one tool here that needs no API key. Generative, so the same input yields different wording each time. Returns the drafted message text.

Parameters3

name	string	required	Person's full name (1-100 chars)
role	string	optional	Job title or role (optional, max 100 chars)
company	string	optional	Company name (optional, max 100 chars)

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Person's full name (1-100 chars)"
    },
    "role": {
      "type": "string",
      "description": "Job title or role (optional, max 100 chars)"
    },
    "company": {
      "type": "string",
      "description": "Company name (optional, max 100 chars)"
    }
  },
  "required": [
    "name"
  ]
}

send_to_campaign

Add saved leads to a campaign's contact list in bulk, up to 500 at a time. This is how leads enter an outreach sequence, so treat it as consequential: once they are on a running campaign's list they can start receiving messages. It does NOT send anything by itself and does not start the campaign — but it removes the last step before the campaign does. Every lead must belong to the authenticated account, or the call fails. Adding a lead already on the list does not duplicate it. Requires an API key. Verify addresses with verify_emails first; importing dead ones damages sender reputation.

Parameters3

leadIds	array	required	Lead UUIDs to import (1-500)
campaignId	string	required	Target campaign UUID
listId	string	optional	Target contact list UUID (defaults to campaign's own list)

Raw schema

{
  "type": "object",
  "properties": {
    "leadIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Lead UUIDs to import (1-500)"
    },
    "campaignId": {
      "type": "string",
      "description": "Target campaign UUID"
    },
    "listId": {
      "type": "string",
      "description": "Target contact list UUID (defaults to campaign's own list)"
    }
  },
  "required": [
    "leadIds",
    "campaignId"
  ]
}

list_deals

List deals as a flat, paged array, optionally filtered by status, with revenue totals alongside. Use this when you want deals as data — to count them, filter one status, or page through many. For the board view with deals grouped into stages, use get_pipeline instead; the two return the same deals in different shapes. Reads only. Requires an API key. Returns the deals plus a summary of total, closed and open pipeline revenue. Money is in minor currency units (cents), so divide by 100 before showing it.

Parameters3

status	string	optional	Filter by deal status (e.g. new, contacted, interested, meeting, proposal, closed, lost)
limit	number	optional	Max results (default 50, max 100)
offset	number	optional	Pagination offset (default 0)

Raw schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Filter by deal status (e.g. new, contacted, interested, meeting, proposal, closed, lost)"
    },
    "limit": {
      "type": "number",
      "description": "Max results (default 50, max 100)"
    },
    "offset": {
      "type": "number",
      "description": "Pagination offset (default 0)"
    }
  }
}

create_deal

Open a new deal against a lead's email address. Use it when a conversation turns into a real opportunity worth tracking. Each call creates a NEW deal — it does not check for an existing one on the same email, so list_deals first if you might be duplicating. To change a deal that exists, use update_deal. Requires an API key. `value` is in MINOR CURRENCY UNITS — 2500 means $25.00, not $2500 — and defaults to 0 with currency USD. Returns the created deal, which enters the pipeline at the first stage.

Parameters8

leadEmail	string	required	Lead's email address
leadName	string	optional	Lead's display name
value	number	optional	Deal value in minor currency units (default 0)
currency	string	optional	ISO 4217 currency code (default USD)
notes	string	optional	Deal notes (max 5000 chars)
conversationId	string	optional	UUID of associated conversation
campaignId	string	optional	UUID of associated campaign
contactId	string	optional	UUID of associated contact

Raw schema

{
  "type": "object",
  "properties": {
    "leadEmail": {
      "type": "string",
      "description": "Lead's email address"
    },
    "leadName": {
      "type": "string",
      "description": "Lead's display name"
    },
    "value": {
      "type": "number",
      "description": "Deal value in minor currency units (default 0)"
    },
    "currency": {
      "type": "string",
      "description": "ISO 4217 currency code (default USD)"
    },
    "notes": {
      "type": "string",
      "description": "Deal notes (max 5000 chars)"
    },
    "conversationId": {
      "type": "string",
      "description": "UUID of associated conversation"
    },
    "campaignId": {
      "type": "string",
      "description": "UUID of associated campaign"
    },
    "contactId": {
      "type": "string",
      "description": "UUID of associated contact"
    }
  },
  "required": [
    "leadEmail"
  ]
}

update_deal

Change a deal's status, value, or notes. Only the fields you pass are altered. For moving a deal along the pipeline board prefer move_deal_stage, which is the same operation expressed in stage terms; use this one for value and notes. Setting status to 'closed' or 'lost' marks the deal resolved and takes it out of open pipeline revenue. Safe to repeat — the same call twice leaves the same deal. Requires an API key, and the account must own the deal. `value` is in MINOR CURRENCY UNITS (2500 = $25.00). Notes REPLACE the existing note rather than appending.

Parameters4

dealId	string	required	Deal UUID
status	string	optional	New deal status
value	number	optional	Updated deal value in minor currency units
notes	string	optional	Updated deal notes (max 5000 chars)

Raw schema

{
  "type": "object",
  "properties": {
    "dealId": {
      "type": "string",
      "description": "Deal UUID"
    },
    "status": {
      "type": "string",
      "enum": [
        "interested",
        "meeting",
        "proposal",
        "closed",
        "lost"
      ],
      "description": "New deal status"
    },
    "value": {
      "type": "number",
      "description": "Updated deal value in minor currency units"
    },
    "notes": {
      "type": "string",
      "description": "Updated deal notes (max 5000 chars)"
    }
  },
  "required": [
    "dealId"
  ]
}

get_pipeline

Get the sales pipeline as a board: deals grouped by stage, with revenue totals. Use this for 'how does the pipeline look' questions and stage-by-stage review. It is the board view of the same deals list_deals returns flat — reach for that one when you need filtering or paging, since this returns the whole board. Reads only. Requires an API key. Stages are new, contacted, interested, meeting, proposal, closed and lost. Money is in minor currency units (cents), so divide by 100 before showing it.

Parameters1

workspaceId

string

optional

Optional workspace UUID to filter pipeline

Raw schema

{
  "type": "object",
  "properties": {
    "workspaceId": {
      "type": "string",
      "description": "Optional workspace UUID to filter pipeline"
    }
  }
}

move_deal_stage

Move one deal to a different pipeline stage — the equivalent of dragging its card on the board. This is the tool for pipeline progression; update_deal is for value and notes. Moving to 'closed' or 'lost' resolves the deal and removes it from open pipeline revenue, which changes reported figures — only do it when the user says the outcome is settled. Safe to repeat: moving a deal to the stage it is already in changes nothing. Stages are not ordered by this call, so it can move a deal backwards as easily as forwards. Requires an API key.

Parameters2

dealId	string	required	Deal UUID
newStage	string	required	Target stage

Raw schema

{
  "type": "object",
  "properties": {
    "dealId": {
      "type": "string",
      "description": "Deal UUID"
    },
    "newStage": {
      "type": "string",
      "enum": [
        "new",
        "contacted",
        "interested",
        "meeting",
        "proposal",
        "closed",
        "lost"
      ],
      "description": "Target stage"
    }
  },
  "required": [
    "dealId",
    "newStage"
  ]
}

start_autopilot

Start an autonomous outreach run: give the agent a goal and it finds, contacts and follows up with leads on its own. This is the most consequential tool on this server. It is FIRE-AND-FORGET and it SENDS REAL MESSAGES TO REAL PEOPLE without returning for approval, so only start a run when the user has explicitly asked for one and understands the goal as written — the goal text is the entire brief. It returns a runId immediately; watch progress with get_autopilot_status. CONSUMES AUTOPILOT CREDITS, plus search, enrichment and AI credits as it works. Requires an API key. Each call starts a SEPARATE run — calling twice runs two campaigns concurrently against the same goal.

Parameters2

goal	string	required	Outreach goal description (10-500 chars). E.g. 'Find and email 10 SaaS startup CTOs in London about our product'
workspace_id	string	optional	Optional workspace UUID to associate with this run

Raw schema

{
  "type": "object",
  "properties": {
    "goal": {
      "type": "string",
      "description": "Outreach goal description (10-500 chars). E.g. 'Find and email 10 SaaS startup CTOs in London about our product'"
    },
    "workspace_id": {
      "type": "string",
      "description": "Optional workspace UUID to associate with this run"
    }
  },
  "required": [
    "goal"
  ]
}

list_autopilot_runs

List past and running autopilot runs with their status and result summaries. Use it to review what has already been run — and to check for a run already in flight before start_autopilot launches a second one against the same goal. For detail on one run, use get_autopilot_status. Reads only, costs no credits, and starts nothing. Requires an API key. Returns runs newest first with paging.

Parameters2

limit	number	optional	Max results (default 20)
offset	number	optional	Pagination offset

Raw schema

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max results (default 20)"
    },
    "offset": {
      "type": "number",
      "description": "Pagination offset"
    }
  }
}

get_autopilot_status

Get the current progress and results of one autopilot run. This is how you follow a run started by start_autopilot: call it with the runId, leaving time between polls. Reading status does not pause, stop, or alter the run in any way — it keeps going regardless, and there is no tool here to stop it. Reads only and costs no credits, however often you call it. Requires an API key. A run still in progress is a normal answer, not an error.

Parameters1

runId

string

required

Autopilot run UUID

Raw schema

{
  "type": "object",
  "properties": {
    "runId": {
      "type": "string",
      "description": "Autopilot run UUID"
    }
  },
  "required": [
    "runId"
  ]
}

get_channels_status

Report the configuration, connection state and delivery stats for every outreach channel — WhatsApp, SMS and push. Check this before relying on a channel: a disabled or unconfigured one silently delivers nothing. It is also the natural first step before update_channel, so you know the current state rather than toggling blind. Reads only, takes no parameters, and changes nothing. Requires an API key. Returns each channel with whether it is enabled, whether credentials are configured, and recent delivery counts.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

update_channel

Turn one outreach channel on or off — WhatsApp, SMS or push. This changes how the account actually delivers messages, so it affects live campaigns and autopilot runs, not just future ones. DISABLING a channel silently stops delivery over it; enabling one that has no credentials configured will not make it work. Call get_channels_status first to see where things stand. Handles one channel per call. Safe to repeat: setting a channel to the state it is already in changes nothing. Requires an API key.

Parameters2

channel	string	required	Channel to update
enabled	boolean	required	Whether to enable (true) or disable (false) the channel

Raw schema

{
  "type": "object",
  "properties": {
    "channel": {
      "type": "string",
      "enum": [
        "whatsapp",
        "sms",
        "push"
      ],
      "description": "Channel to update"
    },
    "enabled": {
      "type": "boolean",
      "description": "Whether to enable (true) or disable (false) the channel"
    }
  },
  "required": [
    "channel",
    "enabled"
  ]
}

get_sales_agent_config

Fetch the AI sales agent's current settings: whether it is enabled, its booking link, offer price, reply limits and confidence threshold. Read this before update_sales_agent_config so you change one field without clobbering the rest, and to check whether the agent is enabled at all before expecting it to act. Reads only, takes no parameters, changes nothing. Requires an API key. Returns the configuration for the authenticated account.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

update_sales_agent_config

Change the AI sales agent's settings — enable or disable it, set the booking link, offer price, reply limits and confidence threshold. These settings govern an agent that replies to real prospects, so treat them as live: ENABLING it lets it start responding on its own, the confidence threshold decides how sure it must be before acting, and reply limits cap how much it can send. Read the current config first — only the fields you pass change, but a wrong value takes effect immediately. Safe to repeat. Requires an API key.

Parameters6

enabled	boolean	optional	Enable or disable the sales agent
cal_link	string	optional	Calendly or Cal.com URL for meeting booking (max 500 chars, set null to clear)
offer_price	number	optional	Offer price in minor currency units (integer, min 0)
offer_description	string	optional	Short description of the offer (max 1000 chars, set null to clear)
max_replies_per_day	number	optional	Maximum automated replies per day (1-500, default 20)
confidence_threshold	number	optional	Confidence score below which agent flags for human review (0.0-1.0, default 0.65)

Raw schema

{
  "type": "object",
  "properties": {
    "enabled": {
      "type": "boolean",
      "description": "Enable or disable the sales agent"
    },
    "cal_link": {
      "type": "string",
      "description": "Calendly or Cal.com URL for meeting booking (max 500 chars, set null to clear)"
    },
    "offer_price": {
      "type": "number",
      "description": "Offer price in minor currency units (integer, min 0)"
    },
    "offer_description": {
      "type": "string",
      "description": "Short description of the offer (max 1000 chars, set null to clear)"
    },
    "max_replies_per_day": {
      "type": "number",
      "description": "Maximum automated replies per day (1-500, default 20)"
    },
    "confidence_threshold": {
      "type": "number",
      "description": "Confidence score below which agent flags for human review (0.0-1.0, default 0.65)"
    }
  }
}

get_sales_agent_actions

Get what the AI sales agent has done today, with summary stats — actions taken, deals created, replies sent. This is the audit trail: use it to see what the agent did on the account's behalf, and to sanity-check its behaviour after enabling it. Covers TODAY only, so it is not the tool for historical reporting. Reads only and changes nothing; it does not approve or undo any action. Requires an API key. No actions today is a normal answer, not an error.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

process_sales_agent

Run the sales-agent pipeline over one conversation: decide the next action and carry it out. This ACTS on a real conversation — depending on what it decides, it can reply to the prospect, create a deal, or book a meeting. It is not a dry run and there is no preview, so call it only when the user wants the agent to take its turn on that specific conversation. For what it has already done, use get_sales_agent_actions. CONSUMES AI CREDITS. Not idempotent: calling twice processes the conversation twice and can send two messages. Requires an API key, and the agent's configured confidence threshold still governs whether it acts.

Parameters1

conversationId

string

required

UUID of the conversation to process

Raw schema

{
  "type": "object",
  "properties": {
    "conversationId": {
      "type": "string",
      "description": "UUID of the conversation to process"
    }
  },
  "required": [
    "conversationId"
  ]
}

README.md8 KBView on GitHub

MisarReach MCP Server

Find leads, enrich and score them, run multi-channel outreach, and manage the sales pipeline — from any AI assistant.

31 tools · 5 prompts · 4 resources · 4 agent skills

Works with Claude (Desktop, Code, and web), Cursor, VS Code, Windsurf, Cline, Zed, Gemini CLI, ChatGPT, and any other MCP-compatible client — over stdio or Streamable HTTP.

Install

Smithery (recommended)

bash

npx -y @smithery/cli install misar/misarreach-mcp --client claude

Claude Code

bash

claude mcp add misarreach -- npx -y @misarreach/mcp@latest

Manual (any client)

json

{
  "mcpServers": {
    "misarreach": {
      "command": "npx",
      "args": ["-y", "@misarreach/mcp@latest"],
      "env": { "MISARREACH_API_KEY": "mrk_your_key_here" }
    }
  }
}

Ready-made configs for every client live in connectors/.

Remote (no install)

json

{
  "mcpServers": {
    "misarreach": {
      "type": "streamable-http",
      "url": "https://api.misar.io/reach/mcp",
      "headers": { "Authorization": "Bearer mrk_your_key_here" }
    }
  }
}

Authentication

Two options — no copy-paste needed for the first:

Browser login. Start the server with no key and run the login tool. It opens the MisarReach consent screen, you review the requested permissions, and the key is delivered straight back and saved to ~/.misarreach/config.json.
API key. Create one at https://reach.misar.io/settings/api-keys and set MISARREACH_API_KEY.

Self-hosted instances: set MISARREACH_BASE_URL.

Tools

Tool	Description
`list_leads`	List leads already saved to the account, newest first, with paging and search.
`search_leads`	Start an AI lead-search job and return its jobId immediately.
`get_search_job_status`	Poll one lead-search job for its progress and results.
`submit_lead_feedback`	Record whether an AI-generated outreach message for a lead was good or bad, as training signal for future generations.
`discover_companies`	Find COMPANIES matching firmographic criteria, optionally pulling contact emails for each.
`enrich_lead`	Fill in a saved lead's missing person and company detail — seniority, department, LinkedIn, phone, company size, industry.
`verify_emails`	Check whether email addresses are deliverable, one or up to 20 at a time.
`score_leads`	Queue AI qualification scoring for leads — either every unscored lead in a search job, or a specific set of ids.
`list_lead_lists`	List the managed lead lists this account has created or synced.
`create_lead_list`	Create a new, empty managed lead list.
`sync_lead_list`	Import a managed lead list into local lead records so the rest of these tools can work with it.
`preview_message`	Draft a sample AI-personalised outreach message for a named person, to show what the agent would say.
`send_to_campaign`	Add saved leads to a campaign's contact list in bulk, up to 500 at a time.
`list_deals`	List deals as a flat, paged array, optionally filtered by status, with revenue totals alongside.
`create_deal`	Open a new deal against a lead's email address.
`update_deal`	Change a deal's status, value, or notes.
`get_pipeline`	Get the sales pipeline as a board: deals grouped by stage, with revenue totals.
`move_deal_stage`	Move one deal to a different pipeline stage — the equivalent of dragging its card on the board.
`start_autopilot`	Start an autonomous outreach run: give the agent a goal and it finds, contacts and follows up with leads on its own.
`list_autopilot_runs`	List past and running autopilot runs with their status and result summaries.
`get_autopilot_status`	Get the current progress and results of one autopilot run.
`get_channels_status`	Report the configuration, connection state and delivery stats for every outreach channel — WhatsApp, SMS and push.
`update_channel`	Turn one outreach channel on or off — WhatsApp, SMS or push.
`get_sales_agent_config`	Fetch the AI sales agent's current settings: whether it is enabled, its booking link, offer price, reply limits and confidence threshold.
`update_sales_agent_config`	Change the AI sales agent's settings — enable or disable it, set the booking link, offer price, reply limits and confidence threshold.
`get_sales_agent_actions`	Get what the AI sales agent has done today, with summary stats — actions taken, deals created, replies sent.
`process_sales_agent`	Run the sales-agent pipeline over one conversation: decide the next action and carry it out.
`search_verified_leads`	Find people or businesses matching a plain-language description and return only leads with a real way to reach them (email, phone or LinkedIn), each read from a real record — never generated.
`reveal_company_contacts`	Read a company's own website now and return what it publishes: contact emails, a phone number, its social profiles and its detected tech stack.
`company_email_format`	The email address format a company uses (e.g.
`verify_email`	Check whether one email address can receive mail.

Prompts

Reusable workflows your client exposes as slash-commands.

Prompt	Description
`build_lead_list`	Find, enrich, verify and score a target lead list before any outreach.
`outreach_sequence`	Design and preview a multi-channel sequence, sending only after approval.
`pipeline_review`	Review deal pipeline health and recommend the next actions.
`autopilot_audit`	Check what autopilot has been doing and whether it should keep running.
`sales_agent_tuning`	Review the AI sales agent's configuration and recent actions.

Resources

Read-only context an agent can attach without spending a tool call.

URI	Description
`misarreach://channels`	Which outreach channels are connected and healthy.
`misarreach://lead-lists`	Your saved lead lists with sizes, so a campaign targets a real audience..
`misarreach://pipeline`	Current pipeline by stage — the baseline for any performance question..
`misarreach://autopilot/status`	Whether autopilot is running, and its current sending posture..

Agent skills

Bundled in skills/ — guidance an agent loads when a task matches.

Skill	Use when
`audit-autopilot-and-agent`	Check what MisarReach autopilot and the AI sales agent have been doing, and whether they should keep running. Use when asked to review automation, autopilot, or agent behaviour.
`build-and-qualify-a-lead-list`	Find companies matching an ICP, enrich and verify the contacts, score them, and save a qualified list. Use when asked to find leads, build a prospect list, or research a target market in MisarReach.
`review-the-sales-pipeline`	Report deal pipeline health and recommend next actions. Use when asked about deals, pipeline, forecast, or sales performance in MisarReach.
`run-an-outreach-sequence`	Design, preview and send a multi-channel outreach sequence. Use when asked to run a campaign, start outreach, or message a lead list in MisarReach.

Safety

Destructive and irreversible actions are annotated (destructiveHint) so clients can prompt before running them. The skills instruct agents to confirm before anything that sends mail, publishes content, or is otherwise visible to other people.

Discovery (initialize, tools/list, prompts/list, resources/list) never requires credentials, so registries can index the server without one. Every action does.

Install

Tools (27)

list_leadssearch_leadsget_search_job_statussubmit_lead_feedbackdiscover_companiesenrich_leadverify_emailsscore_leads

Configuration

Environment variables

MISARREACH_API_KEYsecret

Your MisarReach API key (mrk_…). Create one at https://reach.misar.io/settings/api-keys, or omit it and run the "login" tool to authenticate via browser.

MISARREACH_BASE_URL

Override the API base URL. Only needed for self-hosted instances.

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "misarreach-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@misarreach/mcp@5.1.2"
      ],
      "env": {
        "MISARREACH_API_KEY": "<YOUR_MISARREACH_API_KEY>",
        "MISARREACH_BASE_URL": "<YOUR_MISARREACH_BASE_URL>"
      }
    }
  }
}

MisarReach MCP Server (io.github.Misar-AI/misarreach-mcp)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

list_leads

search_leads

get_search_job_status

submit_lead_feedback

discover_companies

enrich_lead

verify_emails

score_leads

list_lead_lists

create_lead_list

sync_lead_list

preview_message

send_to_campaign

list_deals

create_deal

update_deal

get_pipeline

move_deal_stage

start_autopilot

list_autopilot_runs

get_autopilot_status

get_channels_status

update_channel

get_sales_agent_config

update_sales_agent_config

get_sales_agent_actions

process_sales_agent

MisarReach MCP Server

Install

Smithery (recommended)

Claude Code

Manual (any client)

Remote (no install)

Authentication

Tools

Prompts

Resources

Agent skills

Safety

Links

Install

Configuration

Related servers