# Chrome Web Store Email and Phone Number Scraper (`neuro-scraper/chrome-web-store-email-and-phone-number-scraper`) Actor

Chrome Web Store Email and Phone Number Scraper SD - Chrome Web Store Email and Phone Number Scraper is a lead generation tool that extracts leads with public contact emails and phone numbers from Chrome Web Store by keyword, location, email domain and country.

- **URL**: https://apify.com/neuro-scraper/chrome-web-store-email-and-phone-number-scraper.md
- **Developed by:** [Neuro Scraper](https://apify.com/neuro-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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Chrome Web Store Email and Phone Number Scraper

**Chrome Web Store Email and Phone Number Scraper** turns a keyword into a contact sheet of emails and phone numbers published on Chrome Web Store. Give it search terms and it returns the accounts that publish a way to reach them, with the account name, handle and profile URL beside each contact.

It reads only what Chrome Web Store and Google already show a signed-out visitor. No login, no cookies, no private or partner API, no browser and no JavaScript rendering.

***

### What the Chrome Web Store Email and Phone Number Scraper does

The Chrome Web Store Email and Phone Number Scraper searches Google with a contact dork rather than a plain keyword: `site:chromewebstore.google.com extension "@gmail.com" and whatsapp "+44"`. That asks for the pages which already publish a email address or phone number, instead of every page matching a word.

Each result block yields the account and the email address or phone number together, in one request. Google no longer prints the target URL on most layouts, so the handle comes from what it does print: the "Chrome Web Store - handle" site label, the breadcrumb, or a `Name (@handle)` title.

Every row is written to the dataset the moment it is found and logged as it is written, so a run is readable while it is still going.

Phone numbers are validated by libphonenumber against the real numbering plan of the country you searched, so order numbers, dates and follower counts cannot reach the dataset. Each number is returned in E.164 form and in the national format its country uses.

Addresses are normalised before matching, so `name [at] domain [dot] com`, spaced and full-width forms are all recovered. Placeholders such as `email@`, `yourname@` and `noreply@` are dropped, and so are prose words that only look like an address.

***

### Input reference for the Chrome Web Store Email and Phone Number Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array | `extension, developer` | Search terms - a niche, job title or industry. |
| `location` | string | `""` | Added to every query, e.g. `New York`. |
| `customDomains` | array | `@gmail.com`, `@yahoo.com` | Address domains the search asks for, and a filter on what is kept. |
| `countries` | array | US, UK, India | Which countries' numbers to look for. Name, ISO code or dial code. Each one multiplies the searches. |
| `maxEmails` | integer 1-10000 | `20` | Stop once this many unique contacts are found. |
| `expandQueries` | boolean | `true` | Search each keyword in several phrasings. |
| `queryModifiers` | array | per platform | Extra words combined with each keyword. |
| `maxPagesPerQuery` | integer 1-50 | `30` | Google result pages per query. |
| `maxConcurrency` | integer 1-20 | `5` | Queries run in parallel. |
| `countryCode` | string | `""` | Two-letter country for the search proxy. |

### Output

Every row the Chrome Web Store Email and Phone Number Scraper writes:

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that found this row |
| `query` | The exact Google query used |
| `email` | The public email address found |
| `emailDomain` | Domain part of that address |
| `possiblyTruncated` | True when Google cut the snippet mid-address |
| `phone` | The number in E.164 form, e.g. `+447590574946` |
| `phoneNational` | The same number as its country writes it |
| `phoneCountry` | ISO country the number belongs to |
| `accountName` | Account label as the platform shows it |
| `fullName` | Display name where published |
| `username` | Handle |
| `profileUrl` | Canonical profile URL |
| `url` | The page the result pointed at |
| `description` | The result snippet, cleaned |
| `foundAt` | ISO 8601 UTC timestamp |

```json
{
  "network": "Chrome Web Store",
  "keyword": "extension",
  "accountName": "examplestudio",
  "fullName": "Example Studio",
  "username": "examplestudio",
  "profileUrl": "https://chromewebstore.google.com/detail/examplestudio",
  "email": "hello@examplestudio.com",
  "phone": "+447590574946",
  "phoneNational": "07590 574946",
  "phoneCountry": "GB"
}
```

### How to use the Chrome Web Store Email and Phone Number Scraper

1. Put your search terms in **Keywords** - the niche, job title or industry you sell to.
2. Add a **Location** if the list should be local.
3. Pick the **Countries** whose numbers you want. Every number is validated against that country's numbering plan.
4. Set **Max results** to cap the run, then start it.
5. Export the dataset as CSV, JSON or Excel, or pull it through the Apify API.

### Use cases

**Lead generation.** Build a list of Chrome Web Store accounts in one niche that publish a email address or phone number, with the handle and profile URL for context before you write.

**Recruiting.** Find people describing themselves with a role keyword and reach them on the contact they chose to publish.

**Agency prospecting.** Search a niche and a city, and get a prospect sheet with the account and the contact side by side.

**CRM enrichment.** Feed `profileUrl` and `email` and `phone` straight into your CRM; the `keyword` and `query` columns record where each row came from.

### Limitations, stated plainly

- Only contacts already published in public Chrome Web Store pages indexed by Google. Nothing hidden from a signed-out visitor is reachable, and none is guessed from a name.
- Coverage depends on what Google has indexed, so a narrow niche returns fewer rows than a broad one. Raising **Max pages per query** and adding keywords helps.
- The free Apify plan caps a run at 20 results.
- A number written without its country code can only be validated against the country you searched, so search the countries you actually sell to.

### Pricing

Pay per result: you are charged for each row written to the dataset, and nothing for a run that finds nothing. Platform and proxy costs are included in that price.

### Chrome Web Store Email and Phone Number Scraper vs manual research

Done by hand, one qualified contact takes two to four minutes: find the account, open it, read
the page, copy the email or phone number, paste it into a sheet.

The Chrome Web Store Email and Phone Number Scraper does the same work continuously, with no
tab switching and no transcription errors. A hundred records is minutes rather than an
afternoon.

It also captures what manual research usually skips. The account name, the profile URL and the
exact keyword that surfaced the row all land in the same record.

That context turns a raw list into a prioritised one. The Chrome Web Store Email and Phone
Number Scraper lets you sort and filter before a single message is written.

### Using the Chrome Web Store Email and Phone Number Scraper in a workflow

Most teams run the Chrome Web Store Email and Phone Number Scraper on a schedule and treat the
dataset as a feed rather than a one-off export.

Point a webhook at your own endpoint and each finished run pushes its rows straight into your
CRM, with no manual download step.

The stable output schema matters here. Because every row from the Chrome Web Store Email and
Phone Number Scraper has identical keys, your integration never needs to handle a missing
field.

A common pattern is a nightly keyword run feeding a dedupe step. Another is enrichment: widen
the keyword list and let the Chrome Web Store Email and Phone Number Scraper fill the gaps in
an existing sheet.

#### Troubleshooting the Chrome Web Store Email and Phone Number Scraper

**Few or no rows.** The keyword is probably too broad or too narrow. Ten specific keywords beat
one generic one, and adding a location raises the hit rate.

**Rows without contacts.** That is normal - most accounts publish none. The Chrome Web Store
Email and Phone Number Scraper reports only what is genuinely on the page.

**The run is slow to start.** Lower the concurrency. The Chrome Web Store Email and Phone
Number Scraper is querying faster than the proxy pool is comfortable with.

**Fewer results than requested.** Google caps one query at roughly 300 results. Query expansion
is what reaches past that ceiling, so leave it on.

#### How the Chrome Web Store Email and Phone Number Scraper handles export and integration

Export the Chrome Web Store Email and Phone Number Scraper dataset as CSV, JSON, Excel or XML
from the Apify console, or pull it through the API.

Every field is flat - no nested objects - so the CSV opens cleanly in Excel or Google Sheets
without a parsing step.

### Related Actors

| Actor | What it collects |
|---|---|
| [Chrome Web Store Email Scraper](https://apify.com/leads-scraper/chrome-web-store-email-scraper) | Public contact emails from Chrome Web Store |
| [Chrome Web Store Phone Number Scraper](https://apify.com/neuro-scraper/chrome-web-store-phone-number-scraper) | Public phone numbers from Chrome Web Store |
| [App Store Email Scraper](https://apify.com/leads-scraper/app-store-email-scraper) | Public contact emails from App Store |
| [Atlassian Marketplace Email Scraper](https://apify.com/leads-scraper/atlassian-marketplace-email-scraper) | Public contact emails from Atlassian Marketplace |
| [Bitbucket Email Scraper](https://apify.com/neuro-scraper/bitbucket-email-scraper) | Public contact emails from Bitbucket |
| [CodePen Email Scraper](https://apify.com/neuro-scraper/codepen-email-scraper) | Public contact emails from CodePen |
| [Confluence Email Scraper](https://apify.com/neuro-scraper/confluence-email-scraper) | Public contact emails from Confluence |
| [Dev.to Email Scraper](https://apify.com/neuro-scraper/dev-to-email-scraper) | Public contact emails from DEV Community |
| [Docker Hub Email Scraper](https://apify.com/neuro-scraper/docker-hub-email-scraper) | Public contact emails from Docker Hub |
| [Figma Community Email Scraper](https://apify.com/neuro-scraper/figma-community-email-scraper) | Public contact emails from Figma Community |
| [Firefox Add-ons Email Scraper](https://apify.com/neuro-scraper/firefox-add-ons-email-scraper) | Public contact emails from Firefox Add-ons |
| [GitHub Email Scraper](https://apify.com/leads-scraper/github-email-scraper) | Public contact emails from GitHub |
| [GitLab Email Scraper](https://apify.com/neuro-scraper/gitlab-email-scraper) | Public contact emails from GitLab |
| [Google Play Email Scraper](https://apify.com/leads-scraper/google-play-email-scraper) | Public contact emails from Google Play |
| [Hashnode Email Scraper](https://apify.com/neuro-scraper/hashnode-email-scraper) | Public contact emails from Hashnode |
| [HubSpot Marketplace Email Scraper](https://apify.com/leads-scraper/hubspot-marketplace-email-scraper) | Public contact emails from HubSpot Marketplace |
| [Hugging Face Email Scraper](https://apify.com/leads-scraper/hugging-face-email-scraper) | Public contact emails from Hugging Face |
| [Jira Email Scraper](https://apify.com/neuro-scraper/jira-email-scraper) | Public contact emails from Jira |
| [Maven Central Email Scraper](https://apify.com/neuro-scraper/maven-central-email-scraper) | Public contact emails from Maven Central |
| [Microsoft AppSource Email Scraper](https://apify.com/neuro-scraper/microsoft-appsource-email-scraper) | Public contact emails from Microsoft AppSource |
| [Salesforce AppExchange Email Scraper](https://apify.com/leads-scraper/salesforce-appexchange-email-scraper) | Public contact emails from Salesforce AppExchange |
| [Shopify App Store Email Scraper](https://apify.com/leads-scraper/shopify-app-store-email-scraper) | Public contact emails from Shopify App Store |
| [Slack App Directory Email Scraper](https://apify.com/leads-scraper/slack-app-directory-email-scraper) | Public contact emails from Slack App Directory |
| [SourceForge Email Scraper](https://apify.com/leads-scraper/sourceforge-email-scraper) | Public contact emails from SourceForge |
| [Stack Overflow Email Scraper](https://apify.com/leads-scraper/stack-overflow-email-scraper) | Public contact emails from Stack Overflow |
| [Unity Asset Store Email Scraper](https://apify.com/leads-scraper/unity-asset-store-email-scraper) | Public contact emails from Unity Asset Store |
| [Unreal Engine Marketplace Email Scraper](https://apify.com/leads-scraper/unreal-engine-marketplace-email-scraper) | Public contact emails from Unreal Engine Marketplace |
| [WordPress Plugin Directory Email Scraper](https://apify.com/neuro-scraper/wordpress-plugin-directory-email-scraper) | Public contact emails from WordPress Plugin Directory |
| [WordPress Theme Directory Email Scraper](https://apify.com/leads-scraper/wordpress-theme-directory-email-scraper) | Public contact emails from WordPress Theme Directory |
| [Zapier App Directory Email Scraper](https://apify.com/leads-scraper/zapier-app-directory-email-scraper) | Public contact emails from Zapier App Directory |
| [App Store Email and Phone Number Scraper](https://apify.com/leads-scraper/app-store-email-and-phone-number-scraper) | Emails and phone numbers from App Store |
| [Atlassian Marketplace Email and Phone Number Scraper](https://apify.com/neuro-scraper/atlassian-marketplace-email-and-phone-number-scraper) | Emails and phone numbers from Atlassian Marketplace |
| [Bitbucket Email and Phone Number Scraper](https://apify.com/neuro-scraper/bitbucket-email-and-phone-number-scraper) | Emails and phone numbers from Bitbucket |
| [CodePen Email and Phone Number Scraper](https://apify.com/neuro-scraper/codepen-email-and-phone-number-scraper) | Emails and phone numbers from CodePen |
| [Confluence Email and Phone Number Scraper](https://apify.com/neuro-scraper/confluence-email-and-phone-number-scraper) | Emails and phone numbers from Confluence |
| [DEV Community Email and Phone Number Scraper](https://apify.com/neuro-scraper/dev-to-email-and-phone-number-scraper) | Emails and phone numbers from DEV Community |
| [Docker Hub Email and Phone Number Scraper](https://apify.com/neuro-scraper/docker-hub-email-and-phone-number-scraper) | Emails and phone numbers from Docker Hub |
| [Figma Community Email and Phone Number Scraper](https://apify.com/neuro-scraper/figma-community-email-and-phone-number-scraper) | Emails and phone numbers from Figma Community |
| [Firefox Add-ons Email and Phone Number Scraper](https://apify.com/neuro-scraper/firefox-add-ons-email-and-phone-number-scraper) | Emails and phone numbers from Firefox Add-ons |
| [GitHub Email and Phone Number Scraper](https://apify.com/leads-scraper/github-email-and-phone-number-scraper) | Emails and phone numbers from GitHub |
| [GitLab Email and Phone Number Scraper](https://apify.com/neuro-scraper/gitlab-email-and-phone-number-scraper) | Emails and phone numbers from GitLab |
| [Google Play Email and Phone Number Scraper](https://apify.com/leads-scraper/google-play-email-and-phone-number-scraper) | Emails and phone numbers from Google Play |

### FAQ

#### Does the Chrome Web Store Email and Phone Number Scraper need a login or cookies?

No. It reads public search results and public Chrome Web Store pages only.

#### Where do the emails and phone numbers come from?

From the public page the search result points at - the same text any visitor can read.

#### Are the numbers real?

Every number is checked against its country's numbering plan before it is written, so invalid strings are dropped rather than shipped.

#### Can I run it on a schedule?

Yes, with Apify Schedules. Progress is saved, so a migrated run continues instead of starting over.

**Something is missing or wrong.**\
Email <neurodata.apify@gmail.com>.

### More about the Chrome Web Store Email and Phone Number Scraper

Because the Chrome Web Store Email and Phone Number Scraper reads only pages Google has already
indexed, it never needs a login, a cookie jar or an API key from the platform it reads.

Run the Chrome Web Store Email and Phone Number Scraper with a narrow keyword set first. A
short test run shows the yield of a niche before a large run is paid for.

Output from the Chrome Web Store Email and Phone Number Scraper is flat - no nested objects -
so a CSV export opens cleanly in Excel or Google Sheets with no parsing step.

Pair the Chrome Web Store Email and Phone Number Scraper with Apify Schedules to rebuild a
prospect list weekly and catch accounts that published contact details since the last run.

#### Chrome Web Store Email and Phone Number Scraper at a glance

Proxy and platform costs are already inside the per-result price of the Chrome Web Store Email
and Phone Number Scraper, so the figure quoted on the Store page is the figure you pay.

Every field the Chrome Web Store Email and Phone Number Scraper returns is documented in the
output table above, and the schema does not change between runs or between platforms.

Teams that outgrow manual prospecting usually reach for the Chrome Web Store Email and Phone
Number Scraper first, because it needs no setup beyond a keyword list and a result cap.

Concurrency on the Chrome Web Store Email and Phone Number Scraper is adjustable, so a run can
be tuned for speed on a quiet network or for reliability on a busy one.

### Leave a review

If the Chrome Web Store Email and Phone Number Scraper saved you time, please leave a star
rating and a short review on the Chrome Web Store Email and Phone Number Scraper 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 <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions, bugs or a custom build: <neurodata.apify@gmail.com>.

# Actor input Schema

## `keywords` (type: `array`):

Search terms describing the Chrome Web Store 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).

## `countries` (type: `array`):

Which countries' phone numbers to look for. The search asks Google for that country's dial code, and every number found is validated against that country's real numbering plan. Country name, ISO code or dial code all work. Each extra country multiplies the number of searches.

## `maxEmails` (type: `integer`):

Stop once this many unique contacts have been collected.

## `maxEmailResults` (type: `integer`):

How many of the results should be email addresses. Leave at 0 to split "Max results" evenly between emails and phone numbers.

## `maxPhoneResults` (type: `integer`):

How many of the results should be phone numbers. Leave at 0 to split "Max results" evenly. If one type runs out first, the other takes the remaining budget.

## `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 Chrome Web Store.

## `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": [
    "extension",
    "developer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com",
    "@hotmail.com",
    "@icloud.com",
    "@aol.com",
    "@protonmail.com",
    "@live.com",
    "@gmx.com",
    "@mail.com",
    "@yandex.com",
    "@zoho.com"
  ],
  "countries": [
    "United States",
    "United Kingdom",
    "India"
  ],
  "maxEmails": 20,
  "maxEmailResults": 0,
  "maxPhoneResults": 0,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "support",
    "developer",
    "publisher"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Chrome Web Store Email and Phone Number 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "extension",
        "developer"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
        "@outlook.com",
        "@hotmail.com",
        "@icloud.com",
        "@aol.com",
        "@protonmail.com",
        "@live.com",
        "@gmx.com",
        "@mail.com",
        "@yandex.com",
        "@zoho.com"
    ],
    "countries": [
        "United States",
        "United Kingdom",
        "India"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "support",
        "developer",
        "publisher"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/chrome-web-store-email-and-phone-number-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "extension",
        "developer",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
        "@outlook.com",
        "@hotmail.com",
        "@icloud.com",
        "@aol.com",
        "@protonmail.com",
        "@live.com",
        "@gmx.com",
        "@mail.com",
        "@yandex.com",
        "@zoho.com",
    ],
    "countries": [
        "United States",
        "United Kingdom",
        "India",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "support",
        "developer",
        "publisher",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/chrome-web-store-email-and-phone-number-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": [
    "extension",
    "developer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com",
    "@hotmail.com",
    "@icloud.com",
    "@aol.com",
    "@protonmail.com",
    "@live.com",
    "@gmx.com",
    "@mail.com",
    "@yandex.com",
    "@zoho.com"
  ],
  "countries": [
    "United States",
    "United Kingdom",
    "India"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "support",
    "developer",
    "publisher"
  ]
}' |
apify call neuro-scraper/chrome-web-store-email-and-phone-number-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-scraper/chrome-web-store-email-and-phone-number-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 <APIFY_API_TOKEN>` 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/JnSFj6Rtls1pmfPZr/builds/9Y3DXYFcpXaEb6WSf/openapi.json