Crawl Url List 1by1 avatar
Crawl Url List 1by1

Pricing

Pay per usage

Go to Store
Crawl Url List 1by1

Crawl Url List 1by1

Developed by

Marek Trunkát

Marek Trunkát

Maintained by Community

Run the act with a specific configuration and input. If you leave Build, Timeout or Memory empty, the run will use the default values defined in the act. Note that the form remembers settings from the last run.

0.0 (0)

Pricing

Pay per usage

0

Total users

3

Monthly users

2

Runs succeeded

0%

Last modified

8 years ago

You can access the Crawl Url List 1by1 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=mtrunkat.com/crawl-url-list-1by1",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Crawl Url List 1by1

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=mtrunkat.com/crawl-url-list-1by1 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=mtrunkat.com/crawl-url-list-1by1",
"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.