Skip to main content
Glama
744,934 tools. Updated 2026-11-05 01:14

"A tool for sending emails" matching MCP tools:

  • [cost: write (single MongoDB row) | rate-limited per IP: 3/min, 20/day] Send the Sipflow team feedback when something doesn't work, a vendor or RFC isn't covered, or a tool produced a wrong/incomplete answer. Categories: - docs_gap: search_sip_docs returned nothing useful, vendor missing, coverage incomplete - tool_bug: a tool errored, returned garbage, or behaved unexpectedly on a real input - wrong_answer: the answer it produced was incorrect for the SIP/VoIP question asked - feature_request: a new tool, dataset, or behavior the user wants - general: anything else PRIVACY CONTRACT (MUST FOLLOW): 1. Use this tool only when the user explicitly asks to send feedback, OR when you have completed the user's primary task and there is a clear, actionable gap worth reporting. 2. ALWAYS show the user the exact `summary` + `details` + other fields you plan to send and wait for an explicit yes before calling this tool. Set `userConsent: true` only after that confirmation. 3. NEVER include raw SIP traces, INVITE/REGISTER bodies, SDP, phone numbers, IP addresses, Call-IDs, or any other PII. Summarize in your own words instead. The server runs a sanitizer as a backstop, but you are the first line of defense. 4. The `contact` field is optional and may only be filled when the user explicitly provides an email and asks you to include it. 5. The `traceExcerpt` field is optional and accepts a sanitized SIP message text block (Via/From/To/Call-ID, optional minimal SDP) the user explicitly approved attaching. Pipe `minimize_sip_trace` output here, NEVER raw INVITE / REGISTER bodies or full pcap text. Phone numbers, IPs, and emails are scrubbed server-side as a backstop; the agent must still summarize / minimize first. The same `userConsent: true` covers both the text fields and the excerpt - if the user wants the excerpt included you must show it to them before sending. The tool returns a ticket id (fb_xxxxxxxx) and stores one anonymous row keyed by your daily-rotating IP hash (no raw IP, no account). Rate-limited at 3/min and 20/day per IP hash.
    ConnectorNo auth
  • Submit an uploaded PDF for faxing. Step 1 (before this tool): upload the PDF over plain HTTP multipart, using any HTTP client you have — shell, JavaScript fetch with FormData, Python, etc.: curl -F "file=@document.pdf" https://www.sendthisfax.com/api/upload fetch("https://www.sendthisfax.com/api/upload", {method: "POST", body: formDataWithFile}) The response contains fax_public_id and page_count. PDFs must be unencrypted, at most 50 MB and 1000 pages. Step 2: call this tool with the fax_public_id and the recipient fax number. Two modes: - With an API key (Authorization: Bearer stf_live_... on this MCP connection): the fax price is debited from the prepaid credit balance and sending starts immediately — no checkout, no browser. sender_email and billing_country are optional (they default to the key's records). Buy credits at https://www.sendthisfax.com/en/credits. - Without an API key: sender_email and billing_country are REQUIRED and the tool returns a checkout_url the USER must pay in a browser; the fax is sent automatically once paid. In both modes, poll get_fax_status until status reaches "delivered" or "failed" (failures after payment are auto-refunded). For integration testing, +19898989898 is the designated test recipient number.
    ConnectorNo auth
  • Creates a new campaign, by default as a DRAFT that sends nothing. Needs list_uid, name, subject, from_name, from_email, reply_to, send_at and content (template_uid or template_content HTML). To duplicate a past campaign use copy_campaign; to create and schedule in one step use create_scheduled_campaign. status=pending-sending schedules real sending and requires confirm_send=true after explicit user approval.
    Connector
    Destructive
    OAuth
  • Start a Hokai directory listing for an AI tool, model, agent, MCP server, skill or AI service. Returns a payment link: a PERSON must open it and pay the one-time fee. Nothing is charged by this call, and the submission is reviewed by a human (full refund if the product is not a fit). Paying never affects rankings. Only call this when the product's owner or their team asked for it, and use their real work email: Hokai emails it when the page goes live. Args: tool_url: the product's own website, e.g. https://example.com email: a work email for the vendor company: company name (optional) note: anything the editors should know (optional)
    ConnectorNo auth
  • Log a feature request for the STEMPA team, ONLY after the person said yes to your offer (confirmed_by_person true). `text` is what they want STEMPA to do, in their words, without names or contact details (emails and phone numbers are removed). It changes nothing else: no act, no brief, no outcome.
    ConnectorOAuth
  • Resolve the storyflo embedder onboarding URL prefilled with the partner's name + email + optional vertical. Returns the URL the human must visit to complete signup (storyflo emails a magic link to verify ownership; the embedder slug + ref_token are minted on verification). DOES NOT create a DB row + DOES NOT send email — the MCP tool is a discovery + handoff surface so an agent can call it speculatively without triggering inbox-bound email to the human. Public — no auth required.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    面向 Codex、WorkBuddy 等 AI 工具的知你AI助手合并版 Skills,涵盖当前会话分诊、客户查询与画像、历史会话检索、客户分群和 API Key 用量查询,并连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服等渠道。
    MIT No Attribution
  • A
    license
    Not graded
    quality
    A
    maintenance
    . A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{
    7,061 npm
    MIT

Matching MCP Connectors

  • Resolve the storyflo embedder onboarding URL prefilled with the partner's name + email + optional vertical. Returns the URL the human must visit to complete signup (storyflo emails a magic link to verify ownership; the embedder slug + ref_token are minted on verification). DOES NOT create a DB row + DOES NOT send email — the MCP tool is a discovery + handoff surface so an agent can call it speculatively without triggering inbox-bound email to the human. Public — no auth required.
    ConnectorNo auth
  • Request a free Recao account for your human. This does NOT create an active account: it registers a PENDING one and emails your human an activation link; nothing works and no terms are accepted until they click it (the human accepts the terms at activation, not you). The API key in the response stays inert until then. Consent stays with the human, so calling this is a request, not a decision made for them: in an interactive session their approval of this tool call is the go-ahead; if you run autonomously, surface this step to your human instead of calling it. After activation, reconnect with header `Authorization: Bearer <key>`.
    ConnectorNo auth
  • Start publisher registration (requires the human's consent — registers their email). Pass server_url (the MCP server's own URL or repo link) when known — it drives the "server URL set" step on the publisher's dashboard, skipping it leaves that step looking incomplete even once real traffic flows. Emails a 6-digit verification code to contact_email; ask the human for the code, then call confirm_publisher(pending_id, code) to receive the API key. This tool does NOT return a publisher_id or api_key — only confirm_publisher does.
    ConnectorNo auth
  • PREFERRED multi-step tool: run 1–10 predictable UI actions in one call (input.click_target, input.click_xy, input.type_text, input.send_keys, input.drag, input.scroll). Side effects: all actions execute on the remote desktop; fails fast before sending if any action is invalid. observe_after defaults true (verification observe: text+targets; set observe_image=true for JPEG). Do not batch across unpredictable waits (page loads, installers, modals) — single-step those. Prefer this over chaining solo click/type/keys tools.
    Connector
    Destructive
    No auth
  • Relays a message you sealed locally with /svc/msg2-sdk.mjs (seal(mailbox, inner) → {ephemeralPubKey, viewTag, ct}). This tool cannot encrypt for you: sending plaintext here would expose it to the relay, so it only accepts the sealed triple. Replay-idempotent (a resend returns duplicate:true). The message appears in the public feed at releaseAt. If you cannot run the SDK, use v1 (POST /api/messages/send) and know that v1 is plaintext.
    ConnectorNo auth
  • Runs calculate_payslip for many employees in one call and returns the run totals: gross, employee deductions, net, and employer cost. Reach for this the moment more than two or three people are in play. A monthly payroll is not a sequence of unrelated questions — the employer share, the totals and the run id only mean anything across the whole run. Asking one employee at a time gives no total and no way to tell a retry from a second run. Put anything shared in defaults (prefecture, business_type, column) and let each row carry only what differs, which is usually pay and age. A row that cannot be computed comes back in errors with its index and id while the rest of the run completes — do not discard a whole payroll over one bad row. The reply carries a run_id derived from the route and the exact input, so sending the same payroll twice gives the same id. Nothing is stored, so a retry cannot double-count.
    ConnectorNo auth
  • What this server is, what it will do for you right now without an account, and what an account adds. Call this first if you have no API key — it answers in one round trip instead of sending you to a website.
    ConnectorNo auth
  • Hand the traveller to Tell & Go's own checkout on tellandgo.com for the quoted rate. Returns checkout_url: the traveller opens it, enters guest details and pays there. This tool asks for no personal or payment card data, and creates no booking: the booking exists only after the traveller completes checkout, and Tell & Go then emails the confirmation. Call get_quote, then this tool with the quote_id and residency. Relay total and price_changed from the result. If the total exceeds a budget the user stated, do NOT call this yet: tell them the price, say it exceeds their budget, and get explicit confirmation first.
    ConnectorNo auth
  • Ask Follow On Tours for a quote on a traveller's behalf. Use after you have found a suitable trip with list_tours or list_golf_trips (or for any other trip — describe it in `trip`). Follow On Tours emails the traveller to confirm the request is theirs; nothing reaches Follow On Tours, and nothing is booked or charged, until the traveller taps the link in that email. Only send details the traveller has given you and agreed to share. It returns an enquiry reference (FOT-E-YY-NNNN) to give the traveller. This tool never returns a price: quotes come from Follow On Tours directly.
    ConnectorNo auth
  • Ask Follow On Tours for a quote on a traveller's behalf. Use after you have found a suitable trip with list_tours or list_golf_trips (or for any other trip — describe it in `trip`). Follow On Tours emails the traveller to confirm the request is theirs; nothing reaches Follow On Tours, and nothing is booked or charged, until the traveller taps the link in that email. Only send details the traveller has given you and agreed to share. It returns an enquiry reference (FOT-E-YY-NNNN) to give the traveller. This tool never returns a price: quotes come from Follow On Tours directly.
    ConnectorNo auth
  • Use this when someone asks which actions their AI agent or its connected tools may take on their own, which need a person's approval, and which a person must do; or how to set up human oversight, permissions or AI governance for an agent (for example under the EU AI Act). Give either the address of a public MCP server, or the list of tools the agent has (name, description and annotations). Sorts every tool into green (runs alone: reads and prepares), yellow (a person approves: sending, updating, scheduling) or red (a person does it: money, permissions, deletion, code execution, commitments), flags tools with no risk annotations, and returns a ready policy, Claude Code permission rules (allow, ask, deny) and an oversight checklist. Reads tool lists only and never calls a tool. A working checklist, not legal advice.
    ConnectorNo auth
  • Every campaign you can see, newest first — its id, name, status, sending account, strategy, ICP, contact count, `priority` (true = its invites go before the account's other campaigns) and `state` (whether it is really sending, and why not). START HERE: li_campaign_status and li_campaign_contacts both need a campaignId, and this is what hands you one. FILTERS run over every campaign before the page is cut: `status` ("active", "paused", "completed"), `namePrefix` (case-insensitive), `sessionLabel`/`sessionId` (sending account), `minContacts`/`maxContacts` (people in it). PAGED: the reply carries `totalMatching`, `truncated` and `nextOffset` (pass it as `offset`); a filtered empty page says how many campaigns exist without the filters. `fields` keeps only the named columns (campaignId always). `format: "csv"` returns the rows as one CSV string (`csv` + `columns`) instead of `campaigns`. DB-backed and instant.
    ConnectorOAuth
  • Queue a draft Meisa broadcast for immediate delivery. IMPORTANT: This sends real emails to all matching contacts and cannot be undone. Only call this after the user has explicitly confirmed they want to send the broadcast. The broadcast must be in 'draft' status (use meisa_get_broadcast to check). If the broadcast was created with warm_send_enabled, delivery will be paced in engagement-ranked chunks over up to 24 hours instead of going out all at once. Returns immediately with status 'sending'; use meisa_get_broadcast to monitor progress.
    Connector
    Destructive
    OAuth
  • Approve or reject one course application from application_list. Approving ENROLLS the applicant right away (prerequisites skipped, the course's access period applied) and emails them an approval with a link into the course; rejecting records the decision and emails them your decisionNote, enrolling no one. Repeating the decision an application already has does nothing (no second enrollment or email), and rejecting an application that was already approved does not remove the enrollment: use enrollment_revoke for that. To enroll someone who never applied, use enrollment_create. Returns {id, status, decisionNote, reviewedAt}.
    Connector
    Destructive
    API key
  • Use this when someone wants a teas.co.uk product delivered again and again (subscribe and save). Pass one product id from find_products or a teas.co.uk product link. Returns the subscriber price, how often it comes and a link to the product on teas.co.uk, where the person presses Subscribe and save, then signs in, checks out and pays for the first delivery. This tool orders and charges nothing. Later deliveries follow every cycle as new orders with the same discount, teas.co.uk emails five days before each one and takes no automatic card payments, and the person can pause, resume or cancel at any time (my_subscriptions, change_subscription). When the product cannot be a repeat delivery, eligible is false and note says why.
    ConnectorNo auth