Skip to main content
Glama
306,570 tools. Last updated 2026-07-25 13:38

"Developing a Bulk Email System" matching MCP tools:

  • 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
  • Complete Disco signup using an email verification code. Call this after discovery_signup returns {"status": "verification_required"}. The user receives a 6-digit code by email — pass it here along with the same email address used in discovery_signup. Returns an API key on success. Args: email: Email address used in the discovery_signup call. code: 6-digit verification code from the email.
    Connector
  • Bulk-export a buyer's licensed catalog via GET /enterprise-license?format=ndjson (Phase 11 M3). Returns up to 1000 articles per call (collected from line-delimited JSON wire format). Each article emits one usage_records row (analytics-only sentinel 'bulk-export:<request_id>:<article_id>' — not metered-billable per the revenue-model bifurcation invariant). Use `since` (ISO 8601) for delta-feed. Use `cursor` to paginate beyond 1000. Backend supports 5000 articles per call; the MCP cap is 1000 for transport reasonability. Real bulk-ingest pipelines should use the Python SDK (pip install opedd) directly — not via MCP. Requires OPEDD_ACCESS_KEY (ent_*).
    Connector
  • Verify an array of email addresses in one call — the volume play for list hygiene and bulk lead enrichment. Returns a per-email result array (same signals as verify_email) plus a deliverable/disposable summary. Up to 100 emails per call; domain-level facts are cached and deduped, so repeat domains are cheap. PAID: $0.003 USDC per email, minimum $0.05, after the daily free allowance. 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 payment.
    Connector
  • Bulk-verify a LIST of email addresses. Submits the whole list, waits for completion, and returns one result per email (same fields as verify_email). Best for cleaning lead lists. Charges 1 Fox Credit per email. Large lists that don't finish quickly return a jobId to poll with get_job.
    Connector
  • [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

Matching MCP Servers

Matching MCP Connectors

  • 斯特丹STERDAN天猫旗舰店产品咨询MCP Server。洛阳30年源头工厂,高端钢制办公家具,1374个SKU,涵盖保密柜、更衣柜、公寓床、货架、快递柜。BIFMA认证,出口35+国家。8个工具:产品目录查询、场景推荐、认证资质、采购政策、维护指南等。

  • Agent-run cold-email infra: 24 MCP tools, live sending, free sandbox. $99/mo, concierge go-live.

  • Add and/or remove the same labels on many email messages at once in a single Gmail API call (wraps users.messages.batchModify). Use this for bulk operations such as marking multiple specific emails as read (remove ['UNREAD']), archiving (remove ['INBOX']), or starring (add ['STARRED']). Use list_labels to find label IDs (Gmail requires IDs, not names). Common system label IDs: INBOX, STARRED, IMPORTANT, UNREAD, SPAM, TRASH. Provide 1-1000 email IDs and at least one of `add` or `remove`. The same label changes are applied to every listed message. Gmail returns no per-message status, so a successful call means Gmail accepted the request; an invalid email ID or label ID typically causes Gmail to reject it.
    Connector
  • Use this when the user has selected a specific inbound email and confirmed a reply. Sends real outbound email with threading handled server-side.
    Connector
  • Submit a list of email addresses as an asynchronous bulk verification job — the right tool for large lists. Returns immediately with a job_id, status, and the check_status_url / results_url to poll. Small lists may complete inline (status 'completed'); larger ones return status 'pending' — poll get_job_status until it is 'completed', then call get_job_results. Optionally register a webhook_url (public HTTPS) to be notified when the job finishes.
    Connector
  • Attach a real email address to the signed-in user's phone-keyed TuLugar account (accounts created via WhatsApp have no usable email). Sends a confirmation link TO that email; the user must open it — the link proves they own the address. Ask for the email, confirm it back to them, then call this. Only works for accounts that do not have a real email yet; if the email belongs to another account, the tool explains the options (never merges silently).
    Connector
  • Search international public procurement — government tenders, contract notices, and contract awards published under the OCDS Open Contracting Data Standard. Covers 18 national and subnational publishers across developing countries and Europe: Africa (Kenya, Nigeria, Ghana, Zambia, Liberia, Rwanda, Tanzania), Latin America (Uruguay, Honduras, Guatemala, Peru, Dominican Republic, Mexico/Oaxaca), the Balkans (Albania, Kosovo, Croatia), Thailand (Bangkok), and Italy (ANAC anti-corruption authority). Free-text query matches tender title, buyer (procuring government entity), and description. Filter by country, status (e.g. tender, award, complete), category (works | goods | services), min_value (tender value floor), and days (recently released). Returns one row per contracting process (latest release) with buyer, value, procurement method, deadlines, and award details when present. Data is a weekly-refreshed hosted mirror of official OCDS bulk publications (OCP Data Registry). Use oc_coverage first to see which countries have data and how fresh it is.
    Connector
  • Complete login and receive a new API key. Call this after discovery_login returns {"status": "verification_required"}. The user receives a 6-digit code by email — pass it here along with the same email address. Returns a new API key on success. Args: email: Email address used in the discovery_login call. code: 6-digit verification code from the email.
    Connector
  • Create an Etch e-signature packet (documents + signers). GraphQL mutation: createEtchPacket. IMPORTANT: isDraft defaults to true (a safe draft that sends nothing). Setting isDraft=false with real signers SENDS signature-request emails to those signers. Use isTest=true while developing.
    Connector
  • Start email verification before showing a customer's private data (past orders, reorder, saved address, email order-status). Sends a 6-digit code to the email. Returns a verificationId. Then ask the customer for the code and call vivid_identity_verify. Use this whenever a customer asks to see 'my orders', 'reorder', or 'status by email' and you don't already have a valid identity token.
    Connector
  • [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
  • Preview a bulk customer import (max 2000 rows). Matches existing accounts by phone/email and shows create vs update actions plus points/stamps/credit deltas. Use commit_customer_import with the returned sessionId to apply.
    Connector
  • Sends an email to specified recipients using SendGrid's email delivery service. Use when: "send an email", "notify user by email", "trigger email alert", "deliver notification via email", "SendGrid email", "outbound email" IMPORTANT: Ensure the sender email address is authorized in SendGrid. If using dynamic content, verify template variables are correct. No direct cross-tool dependencies, but email content may reference data from other EIP modules. Headers required (auto-injected): - Authorization: Bearer token for SendGrid API access - Content-Type: application/json Request body fields: - personalizations: List of recipient and email metadata objects. - to: Array of recipient objects. - email: Recipient's email address. - subject: Subject line for the email. - from: Object specifying the sender. - email: Sender's email address. - content: List of content objects for the email body. - type: MIME type of the email content (e.g., text/plain, text/html). - value: Actual content of the email message. Response fields: - No live response sample available. On success, the API typically returns HTTP 202 Accepted with an empty body, indicating the email was queued for delivery. Error handling: - 400 Bad Request: The request body is invalid, missing required fields, or contains malformed email addresses. - 401 Unauthorized: The Authorization header is missing or the API key is invalid. - 403 Forbidden: The sender email address is not verified or not allowed. - 429 Too Many Requests: Rate limit exceeded. - 5xx Server Errors: Temporary issues with SendGrid's service. Rules: - Always provide a valid, authorized sender email. - Ensure recipient emails are accurate. - If using HTML content, set type to "text/html". - Handle 202 response as success; any 4xx or 5xx code should be treated as a failure and logged for investigation.
    Connector
  • Should a homeowner repair or replace their HVAC system? Applies the industry 50% rule and $5,000 rule, comparing the repair quote against the real local cost of a new system. USE WHEN: the user has a repair quote and asks whether to fix or replace. `system`: "central_ac", "furnace", or "heat_pump". Needs a city+state or ZIP.
    Connector
  • Resend a verification email for your WHOIS contact email. If the contact email matches your login email, it's already verified. Rate limited to once per 15 minutes.
    Connector