Gmail inbox contact scraper avatar
Gmail inbox contact scraper

Pricing

$7.00 / 1,000 results

Go to Store
Gmail inbox contact scraper

Gmail inbox contact scraper

Developed by

SASWAVE

SASWAVE

Maintained by Community

Extract the email address of contacts you exchanges mails with. Perfect for sales teams that are not using CRM You can target specific inbox name like Sent, Inbox, Spam, Trash ...

0.0 (0)

Pricing

$7.00 / 1,000 results

3

Total users

67

Monthly users

2

Runs succeeded

0%

Last modified

2 months ago

You can access the Gmail inbox contact scraper programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=saswave/gmail-inbox-contact-scraper",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Gmail inbox contact scraper

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=saswave/gmail-inbox-contact-scraper along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=saswave/gmail-inbox-contact-scraper",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.