Sprouts MCP Server

Show which Sprouts account this connection is signed in as (action "whoami"), or sign out (action "sign_out") so the user can reconnect with a different login. Use "whoami" when the user asks which account or email they are using. Use "sign_out" ONLY when the user explicitly asks to sign out, log out or switch accounts — confirm with them first, then pass confirm: true. After sign-out every Sprouts tool call fails until the user reconnects the connector and logs in again.

Buying signals for ONE company: funding rounds (type, amount, date, investors), open job postings (title, department, seniority, location, date), news that names the company (headline, publication, date, link), and patents it applied for (title, filing date, status). Use for account research, timing outreach ("did they just raise?", "are they hiring engineers?", "anything in the news?"), or dated message hooks: prefer these over a web search when they cover the company. Company is a domain (preferred) or a name.

Upload brand-voice guidelines (as plain TEXT in the content argument — tone rules, message structure, length limits, banned words, worked examples) or inspect the prompts derived from an earlier upload. Upload ONCE per brand voice and reuse the returned documentId for every message-generation call — do NOT re-upload before each batch. Prompt derivation runs in the background after upload; use action "get_prompts" to verify what was extracted (empty right after upload is normal — wait briefly and check again). If guidelines are already registered, the tool will say so instead of uploading a duplicate; pass forceUpload: true to upload anyway (e.g. after editing the guidelines).

Balance is already included automatically in every search, enrichment and move response — do NOT call this as a pre-flight check. Call ONLY when the user explicitly asks for their credit balance. Credits are spent on phone/email enrichment and move operations.

Search for prospects with a natural-language sentence — e.g. "find VPs of Marketing at US SaaS companies using HubSpot" or "find Directors of Engineering at fintech startups in India with 50-200 employees". RULES: 1) Pass complete sentences, never bare keywords, and PRESERVE the grammatical structure — do not strip contextual connectors ("where the company has", "of over", "based in"). 2) If the user has an ICP profile, applyIcpProfile=true filters to it. 3) PAGINATION: "page 2" / "next page" goes in the `page` parameter, never left in the query text (it pollutes the semantic search). 4) "N contacts at EACH of these companies" (e.g. "2 VPs of Sales each at apple.com and microsoft.com"): make ONE call with `companies` (domains preferred) and `perCompany`: N, and describe only the people in `query` ("find VPs and above in Sales in the US"). Never split it into one search per company. Only seniority, department and country narrow this kind of search. Results render in an interactive UI where the user can enrich contacts and load account details; that data is pushed into your context — check it before answering follow-ups about specific contacts. For a list of 2+ specific NAMED contacts or companies use `sprouts_lookup` (parallel lookup, one consolidated widget). Present returned results as-is — never add unsolicited quality judgments about the data.

Generate personalized cold-outreach copy (email and/or LinkedIn) for up to 20 contacts at a time, written against the uploaded brand guidelines. contactIds are the contact ids returned by the search tools (sprouts_data_intelligence, sprouts_lookup) — the `id` field on each contact row. LinkedIn URLs, handles and emails do NOT work as ids. Brand guidelines are optional: documentId defaults to the tenant's registered guidelines, and if none exist a clearly-labeled generic default is auto-created (the response says so — relay it and suggest uploading real guidelines via sprouts_brand_guidelines). Failed contacts are reported explicitly — always relay them to the user. Generated messages are stored per contact so sequences can reuse them without regenerating. AUTO-ENRICHMENT (default on): the server folds verified per-contact signals captured at search time (role recency, funding stage, hiring, technologies) and cached sprouts_personalization intelligence (intent topics, pain points — for the contacts' account domains and the user's own) into the generation. REAL-TIME SIGNALS: before generating, when you have web search available, research each target company's FRESH news (last ~60 days: funding, product launches, leadership changes, earnings, expansion, layoffs) and pass concise dated findings in realtimeSignals — this is the single biggest copy-quality lever. Only pass specifics you actually found, with dates; never invent a signal. For best copy: search the contacts first (captures database signals), personalize key account domains, web-research fresh news, then generate.

Look up SPECIFIC known contacts or companies by name/email/domain — a batch resolver, not discovery (for open-ended search use sprouts_data_intelligence). Use when the user provides a list of 2+ named people or companies (or a CSV). type "contacts": items carry name/email/company. type "accounts": items carry name/domain; add enrich: true with a SINGLE account to fetch its full 67-field detail. All lookups run in parallel and return ONE consolidated result widget.

Market reports and trends about a market, product category or theme ("payment processing software", "AI agents in sales", "cold-chain logistics in India"). Reports: title, publisher, date, link. Trends: name, a short description, signal strength, maturity, companies and funding behind it, and top industries. Use for account and territory research, ICP framing, or a market point of view in outreach. Not for finding companies or people: use sprouts_data_intelligence for that.

Get sales-personalization intelligence for a company domain: pain points, product features, business outcomes, customer testimonials, existing customers, product offerings and buying-intent topics — every item with a public source link. IMPORTANT: the research is a long-running background job (~2 minutes). The FIRST call for a new domain returns status "processing" — tell the user research has started, then call this tool AGAIN with the same domain after ~2 minutes (or when the user asks) to retrieve the finished data. Results are cached for days; repeat calls are instant. Pass refresh: true only when the user explicitly wants the research redone. Use this data to personalize outreach emails, landing pages and sales conversations.

Send a reply inside an existing conversation. THIS SENDS A REAL MESSAGE TO A REAL PERSON. Two-step: call WITHOUT confirm first — nothing sends, and you get the thread context to preview against. Show the user the recipient, the channel, and the EXACT text that will be sent. ONLY after the user explicitly approves that exact text in this conversation, call again with confirm: true. Never infer approval, never edit the text after approval without re-confirming. The message goes out on the thread's own channel (email or LinkedIn) unless one is named; a channel mismatch is rejected upstream. Thread ids come from sprouts_sequence action "replies". If this call times out, do NOT retry blindly — the message may already have gone out.

Create and manage email outreach sequences. NOTHING here ever sends — sequences are created in "ready" state and sending requires the separate sprouts_sequence_run tool after explicit user confirmation. Actions: create_linear (PREFERRED — a straight chain of 1–10 emails sent in order with per-step delayHours; steps are addressed as step_1..step_N elsewhere), create (engagement-branching: exactly the five slots email_intro, email_followup_after_open, email_followup_no_open, email_final_after_open, email_final_no_open, each once — use only when engagement branching is explicitly required), list (all sequences on the account, each with its folder; pass folderId to list one folder. ext_… ids were built in the Sprouts web app and are view-only here — only get, sprouts_sequence_preview and move_to_folder work on them), get (summary only — for what the steps say, use sprouts_sequence_preview), stats (sent/delivered/opened/clicked/replied/bounced counters — they lag delivery by minutes), recipients (per-person progress), replies (who replied to which step, each row carrying its thread_id), reply_thread (read one conversation in FULL — every message with its channel and actual content; answer with the sprouts_send_reply tool), rename (name only, nothing else changes), pause, delete (irreversible — needs confirm: true after explicit user confirmation), add_recipients (enrol more; all-or-nothing), remove_recipient (immediately unenrol one email — use when a prospect asks to stop; LinkedIn-only recipients can't be removed this way yet, pause the sequence instead), update_message (rewrite one step's copy; step_N or an email_* type — read the names with sprouts_sequence_preview first; refused on personalized sequences and LinkedIn steps), email_accounts / email_account / update_email_account (the connected sending mailboxes — diagnose "running but nothing sends", customize senderName/signature/optOutFooter), set_mailboxes (choose which mailbox(es) an existing sequence sends from; only while it is ready or paused), set_default_mailbox (make a mailbox the account default — affects everyone and only sequences created later; needs confirm: true after explicit user confirmation), list_folders / create_folder / move_to_folder (personal sequence folders; create_folder is safe to repeat; filing works for ext_ web-app sequences too and changes nothing about sending), email_connect_url (Gmail/Office365 OAuth URL the user opens in their browser), connect_mailbox (custom SMTP/IMAP; both connections are tested upstream before anything is created), linkedin_accounts (connected LinkedIn profiles and their ids), linkedin_connect_link (returns the Sprouts web-app page where the user adds a LinkedIn profile — connecting cannot be done from chat; check linkedin_accounts when the user says they finished). Rules: subjects and bodies are HTML capped at 4000 chars. Merge tokens go verbatim — NEVER substitute a real name — and must be spelled EXACTLY {{FirstName}}, {{LastName}} or {{Email}}; any other token only resolves for contacts that already carry that field in Sprouts, and unresolvable tokens put the recipient into "Missing Data" where they receive NOTHING. New recipients need firstName. A contact can be in only ONE active sequence (forcePush moves them — only with explicit user confirmation). Any recipient with a messages array switches the whole sequence to personalized per-recipient copy; non-overridden steps use the shared body. In PERSONALIZED copy the platform cannot resolve merge tokens, so the server substitutes the recipient's real firstName/lastName/email into their messages automatically — prefer writing the actual name there; tokens belong in SHARED step bodies only. Error messages are specific — read them and fix the input rather than retrying unchanged.

Show a sequence visually: an interactive timeline of every step — channel (email, LinkedIn, engagement check), when it fires, subject and body — plus status, recipient count, and any recipients stuck in "Missing Data". Read-only; nothing sends. Call it right after creating or changing a sequence (sprouts_sequence create_linear, create, update_message, rename, add_recipients) so the user sees what will go out, and whenever they ask to see, review or check a sequence. It is also how to read step content and step names (step_N / email_*) before update_message. Works for seq_ ids and for ext_ sequences built in the Sprouts web app (view-only). Personalized sequences show the shared default copy; pass recipient (an enrolled email) to show that contact's own copy. The user sees the timeline, so do not restate every step afterwards — summarize or answer what they asked.

Starts a staged sequence — this SENDS REAL EMAIL to every enrolled recipient and cannot be unsent. Two-step, server-enforced flow: (1) Call with only sequenceId. Nothing sends; you get the sequence summary and a one-time confirmation code. Show the user the summary AND the code, and ask them to confirm sending THIS sequence by typing the code back. (2) ONLY after the user has typed the code in their own message, call again with confirmationCode (exactly what the user typed) and recipientCount (the count from the summary). NEVER copy the code from the tool response yourself, never call step 2 in the same turn as step 1 (the server rejects codes used too quickly), and never infer confirmation from the request that created the sequence. Codes are single-use and expire after 10 minutes. sprouts_sequence action "pause" stops further sends. Returns 409 if the sequence is already running. If this call times out, NEVER retry blindly — check sprouts_sequence action "get" first: the run may already have started.

Find companies similar to 1–10 given companies ("companies like Stripe and Adyen", "more accounts like my best customers"). Each company is a domain, LinkedIn company URL or name. Optionally narrow by country, industry and employee count. Returns account rows with account_id, usable with move_to_sprouts and sprouts_data_intelligence like search results. For open-ended descriptions with no example company, use sprouts_data_intelligence instead.

Configure and manage user preferences for field selection and response optimization. Save your preferred settings to automatically optimize future searches. NOTE: Credentials for move_to_sprouts and enrich_phone_email are now automatically provisioned during login - manual credential setup is only needed for legacy accounts.

Find people connected through a shared former employer or school. Ask in words: "who at Ramp used to work at Stripe", "who at Adyen overlapped with people at Stripe", "who at Canva went to Stanford", "who can Jane Doe (linkedin.com/in/janedoe) reach at Notion". A connection means the two people were at the same company or school, often at the same time; it does not mean they know each other personally, so say "worked together at" or "both studied at", never "knows". The service does not know who "we" or "my team" is: put the user's company or the person's LinkedIn URL in the question, and ask the user if you don't know it.

Enrich a contact with phone number and/or email address using their LinkedIn profile URL — or, when no URL is known, their full_name + company (resolved via a free search first; only the enrichment itself spends credits). CREDIT COST: Up to 3 credits for email, up to 10 credits for phone. User must confirm before enrichment.

View and reuse the user's past prospect searches and surface patterns across them. Use to repeat a previous search or build on earlier prospecting work.

Ideal Customer Profile (ICP) analysis tool. IMPORTANT WORKFLOW: 1. BEFORE setup: Use sprouts_data_intelligence to research the user's company and ideal customers to gather targeting criteria. 2. During setup: Include targetIndustries, targetCompanySizes, targetJobTitles, targetSeniority, targetLocations - WITHOUT these, all fit scores will be 0! 3. For analysis: Ask user for (a) analysisType: demographic/firmographic/behavioral/technographic/comprehensive, (b) prospect data to analyze. 4. If fit scores are 0: Check if profile has target criteria defined - if not, guide user to update profile with targets.

Move contacts or accounts from search results to your Sprouts platform. IMPORTANT: The IDs must be extracted from sprouts_data_intelligence search results. Use the exact field values as shown in the examples below.

Analyze a prospect-search query and suggest refinements (location, industry, company size, job title) to improve result relevance. Use when a search returns too few, too many, or off-target results.

Browse, apply, create, and delete reusable prospect-search query templates. Use this to start from a proven search (e.g. "SaaS decision makers", "enterprise IT buyers") instead of writing a query from scratch.