Remote.com Job Scraper avatar
Remote.com Job Scraper

Pricing

$22.00/month + usage

Go to Store
Remote.com Job Scraper

Remote.com Job Scraper

Developed by

SASWAVE

SASWAVE

Maintained by Community

Remote.com Job Scraper. From a job search url on website remote.com , extract job listings. Get informations about title, date creation, location, salary, company website, company name and more

0.0 (0)

Pricing

$22.00/month + usage

2

Total users

29

Monthly users

6

Runs succeeded

56%

Issues response

0.97 hours

Last modified

20 days ago

You can access the Remote.com Job 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/remote-com-job-scraper",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Remote.com Job 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/remote-com-job-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/remote-com-job-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.