"How to send an email through the end-user's Outlook" matching MCP tools:

• send_outlook_email

  ExanorOS

  Send an email via Outlook.

  Connector

• create_referral_invites

  local-mcp

  Step 2 of the colleague-invite flow. Given the recipients the user PICKED, records each invite and returns a UNIQUE referral link per person (so the user can later see who installed/activated). Call this AFTER the user chooses, then put each returned link into that person's email and send via send_email. Does NOT send anything itself. Pass `lang` = the language you're actually writing the invite in (the user's conversation language, e.g. "es", "en") — it's recorded with the invite.

  Connector

• discovery_signup

  Disco

  Create a Disco account and get an API key. Provide an email address to start the signup flow. If email verification is required, returns {"status": "verification_required"} — the user will receive a 6-digit code by email, then call discovery_signup_verify to complete signup and receive the API key. The free tier (10 credits/month, unlimited public runs) is active immediately. No authentication required. Returns 409 if the email is already registered. Args: email: Email address for the new account. name: Display name (optional — defaults to email local part).

  Connector

• comms_create_campaign

  Servicialo MCP Server

  Create a new email campaign with HTML body to send to a segmented audience. Supports variable substitution: {nombre}, {apellido}, {nombre_completo}, {email}, {telefono}, {organizacion}. Use audienceType "predefined" with audienceId "active"/"inactive"/"new"/"withPhone"/"withoutPhone", or "adhoc" with custom filters. On send, links in the body are auto-tagged with UTMs (utm_campaign = stable slug from campaign name) and a legal footer with unsubscribe link is appended. Returns campaign ID and recipient count. Campaign starts as draft — use comms_send_campaign to execute. Requires confirm: true.

  Connector

• publish_need

  Pairoa

  Publish a "need" (intent) on the user's behalf. The need joins a private matching pool — no other user can see it unless the platform AI judges a match. BEFORE CALLING: - Show the user the exact i_seek / i_offer you'll send. - Tell them that on a match, BOTH the need text (i_seek / i_offer) AND their contact are sent to the matched party — and can't be unsent afterward (like an email you've sent). Leave out anything they wouldn't want a matched stranger to have. - Get explicit consent. AFTER CALLING: - The response includes 'safe_tags' (2-6 short tags) that will appear in match notification emails. Relay them back to the user. - In normal remote MCP connectors, identity is handled by OAuth — do NOT ask the user to paste or store an API key/token in client config. Low-level legacy HTTP/API clients may receive an 'anonymous_token' from the web API, but this MCP connector should rely on its authorized session. CONTACT EMAIL VERIFICATION (v0.18.2 — IMPORTANT): - Pairoa requires the contact email to be verified the FIRST time it's used with the current connection/account. - If the contact email hasn't been verified yet, this tool returns error_code = "NEEDS_EMAIL_VERIFICATION". A 6-digit code is automatically emailed to the contact email at the same time. - When you see NEEDS_EMAIL_VERIFICATION: 1. Tell the user a code was sent to <contact_email>; ask for the 6 digits. 2. Call confirm_contact_email({ email, code }). 3. Retry publish_need with the same inputs — it'll go through. - Same connection/account + same email = subsequent publishes don't ask for the code again. - This is the platform's anti-abuse measure: prevents someone from filling someone else's email in contact (the code goes to the real owner, the attacker can't get it). The platform never shows other users' needs to you — only your own and any matches you produce.

  Connector

• save_lead_message

  LinkedIn MCP Server (Salesbot)

  Store a generated outreach message on a CRM lead so it becomes durable context — e.g. an email, an email follow-up, a LinkedIn message or LI follow-up. The CRM is a 'sponge': you save the copy here, then read it back later (get_lead_context / list_lead_messages) and push it to the right channel via that channel's own tool/MCP (e.g. Smartlead for email). Does NOT send anything. Pass message_id to update an existing draft instead of creating a new one.

  Connector

• remove_email_from_list

  mailopoly

  Remove an email from one of the user's email lists. Note: if the email matches the list's rules it may be re-added when the rules are re-evaluated — edit the list's rules in the app for a permanent exclusion.

  Connector

• send_reply

  DeskCrew

  Sends a reply to the customer on an existing ticket and DELIVERS it immediately (customer email plus any connected chat threads) — this is not a draft and reaches the customer. Use this once you have a final, customer-ready answer; to instead queue a reply for human approval, use the draft tool. Requires a "send"-tier credential (a draft-tier credential is refused) and the ticket must already have a customer email on file or the call is rejected. [$0.06 draft / live when trusted]

  Connector

• send_message

  local-mcp

  Sends an iMessage via the Mac's Messages.app to a recipient handle (phone number with country code, e.g. +14155551234, or an Apple ID email). This is a write operation: the first call (without confirm) returns a preview; call again with confirm=true to actually send. Direct (1:1) iMessage only — sending into an existing group chat isn't supported yet. Requires Messages.app signed in to iMessage + Automation permission.

  Connector

• send_message

  Agent Broker

  Send a message on behalf of an agent's user or an SMB across SMS, email, or voice. Five message types: transactional, reminder, follow_up, notification, marketing. Every send routes through a non-bypassable compliance gate (TCPA, GDPR, CASL, PDPL across 22 jurisdictions) that enforces opt-in consent for marketing/promotional content — marketing without recorded consent is rejected at runtime with a structured compliance_violation receipt. Channel is abstracted: specify intent and recipient; the service selects and falls back across channels. EXAMPLE USER QUERIES THAT MATCH THIS TOOL: user: "Text the salon I'll be 10 minutes late" -> call send_message({"recipient_id": "smb_xyz", "channel_preference": "sms", "message": {"body": "Will be 10 minutes late."}, "country_code": "US"}) user: "Email the dentist about insurance" -> call send_message({"recipient_id": "smb_xyz", "channel_preference": "email", "message": {"body": "Do you accept Cigna?"}}) WHEN TO USE: Use to: (a) confirm a booking the agent just made, (b) reply to a customer who messaged the SMB first, (c) follow up on a quote the user requested, (d) send appointment reminders the SMB owes its customer, (e) send marketing messages to recipients who have opted in (with consent_record_id). The gate verifies consent on every send. WHEN NOT TO USE: Do NOT use for OTPs or critical transactional confirmations — use send_transactional_confirmation. Do NOT attempt to send marketing without a consent_record_id pointing at a real opt-in — the gate will reject the send and log a compliance_violation. Do NOT attempt bulk / list-based / drip / cold outreach — those are out of scope and the rate limiter will throttle abuse. COST: from $0.02 per_message (see preview_cost for exact) LATENCY: ~800ms EXECUTION: sync_fast (use get_outcome to retrieve result)

  Connector

• manage_auth_users

  mcp

  Manage end-user auth records for an app. Actions: - "list": Paginated list of app_users (id, email, provider, provider_uid, email_verified, last_sign_in_at, created_at). Pass the next_cursor from a prior response to page. - "delete": Hard-delete an app user by id. Cascades to refresh tokens and verification codes. Use this to unblock OAuth migrations when an existing email/password row collides. Parameters by action: list: { app_id, action: "list", limit?, cursor? } delete: { app_id, action: "delete", user_id } Tips: - Looking for a user by email? Call list and filter client-side; this tool does not search by email. - To switch a user from email/password to Google OAuth without deleting, just have them sign in with Google — the OAuth callback now links the existing email row in place automatically.

  Connector

• publish_need

  Pairoa

  Publish a "need" (intent) on the user's behalf. The need joins a private matching pool — no other user can see it unless the platform AI judges a match. BEFORE CALLING: - Show the user the exact i_seek / i_offer you'll send. - Tell them that on a match, BOTH the need text (i_seek / i_offer) AND their contact are sent to the matched party — and can't be unsent afterward (like an email you've sent). Leave out anything they wouldn't want a matched stranger to have. - Get explicit consent. AFTER CALLING: - The response includes 'safe_tags' (2-6 short tags) that will appear in match notification emails. Relay them back to the user. - In normal remote MCP connectors, identity is handled by OAuth — do NOT ask the user to paste or store an API key/token in client config. Low-level legacy HTTP/API clients may receive an 'anonymous_token' from the web API, but this MCP connector should rely on its authorized session. CONTACT EMAIL VERIFICATION (v0.18.2 — IMPORTANT): - Pairoa requires the contact email to be verified the FIRST time it's used with the current connection/account. - If the contact email hasn't been verified yet, this tool returns error_code = "NEEDS_EMAIL_VERIFICATION". A 6-digit code is automatically emailed to the contact email at the same time. - When you see NEEDS_EMAIL_VERIFICATION: 1. Tell the user a code was sent to <contact_email>; ask for the 6 digits. 2. Call confirm_contact_email({ email, code }). 3. Retry publish_need with the same inputs — it'll go through. - Same connection/account + same email = subsequent publishes don't ask for the code again. - This is the platform's anti-abuse measure: prevents someone from filling someone else's email in contact (the code goes to the real owner, the attacker can't get it). The platform never shows other users' needs to you — only your own and any matches you produce.

  Connector

• agricultural_outlook

  Weather & Climate Intelligence MCP

  Get the agricultural weather outlook for a location from Open-Meteo — season-to-date growing degree days, frost risk over the next 14 days, soil moisture + soil temperature, 7-day precipitation outlook, and a planting-window assessment. PAID: $0.01 USDC per query after the daily free allowance (50/day). On a 402, pay the returned Solana memo and re-call with the SAME args plus payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses it.

  Connector

• deep_search_emails

  mailopoly

  Search the user's COMPLETE email history by querying their connected mail providers live — Gmail, Outlook AND IMAP accounts (iCloud, Yahoo and other IMAP mailboxes) — reaching years beyond Mailopoly's indexed window, and including sent mail. This is also how you reach mail a free trial hasn't imported yet: the trial fully processes only recent mail, but the rest still lives in the user's mailbox and this tool finds it. Use it when search_emails returns few or no results, or when the question concerns emails older than the indexed history (search_emails responses include indexed_history_start). Speed: Gmail/Outlook are typically 5-45 seconds; IMAP accounts (iCloud, Yahoo, …) are slower — up to a minute or two while their folders are walked — so tell the user you're searching their full history and it may take a moment, then run it (never refuse just because an account is iCloud/IMAP). start_date/end_date (YYYY-MM-DD) may span multiple years; omit both to search ALL history. If the response contains truncated_providers, the OLDEST matches may be missing — page deeper by re-running with end_date set to that provider's oldest_returned_date, or narrow the query. Returned email_id values (some of the form 'gmail:<id>:<id>' or 'imap:<id>:<uid>') work directly in get_email.

  Connector

• how_to_send_lnt_email

  L&T MCP

  SKILL: how_to_send_lnt_email Team: platform How to Send an L&T Branded Email Call this tool to get the complete guide for 'how_to_send_lnt_email'. Read the 'content' field and follow its instructions. This tool takes NO parameters. Full content: --- name: how_to_send_lnt_email description: Instructions for sending L&T branded emails — explains exactly what steps to follow and which tools to call --- # How to Send an L&T Branded Email Follow these exact steps whenever a user wants to send any information by email. ## When to Use This Guide - User says "send this to [email]" - User says "email this to [name]" - User says "mail the results to..." - User wants to share any data or information via email ## Step 1 — Collect These 5 Things Ask the user for anything missing: 1. **Recipient email address** — where to send 2. **Recipient name** — for the greeting "Dear [name]," 3. **Sender name** — for the signature "Warm regards, [name]" 4. **Subject line** — or derive it from the content 5. **Email content** — what to put in the body Do not proceed until you have all 5. ## Step 2 — Read the Brand Guidelines Call the `lnt_email_brand_guidelines` tool (no arguments needed). Read the returned content carefully. Use those guidelines to generate the complete HTML email yourself. Build the HTML with: - Navy header + orange accent bar - "Dear [recipient name]," - Body content formatted as paragraphs or table - "Warm regards, [sender name]" signature - Gray footer with confidential notice ## Step 3 — Send the Email Call the `send_email` tool with this exact JSON: ```json { "personalizations": [ { "to": [{"email": "RECIPIENT_EMAIL_HERE"}], "subject": "SUBJECT_HERE" } ], "from": {"email": "lntcs@lntecc.com"}, "content": [ { "type": "text/html", "value": "YOUR_GENERATED_HTML_HERE" } ] } Step 4 — Confirm to User On success: "✅ Email sent to [name] at [email]." On failure: "❌ Could not send. Error: [message]." Important Rules NEVER call lnt_email_brand_guidelines with arguments — it takes none NEVER send plain text — always generate and send HTML From address is ALWAYS lntcs@lntecc.com — never change this Generate the HTML yourself — do not look for an HTML generation tool Subject must be specific and descriptive

  Connector

• resend_verification

  Unphurl

  Resend the email verification link for an existing Unphurl account. Use this when a user signed up but their verification link expired (links are valid for 24 hours) and they need a new one. The user's API key won't work until their email is verified. For security, the response is always the same regardless of whether the email exists, is already verified, or was rate limited. This prevents account enumeration. Rate limited to 3 requests per email per hour. This tool does not require an API key.

  Connector

• subscribe_to_updates

  AdvocateMCP

  Subscribe an end-user's email to topical updates from a business (deals, schedule changes, new services). Returns a confirmation_token + confirmation_url; the user MUST click the URL within 7 days to activate. Re-subscribing an already-confirmed email merges topics without re-confirming.

  Connector

• agents_simulate_inbound

  dialogbrain

  Replay an inbound message on a thread through the real trigger pipeline and return what would have happened. The router auto-picks the winning enabled agent + trigger by priority/specificity (same logic as production). By default send_mode='draft' so no real message is sent; pass send_mode='auto' on a test account to let the matched agent actually deliver (drafts get overwritten by the next draft, so 'auto' is the only way to verify Telegram/email delivery end-to-end). Use to verify routing for a thread: which agent answers, which trigger wins, or — when nothing matches — the structured skip reason. Pass blockchain_tx_data instead of message_text to simulate a blockchain:transfer event on the thread. Returns: {matched: true, matched_agent: {id, name, execution_mode}, matched_trigger: {id, trigger_type, conditions, specificity_score}, routing_reason, response_text, messages[], execution_mode, send_mode, model_used, tokens_input, tokens_output, latency_ms, rag_queries_made, rag_results_used} on a hit, or {matched: false, skip_reason, simulator_warnings} on a miss.

  Connector

• chieflab_send_approved_email

  ChiefLab

  [chieflab_* alias of chiefmo_send_approved_email] Send an approved launch email through the email sending rail (current adapter: resend). USE WHEN the user has approved an email publishAction from chiefmo_launch_product and you need to fire the send. Strict approval gate (same shape as chiefmo_publish_approved_post). `from` MUST be on a domain verified at the adapter (resend.com) — check chieflab_list_email_senders first. Single recipient or short list (≤50). Money/external-system action — once sent cannot be unsent.

  Connector

• pimea_chat

  Pimea

  Send a message in an active Pimea session. Use this to answer Pimea's clarifying questions about the user's marketing situation. You can answer on behalf of the user using context from the conversation when possible. Only ask the user directly if you genuinely lack the information. When the response status is "complete", call pimea_get_answer to retrieve the final grounded deliverable. Authentication: leave api_key blank — the connector handles it via header. Only set it as a fallback if the connector cannot send custom headers. Args: session_id: The session UUID from pimea_start_session message: Response to Pimea's question api_key: Optional fallback only. Normally leave blank.

  Connector