Skip to main content
Glama
650,553 tools. Updated 2026-10-14 10:52

"Automated Outreach Tools or Techniques" matching MCP tools:

  • 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
  • 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 detailed documentation for Strudel live coding or ABC/ABCJS notation. Returns relevant code examples and explanations from the official docs. Use this when the curated guides (get-strudel-guide, get-music-guide) don't cover what you need — for specific functions, advanced techniques, or when you're unsure about syntax. Powered by semantic search over strudel.cc and ABCJS docs.
    ConnectorNo auth
  • Describe what's going wrong — your human's complaint, or a failure you notice in your own behavior — and get the matching techniques. Deterministic matching; if the description fits two problems it returns one clarifying question instead of guessing.
    ConnectorNo auth
  • 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 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

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to query OpenRouter model information including prices, ELO rankings, context, and perform comparisons.
    11 npm
    1
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    MCP server that provides tools for cold email outreach, including checking contact history, drafting personalized emails, and retrieving performance summaries from past outreach data.
    -

Matching MCP Connectors

  • Oregon DMV MCP — live wait times at all 60 Oregon DMV field offices, plus the office

  • USPS state code OR.

  • <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 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
  • Look up a MITRE ATT&CK threat group or software entry by ID, name, or keyword. Results include ATT&CK identity, aliases, type, description, and associated techniques with procedure-level context from public ATT&CK reporting.
    ConnectorNo auth
  • Returns structured public counterparty context before an automated B2B payment. It never approves or recommends a payment. Use when: Returns structured public counterparty context before an automated B2B payment. It never approves or recommends a payment. You need compact public counterparty context immediately before an automated B2B payment. You want company status, legal-risk and compliance signals together without a full KYB dossier. Avoid when: You only need existence or administrative status; use company/fr/verify. You need a broader multi-section company dossier; use company/fr/intelligence. Limitations: This endpoint supplies decision context but never approves, blocks or recommends a payment. It does not verify bank-account ownership, invoice authenticity or private payment behavior. Price: 0.020 USD per call via x402. Paid-call behavior: source records are not modified, but a successful invocation can consume the advertised x402 payment; the payment-required challenge is free, and repeating the tool after a completed paid invocation may require a new payment. Accepted x402 networks: eip155:8453, xrpl:0.
    ConnectorNo auth
  • 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
  • List the moderators of an X Community, cursor-paginated. Use this to identify the people who set the agenda in a community — the highest-leverage contacts for outreach or partnership. Returns full user objects. For the full membership use `get_twitter_community_members`.
    ConnectorOAuth
  • List the moderators of an X Community, cursor-paginated. Use this to identify the people who set the agenda in a community — the highest-leverage contacts for outreach or partnership. Returns full user objects. For the full membership use `get_twitter_community_members`.
    ConnectorOAuth
  • Your outreach campaigns with stats (sent, replies, queued, signed). v1 tools can only create DRAFTS, launching, pausing and sending happen in the dashboard at https://affiliatespy.io/dashboard/campaigns.
    ConnectorAPI key
  • Generate a draft reply or outreach email for one processed mention. Returns draft text for a human to review and never posts, sends, or publishes anything.
    ConnectorNo auth
  • Solve a sudoku puzzle completely with step-by-step logical deduction. Input: 81-character string of digits (0 or . for empty cells). Whitespace is tolerated. Returns: every solving step with technique name + human-readable explanation + action, the final solution string, a technique summary (counts), and tutorial links. Only uses logical techniques — never guesses. If the puzzle cannot be solved logically, the steps will end before completion. Use this when the user wants to understand how to solve a puzzle from scratch. The response includes a solve_url for continuing the same board interactively and tutorial_links for techniques used in the solution.
    ConnectorNo auth
  • Read the project's obligation schedule, completion evidence, internal action history and monthly reporting enrollment. Requires Startup or higher. A handoff or manual evidence record is not proof of automated provider execution.
    ConnectorAPI key
  • Search individual outreach emails already sent or scheduled from this workspace. Returns `emailer_messages` alongside `emailer_steps`, which say where in a sequence each message sits. Use it to see what actually went out. For per-message engagement — opens, clicks, replies — use `get_apollo_emailer_messages_id_activities`.
    ConnectorOAuth
  • Search individual outreach emails already sent or scheduled from this workspace. Returns `emailer_messages` alongside `emailer_steps`, which say where in a sequence each message sits. Use it to see what actually went out. For per-message engagement — opens, clicks, replies — use `get_apollo_emailer_messages_id_activities`.
    ConnectorOAuth
  • Remove a file already attached to a queued outreach email. recipient_email targets a queued email (pending or awaiting approval); id is the attachment's `id` as shown on that email in the queue status read. Email queue only, mirroring attach_to_outreach.
    ConnectorOAuth
  • Use this when someone asks whether a website or online store is accessible, meets WCAG, or could face an ADA accessibility complaint. Runs Google Lighthouse's automated accessibility checks (axe-core rules) on the page as a phone sees it, and returns the score, each failing rule in plain English with its WCAG criterion and how many elements fail, and how the site compares with 7IT's study of US online stores. Automated checks cover only part of WCAG; this is a starting point, not a legal opinion. Takes 20 to 60 seconds.
    ConnectorNo auth