# Threads Email Scraper (`leads-scraper/threads-email-scraper`) Actor Threads Email Scraper SD - Threads Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Threads results by keyword, location and email domain - Threads email extractor. - **URL**: https://apify.com/leads-scraper/threads-email-scraper.md - **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.49 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ### Threads Email Scraper ### Threads Email Scraper The **Threads Email Scraper** is an Apify Actor that collects publicly indexed contact emails from Meta's Threads. Feed it keywords, get back a structured dataset of creator and founder leads. Threads is where Instagram's audience went to write. Founders, marketers, journalists and creators post there daily, and many keep a business-inquiry address in their profile bio. The Threads Email Scraper exists to collect exactly those public addresses, with the account metadata attached. Because Threads profiles are indexed by Google across both `threads.net` and `threads.com`, those addresses are publicly discoverable. The Threads Email Scraper finds them and extracts them at scale. If you have ever typed `site:threads.net "founder" "@gmail.com"` into Google by hand, this is that Threads email extractor workflow automated, expanded across dozens of phrasings, deduplicated and exported. The Threads Email Scraper never logs in, never opens threads.net, and never uses Meta's API. Every lead comes from publicly available Google search results. *** ### Key Features of the Threads Email Scraper | Feature | What it means in practice | |---|---| | Dual-domain coverage | Queries target both `threads.net` and `threads.com`, so no half of the index is missed | | Google-powered data collection | Queries use the `site:` operator, fetched through the Apify GOOGLE\_SERP proxy | | Query expansion | Each keyword x email-domain pair is searched as a base query, a quoted phrase, an `intitle:` query, and one variant per modifier | | Domain filtering | Only emails on the domains you list are kept | | Global deduplication | One row per unique address across every query and page | | Obfuscation handling | Parses `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, zero-width characters and the full-width `＠` | | Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals | | Boundary-correct matching | `@gmail.com` does not match inside `@gmail.company` or `@gmail.com.br` | | Handle parsing | `@username` in a Threads result title is turned into a canonical profile URL | | Structural parser | Locates each result's `

` and the smallest surrounding block instead of relying on Google's CSS class names | | Fallback parser | A markup change degrades to "emails without account details" rather than zero results | | Concurrency control | An `asyncio` worker pool runs queries in parallel with a shared stop signal | | Retry logic | Up to 3 attempts per page, exponential backoff, fresh proxy session per request | | Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not treated as empty | | Blocked-query requeue | Failed queries are retried once more at the end of the run | | Resumable state | Input-keyed checkpoints in the key-value store, saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` | | Streaming output | Every lead is pushed to the dataset immediately | | Run summary | Pages fetched, blocked pages, retries and emails per page are logged | Dual-domain coverage is the detail that matters most here. Threads content lives under two hostnames, and a scraper that only checks one leaves leads on the table. The rest of the feature set exists because email extraction from search results is messy. The Threads Email Scraper is built to degrade gracefully rather than fail silently. *** ### How the Threads Email Scraper Works The Threads Email Scraper is a search-engine crawler, not a Threads client. 1. **Read input.** Keywords, location, email domains, caps and concurrency. 2. **Build queries.** The `site:` operator is applied to the Threads domains alongside your keyword, the quoted email domain, and any location phrase. 3. **Fetch search results.** Asynchronous `aiohttp` requests through the Apify GOOGLE\_SERP proxy. 4. **Parse structurally.** Each result block is located from its `

` title outward. 5. **Extract emails.** A domain-filtered regex runs over the block text, with normalisation and the junk filter applied. 6. **Deduplicate and push.** New addresses go into a global set and straight to the Apify dataset. Base queries run before expanded variants, so the strongest matches land in the dataset first. Pagination continues per query until the page cap, the email cap, or a run of pages producing nothing new. That stop rule keeps the Threads Email Scraper from spending compute on exhausted queries. *** ### What Data Does It Extract? Each row the Threads Email Scraper produces is one email address plus the account context Google printed beside it. For profile results that means a handle, a display name, the `https://www.threads.net/@{username}` profile URL, and the bio snippet the address came from. For post results the title is a caption rather than a name, so `fullName` is left empty while `accountName` and the snippet still carry useful context. The Threads Email Scraper never guesses a name it cannot parse. Every row also records the keyword that produced it and the exact Google query used, which makes campaign attribution and segmentation straightforward. *** ### Input Fields All input to the Threads Email Scraper is set in the Apify Console form or passed as JSON via the API. | Field | Type | Default | Description | |---|---|---|---| | `keywords` | array (required) | `["founder", "creator"]` | Search terms describing the Threads accounts you want | | `location` | string | `""` | Optional location phrase added to every query | | `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are kept; leading `@` optional | | `maxEmails` | integer (1-10000) | `20` | Stop once this many unique emails are collected | | `countryCode` | string | `""` | Two-letter country code for the search proxy (US, GB, DE...) | | `expandQueries` | boolean | `true` | Search each keyword x domain pair in several phrasings | | `queryModifiers` | array | `["email", "contact", "business inquiries", "collab", "booking", "dm"]` | Extra words combined with each keyword when expansion is on | | `maxPagesPerQuery` | integer (1-50) | `30` | Page cap per query | | `maxConcurrency` | integer (1-20) | `5` | How many queries run in parallel | The default modifiers shipped with the Threads Email Scraper are tuned for Threads bios, where creators write "collab", "business inquiries" or "DM" beside their address. *** ### Output Schema Every dataset item from the Threads Email Scraper contains all fourteen fields below. | Field | Meaning | |---|---| | `network` | Platform name | | `keyword` | The keyword that produced the lead | | `query` | The exact Google query used | | `title` | Raw result title | | `accountName` | Account label Google prints (handle or display name) | | `fullName` | Display name parsed from a profile-style title; empty for post captions | | `username` | URL-safe handle when Threads exposes one; otherwise `null` | | `profileUrl` | Canonical `https://www.threads.net/@{username}` URL when a handle is known; otherwise empty | | `url` | Direct Threads link when exposed, else the profile URL | | `description` | Bio or caption snippet, cleaned of labels and engagement counters | | `email` | Lower-cased email address | | `emailDomain` | The matched domain, e.g. `@gmail.com` | | `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email | | `foundAt` | ISO 8601 UTC timestamp | Export the Threads Email Scraper dataset as JSON, CSV, Excel, XML or HTML, or read it over the Apify API. The output schema is stable across runs, so you can build a repeatable ingestion pipeline on top of it. *** ### Example Input and Output A realistic Threads Email Scraper configuration for B2B and creator outreach. #### Input ```json { "keywords": ["startup founder", "growth marketer", "newsletter writer"], "location": "Berlin", "customDomains": ["@gmail.com", "@proton.me"], "maxEmails": 200, "countryCode": "DE", "expandQueries": true, "queryModifiers": ["email", "contact", "business inquiries", "collab", "dm"], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` #### Output ```json { "network": "Threads", "keyword": "growth marketer", "query": "site:threads.net growth marketer \"@gmail.com\" \"Berlin\"", "title": "Jonas Weber (@jonasgrowth) on Threads", "accountName": "jonasgrowth", "fullName": "Jonas Weber", "username": "jonasgrowth", "profileUrl": "https://www.threads.net/@jonasgrowth", "url": "https://www.threads.net/@jonasgrowth", "description": "Growth marketing for B2B SaaS in Berlin. Threads every day. Business inquiries: jonas.weber.growth@gmail.com", "email": "jonas.weber.growth@gmail.com", "emailDomain": "@gmail.com", "possiblyTruncated": false, "foundAt": "2026-08-31T12:41:09Z" } ``` *** ### How to Use the Threads Email Scraper 1. Open the Threads Email Scraper on Apify and click **Try for free**. 2. Replace the default keywords with your target niche, for example `indie hacker`, `book author`, `fitness coach`. 3. Set `customDomains` to the providers your audience actually uses. 4. Set `maxEmails` for the list size you need. 5. Optionally set `location` and `countryCode` to focus one market at a time. 6. Run it and export the dataset as CSV, or pull it via the Apify API. **Tip:** Threads bios are short. Keywords describing a job title or niche outperform keywords describing content topics. **Tip:** many Threads users mirror their Instagram bio verbatim. Running the Threads Email Scraper and the [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) on the same keywords catches accounts that only one platform indexed. **Tip:** lower `maxConcurrency` if blocked pages start appearing in the Threads Email Scraper run log; raise it when the log is clean. *** ### Use Cases | Use case | How the Threads Email Scraper helps | |---|---| | Creator partnerships | Build a contact list of Threads creators before pitching a collab | | B2B founder outreach | Reach startup founders who post about building in public | | Newsletter cross-promotion | Find writers with an audience and a public contact address | | PR and media outreach | Contact journalists and commentators active on Threads | | Podcast guest sourcing | Identify subject-matter voices worth booking | | SaaS lead generation | Prospect marketers, operators and agency owners by niche | | Community building | Invite active posters in your topic into a private group | | Recruiting | Reach specialists who describe their role in their Threads bio | | CRM enrichment | Attach a contact channel to Threads handles you already track | | Competitive research | Map which voices dominate a niche, with metadata for segmentation | Agencies commonly run the Threads Email Scraper once per client vertical and per city, keeping each dataset separate for clean reporting. *** ### Why Use This Threads Email Scraper Threads has no public contact directory and no way to filter people by "has an email in bio". Manual search stops working almost immediately. Google caps a single query at roughly 300 results. Query expansion is the fix, and the Threads Email Scraper applies it methodically across base, quoted, `intitle:` and modifier variants. Dual-domain targeting also matters. Covering only `threads.net` and ignoring `threads.com` would silently halve your coverage of the index. The parser inside the Threads Email Scraper is stricter than a naive regex: obfuscated addresses are normalised, placeholders are rejected, and soft-wrapped fragments are collapsed rather than emitted as fake leads. Leads stream to the dataset as they are found, so an aborted or migrated run still leaves usable data, and resumable state means a restart continues where it stopped. Because Threads sits inside Meta's ecosystem, it pairs naturally with the [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) and the [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper). For the same text-first audience elsewhere, try the [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper), the [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) and the [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper). *** ### Limitations Read these before your first Threads Email Scraper run. They are honest and structural. - **Publicly indexed emails only.** If an address is not visible in Google's index, the Threads Email Scraper cannot find it. There is no login, no API and no private data. - **Google's result cap.** A single query returns roughly 300 results maximum. Query expansion works around this but does not remove it. - **`possiblyTruncated`.** `true` means Google's snippet ellipsis touched the address. Verify those rows before sending. - **Apify GOOGLE\_SERP proxy required.** The Actor cannot run without Apify proxy credentials. - **Free-plan cap.** Free Apify plans are limited to 100 emails per run. Paid plans are uncapped. - **Handle availability.** `username` and `profileUrl` populate only when Google exposes a handle. Some rows carry `accountName` and `fullName` with an empty `username`/`profileUrl`. That is a Google limitation, not a bug. - **Variable yield.** Results depend on keywords, domains and location. No volume is guaranteed. *** ### Related Actors The same engine behind the Threads Email Scraper ships for every major network. | Actor | What it collects | |---|---| | [Threads Email and Phone Number Scraper](https://apify.com/leads-scraper/threads-email-and-phone-number-scraper) | Emails and phone numbers from Threads | | [Threads Phone Number Scraper](https://apify.com/leads-scraper/threads-phone-number-scraper) | Public phone numbers from Threads | | [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) | Public contact emails from Behance | | [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) | Public contact emails from Bigo Live | | [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) | Public contact emails from Bluesky | | [Bumble Email Scraper](https://apify.com/leads-scraper/bumble-email-scraper) | Public contact emails from Bumble | | [Clubhouse Email Scraper](https://apify.com/leads-scraper/clubhouse-email-scraper) | Public contact emails from Clubhouse | | [Dailymotion Email Scraper](https://apify.com/leads-scraper/dailymotion-email-scraper) | Public contact emails from Dailymotion | | [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) | Public contact emails from DeviantArt | | [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) | Public contact emails from Discord | | [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) | Public contact emails from Dribbble | | [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) | Public contact emails from Facebook | | [Goodreads Email Scraper](https://apify.com/leads-scraper/goodreads-email-scraper) | Public contact emails from Goodreads | | [Hinge Email Scraper](https://apify.com/leads-scraper/hinge-email-scraper) | Public contact emails from Hinge | | [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) | Public contact emails from Instagram | | [KakaoTalk Email Scraper](https://apify.com/leads-scraper/kakaotalk-email-scraper) | Public contact emails from KakaoTalk | | [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) | Public contact emails from Kick | | [Lemon8 Email Scraper](https://apify.com/leads-scraper/lemon8-email-scraper) | Public contact emails from Lemon8 | | [Likee Email Scraper](https://apify.com/leads-scraper/likee-email-scraper) | Public contact emails from Likee | | [LINE Email Scraper](https://apify.com/leads-scraper/line-email-scraper) | Public contact emails from LINE | | [LinkedIn Email Scraper](https://apify.com/leads-scraper/linkedin-email-scraper) | Public contact emails from LinkedIn | | [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper) | Public contact emails from Mastodon | | [Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper) | Public contact emails from Medium | | [Mixcloud Email Scraper](https://apify.com/leads-scraper/mixcloud-email-scraper) | Public contact emails from Mixcloud | | [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper) | Public contact emails from Patreon | | [Pinterest Email Scraper](https://apify.com/leads-scraper/pinterest-email-scraper) | Public contact emails from Pinterest | | [Quora Email Scraper](https://apify.com/leads-scraper/quora-email-scraper) | Public contact emails from Quora | | [Reddit Email Scraper](https://apify.com/leads-scraper/reddit-email-scraper) | Public contact emails from Reddit | | [Rumble Email Scraper](https://apify.com/leads-scraper/rumble-email-scraper) | Public contact emails from Rumble | | [Snapchat Email Scraper](https://apify.com/leads-scraper/snapchat-email-scraper) | Public contact emails from Snapchat | | [SoundCloud Email Scraper](https://apify.com/leads-scraper/soundcloud-email-scraper) | Public contact emails from SoundCloud | | [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper) | Public contact emails from Substack | | [Telegram Email Scraper](https://apify.com/leads-scraper/telegram-email-scraper) | Public contact emails from Telegram | | [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) | Public contact emails from TikTok | | [Tinder Email Scraper](https://apify.com/leads-scraper/tinder-email-scraper) | Public contact emails from Tinder | | [Tumblr Email Scraper](https://apify.com/leads-scraper/tumblr-email-scraper) | Public contact emails from Tumblr | | [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) | Public contact emails from Twitch | | [Vimeo Email Scraper](https://apify.com/leads-scraper/vimeo-email-scraper) | Public contact emails from Vimeo | | [VK Email Scraper](https://apify.com/leads-scraper/vk-email-scraper) | Public contact emails from VK | | [WeChat Email Scraper](https://apify.com/leads-scraper/wechat-email-scraper) | Public contact emails from WeChat | | [Weibo Email Scraper](https://apify.com/leads-scraper/weibo-email-scraper) | Public contact emails from Weibo | | [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) | Public contact emails from X | ### FAQ #### What is the Threads Email Scraper? An Apify Actor that collects publicly indexed contact emails from Threads-related Google search results and returns them as structured data. #### Does the Threads Email Scraper log into Threads or use Meta's API? No. No login, no cookies, no browser, no API. Everything comes from public Google search results. #### Where do the emails the Threads Email Scraper returns come from? From indexed titles, snippets and site labels, usually Threads bios and post captions where the account published an address itself. #### Does it cover both threads.net and threads.com? Yes. Both domains are targeted, so the Threads Email Scraper does not miss half of Google's index. #### Do I need a proxy to run the Threads Email Scraper? Yes. It requires the Apify GOOGLE\_SERP proxy and cannot run without Apify proxy credentials. #### Can I filter by email domain? Yes, via `customDomains`. Matching is boundary-correct, so `@gmail.com` never matches `@gmail.company`. #### How many emails can one Threads Email Scraper run return? Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, bounded by `maxEmails` and by how much Google has indexed. #### Why is `username` sometimes `null`? Google does not always print a handle. When it does not, you still get `accountName`, `fullName` and the snippet, but `username` and `profileUrl` stay empty. #### What does `possiblyTruncated: true` mean? Google's snippet ellipsis touched the address, so it may be cut off. Verify those rows before adding them to a campaign. #### Are the emails verified or deliverable? No. The Threads Email Scraper extracts addresses exactly as published. Verify deliverability yourself before a send. #### Should I leave query expansion on? Yes. Google caps a single query at roughly 300 results, and expansion is how the Actor reaches past that ceiling. #### Can I resume an interrupted Threads Email Scraper run? Yes. Progress is checkpointed in the key-value store, keyed by an input hash, and restored on restart or migration. *** ### Leave a review If the Threads Email Scraper saved you time, please leave a star rating and a short review on the Actor page. Reviews are how other buyers judge whether a tool works, and they tell us which features to build next. If something did not work, email instead - bugs get fixed faster than they get complained about. ### Support Questions, a bug, or need a custom build of the Threads Email Scraper? Email **neurodata.apify@gmail.com**. # Actor input Schema ## `keywords` (type: `array`): Search terms describing the Threads accounts you want (niche, job title, industry). ## `location` (type: `string`): Optional location phrase added to every query (e.g. "New York"). ## `customDomains` (type: `array`): Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com). ## `maxEmails` (type: `integer`): Stop once this many unique emails have been collected. ## `countryCode` (type: `string`): Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any. ## `expandQueries` (type: `boolean`): Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results. ## `queryModifiers` (type: `array`): Extra words combined with each keyword when Expand queries is on. Tuned for Threads. ## `maxPagesPerQuery` (type: `integer`): Google rarely returns more than ~30 pages for one query. ## `maxConcurrency` (type: `integer`): How many queries run in parallel. ## Actor input object example ```json { "keywords": [ "founder", "creator" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "maxEmails": 20, "countryCode": "", "expandQueries": true, "queryModifiers": [ "email", "contact", "business inquiries", "collab", "booking", "dm" ], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` # Actor output Schema ## `results` (type: `string`): Records produced by Threads Email Scraper, stored in the run's default dataset. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "keywords": [ "founder", "creator" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "countryCode": "", "queryModifiers": [ "email", "contact", "business inquiries", "collab", "booking", "dm" ] }; // Run the Actor and wait for it to finish const run = await client.actor("leads-scraper/threads-email-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "keywords": [ "founder", "creator", ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com", ], "countryCode": "", "queryModifiers": [ "email", "contact", "business inquiries", "collab", "booking", "dm", ], } # Run the Actor and wait for it to finish run = client.actor("leads-scraper/threads-email-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "keywords": [ "founder", "creator" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "countryCode": "", "queryModifiers": [ "email", "contact", "business inquiries", "collab", "booking", "dm" ] }' | apify call leads-scraper/threads-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/threads-email-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/aXdcvFzgOtYHnDBNg/builds/krCxVDUBPtquxOmJD/openapi.json