"Tools to Automate Sales Outreach Emails" matching MCP tools:

• qbSendEmailA

  DeepLedger — AI staff accountant for QuickBooksA

  Email a sales document (Invoice, Estimate, SalesReceipt, CreditMemo, RefundReceipt) to the customer through QuickBooks. The ONLY tool that emails a customer: recording never sends, and emailStatus:"NeedToSend" on qbInvoice/qbEstimate only queues the document for a human to send. An email cannot be unsent: confirm with the user first, never send to test, and never re-send to be sure (every call delivers again). Needs documentType and documentId. Delivery is confirmed only by delivered:true and deliveryTime, not by emailStatus. Voided documents and documents with no address are refused. ERRORS: getGuide(guideType:"error_recovery", tool:"qbSendEmail").

  Connector

  Destructive

  OAuth

• start_agentic_launchA

  Demand Discovery AIA

  Kick off Day 1 of the 90-day Agentic Launch for a completed Demand Discovery Report. Demand Discovery surfaces named prospects matching the idea's ICP and DRAFTS the first outreach batch. It sends NOTHING automatically - the user reviews and sends from their hosted manage page. Outreach is drafted to come from Amy @ Demand Discovery, with replies routed to the user's own email. Call this after a paid report is "ready" and the user wants to act on it (e.g. "generate prospects", "start agentic launch", "find me people to talk to", "yes, do the outreach"). Pass the reportId, the user's email, and the alTriggerToken from the ready report if you have it. The email MUST be the address the user themselves provided earlier in this conversation (their report-delivery email) - if you don't have it in context, ask the user first; NEVER invent one or use a placeholder like user@example.com (placeholders are rejected and the launch will not start). The response returns a manageUrl where the user reviews/sends the drafted outreach (and can switch the sender to their own Gmail).

  ConnectorNo auth

• start_agentic_launchA

  Demand Discovery AIA

  Kick off Day 1 of the 90-day Agentic Launch for a completed Demand Discovery Report. Demand Discovery surfaces named prospects matching the idea's ICP and DRAFTS the first outreach batch. It sends NOTHING automatically - the user reviews and sends from their hosted manage page. Outreach is drafted to come from Amy @ Demand Discovery, with replies routed to the user's own email. Call this after a paid report is "ready" and the user wants to act on it (e.g. "generate prospects", "start agentic launch", "find me people to talk to", "yes, do the outreach"). Pass the reportId, the user's email, and the alTriggerToken from the ready report if you have it. The email MUST be the address the user themselves provided earlier in this conversation (their report-delivery email) - if you don't have it in context, ask the user first; NEVER invent one or use a placeholder like user@example.com (placeholders are rejected and the launch will not start). The response returns a manageUrl where the user reviews/sends the drafted outreach (and can switch the sender to their own Gmail).

  ConnectorNo auth

• search_people_sales_navigatorA

  HeyReagent LinkedIn MCPA

  [Ids in: companyIds (optional): company id, from search_linkedin_companies → results[].id. Ids out: leads[].linkedinUrl: profile link; leads[].providerId: Sales Navigator id; leads[].salesNavLeadUrl: Sales Navigator lead link; leads[].publicIdentifier: public identifier.] Pull LinkedIn people matching a filter set — each person returns name, current title & company, headline, location, industry, the LinkedIn profile URL, providerId (feed to get_recent_posts to personalize), salesNavLeadUrl (the InMail-ready URL — pass it, or {profileUrl, providerId}, to add message targets on an InMail campaign), openProfile (true = accepts InMail for free), connectionDegree, sharedConnectionsCount (warm-intro signal), tenureInRole/tenureInCompany (a SHORT tenure means newly in seat — a timing signal for outreach), and pendingInvitation (true = already invited, skip it). Feed the URLs to enrich linkedin urls / enrich profiles for verified emails, or create leads bulk to add them to a campaign. COSTS HeyReagent credits per person returned (0.02 each; counting is free). ALWAYS size first with count_people_sales_navigator, then call this with confirm:false to see the exact credit cost, get the user's yes, THEN confirm:true. Never pull more than the balance covers. Same filters as count_people_sales_navigator (including the company revenue band — check revenueScope.complete), plus limit (default 25, max 100). BUILD A BIG LIST: to go past 100, pass the returned nextCursor back in as `cursor` (same filters, confirm:true) to pull the next batch — repeat until hasMore is false. For a large list, set format:"csv" to get an export-ready CSV block. Present results as a compact table (name / title / company / location) and, when the set is large, offer to (a) keep paging, (b) export to CSV, or (c) pull direct dials + emails via enrich linkedin urls.

  Connector

  Destructive

  OAuth

• audit_copyA

  Moltline Outbound EngineA

  Audit outreach copy for spam triggers and deliverability risks. FREE. Checks spam-trigger phrases, length, structure, caps, links, and personalization signals. Typical input {"subject": "Quick question", "body": "<email text>"} returns {"score": 0-100, "findings": ["Spam-trigger phrases: ...", "Long for cold outreach (200 words; aim 50-125)"], "note": "..."}. Use on the body of an outreach message. Not for the subject line alone (subject_line_scorer) and not for the send schedule (sequence_planner). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• audit_copyA

  Moltline Outbound EngineA

  Audit outreach copy for spam triggers and deliverability risks. FREE. Checks spam-trigger phrases, length, structure, caps, links, and personalization signals. Typical input {"subject": "Quick question", "body": "<email text>"} returns {"score": 0-100, "findings": ["Spam-trigger phrases: ...", "Long for cold outreach (200 words; aim 50-125)"], "note": "..."}. Use on the body of an outreach message. Not for the subject line alone (subject_line_scorer) and not for the send schedule (sequence_planner). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• salesnav_send_messageA

  Reach MCPA

  Send a message in an existing Sales Navigator thread (salesApiMessageActions). Requires the account to have a Sales Navigator subscription. Use the thread id returned by salesnav_list_messaging_threads. Use only to reply inside an existing Sales Navigator thread; everything else (new messages, classic inbox) goes through send_message. Counts against the daily messages quota.

  ConnectorAPI key

• get_outreach_windowA

  SliqA

  <summary>The account's outreach activity window and whether it is open right now. Sliq only sends LinkedIn and email outreach inside this window, so when a queue looks idle, check this before telling the user something is broken — a closed window (or empty active_days, meaning outreach is paused) is a normal hold, not a failure, and a send cannot be moved into a closed window.</summary> <returns> <description>A dict with `open_now` (whether the window is open at this moment), `window_start` and `window_end` (local time as HH:MM), `active_days` (weekday abbreviations the window runs on, empty when outreach is paused), and `timezone` (IANA name, or null for the legacy send-anytime default). The user edits these under Settings; no tool changes them.</description> </returns>

  ConnectorOAuth

• research-prospectA

  GigSoul x402A

  Research a sales prospect company: company profile, decision-maker role profile (role-level, not a named person), likely pain points, and an outreach angle. Use before writing outreach; then use generate-cold-email. Based on model training knowledge, not a live lookup; figures are estimates. Pay-per-call: $0.06 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.

  ConnectorNo auth

• salesnav_send_messageA

  Reach MCP — LinkedIn for AI agentsA

  Send a message in an existing Sales Navigator thread (salesApiMessageActions). Requires the account to have a Sales Navigator subscription. Use the thread id returned by salesnav_list_messaging_threads. Use only to reply inside an existing Sales Navigator thread; everything else (new messages, classic inbox) goes through send_message. Counts against the daily messages quota.

  ConnectorOAuth

• request_quoteA

  AirShelf CatalogA

  Send a quote request for catalog products to a merchant's sales team on behalf of a named buyer. This is a two-step, double opt-in flow. The first call emails a confirmation link to `contact.email` and returns status "confirmation_required"; no lead exists and no merchant is contacted until the buyer confirms. A later call with the same arguments reports "awaiting_confirmation" while the email is unconfirmed, or "received" with a reference_number after confirmation. Merchant slugs come from list_merchants. Network-catalog brands that are absent from that list use merchant:"airshelf-network" with brandSlug:"<manufacturer-slug>"; AirShelf routes the confirmed request to that brand.

  Connector

  Destructive

  No auth

• humanizeA

  CounselorAIA

  Rewrite reader-facing prose so it sounds direct, specific, and personal without changing facts or inventing a voice. Use it for outreach, emails, letters, posts, and narrative copy. It preserves quoted text and checks the result against the source. It does not evade or promise to beat AI detectors. Do not use it for code, SQL, JSON, legal text, or technical specifications. Cost: about 413 credits (~$0.413) per call.

  ConnectorNo auth

• search_linkedin_connectionsA

  SliqA

  <summary>Search the user's established first-degree LinkedIn connections (research_app_user_linkedin_connections) — the people they are already connected to. Use to find existing relationships by name, title, or company ("which of my connections are Heads of Sales", "do I know anyone at Acme"). This is NOT message history (use search_linkedin_message_history) and NOT outreach prospects (use query_prospects). Use the exact column names listed under `where_clause` below. position and company are connection-time snapshots and may be stale — treat them as a starting point, not current ground truth.</summary> <returns> <description>Dict with count, truncated (True when more rows exist past this page), and connections array.</description> </returns>

  ConnectorOAuth

• create_quote_requestA

  MaterialHandling.comA

  Create a real quote request in the MaterialHandling.com sales system. A human equipment specialist prices it (volume pricing + freight) and emails the finished quote, usually within one business day. Use when the customer wants formal/volume pricing. Requires the customer's real name and email — always confirm these with the customer before calling. Returns the quote number. Rate-limited to 5/hour.

  ConnectorNo auth

• xtiles_list_workflowsA

  xTilesA

  List the pre-built xTiles workflows — curated, step-by-step recipes the team has prepared (recurring digests, weekly reviews, briefs, planner/space setup, onboarding, etc.). Call this FIRST — before you start assembling any multi-step process in xTiles by hand — whenever the user wants to set up, automate, schedule, recurring-ly produce, onboard, or "have xTiles do something for them", or asks what xTiles can do automatically. If there is any chance a prepared workflow already covers the request, check here before improvising with individual `xtiles_*` tools. Returns each workflow id, title, and when to use it — match the request to the closest entry, then call `xtiles_get_workflow` with that id to see the steps it suggests. If nothing matches, proceed normally with the other tools.

  ConnectorOAuth

• find_decision_makersA

  HeyReagent LinkedIn MCPA

  [Ids in: none. Ids out: leads[].linkedinUrl: profile link; leads[].providerId: Sales Navigator id; leads[].salesNavLeadUrl: Sales Navigator lead link; leads[].publicIdentifier: public identifier.] Find the senior decision-makers at a company — C-level, VP, Head-of, Director, Founder — by company name. Returns each person's name, title, and LinkedIn profile URL (feed to enrich_* for emails or create leads bulk for a campaign). COSTS HeyReagent credits per person returned (0.02 each). Preview→confirm like search_people_sales_navigator: confirm:false shows the cost estimate, confirm:true pulls and charges. Pass titles to target specific roles (e.g. ["VP of Marketing"]); omit it to get the full senior set. Optionally narrow by seniority level, job function/department, and location — e.g. seniorities:["CXO","VP"] + functions:["Sales"] for the sales leadership only.

  Connector

  Destructive

  OAuth

• search_contactsA

  xmagnetA

  Search for contacts by title, company, or query. Searches saved Xmagnet contacts first (free, instant), then a profile-first prospecting page of up to 50 profiles (free, emails HIDDEN). Examples: 'CTOs in Denver', 'John Smith at Google', 'VPs of Sales at SaaS startups'. Emails are not included — to reveal one, call find_email for that person (one Contact Finder charge per verified find). Use load_more_contacts for the next page.

  ConnectorNo auth

• list_team_membersA

  hyperpingA

  Users on the project, with names and emails. Use to resolve user IDs from schedules/policies.

  ConnectorNo auth

• outreach_create_campaignA

  rankparse-mcpA

  Create a draft link-building outreach campaign (sends via the user's connected Gmail). Outreach flow: 1) interview the user (their site, goal, competitors), 2) build a prospect list with get_competitor_gap / get_referring_domains / get_domain_authority, 3) research one real contact email per prospect domain, 4) write a short personalized subject+body per contact, 5) outreach_create_campaign, 6) outreach_add_contacts, 7) show the user the emails you drafted and get their OK before launching, 8) outreach_launch_campaign: for most accounts this puts the emails in the user's RankParse inbox and returns status awaiting_approval with a review_url, and nothing is sent until the user approves them there (show them the review_url; if status is approved it is already approved, so do not launch again). Shortcut: propose_outreach_send does steps 5, 6 and 8 in one call (creates or tops up the campaign, adds the contacts, asks for approval). Requires the user to have Gmail connected at rankparse.com/dashboard/integrations. To CONTINUE an existing campaign rather than start a new one, begin at outreach_suggest_prospects instead of step 1: campaigns are topped up, not replaced.

  ConnectorNo auth

• get_meA

  Fractional Teams PortalA

  Who this API key belongs to: the client (customer), the user, their report-section scopes ("*" = full access, else a list from: seo, aeo, geo, smm, outreach, paid_media, plan), whether the key can mark outreach leads, and any own-leads-only restriction.

  ConnectorNo auth

• copilot_launchA

  EmailchaserA

  Creates a DRAFT campaign from a sequence. With a LinkedIn Sales Navigator search it also starts finding + verifying leads for it; without one the draft holds the emails and leads can be added from Lead Finder or a CSV upload. Nothing sends — the campaign stays a draft until you review and launch it. Returns the new campaign id, plus a lead-finding job id when lead finding started.

  ConnectorNo auth