Wait For Element

Try for free

Developed by

Jakub Drobník

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus bibendum nibh id congue convallis. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Pellentesque habitant morbi tristique senectus et neffwefwef wfw fwef wef wfwe fwqef qwef wefwefwef awef wef

5.0 (1)

Pricing

Pay per usage

Last modified

3 years ago

Open source

You can access the Wait For Element 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.

Python

JavaScript

CLI

OpenAPI

HTTP

MCP

{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?actors=drobnikj/wait-for-element",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

Configure MCP server with Wait For Element

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/?actors=drobnikj/wait-for-element 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/?actors=drobnikj/wait-for-element",
            "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.

Pay per event actor

honzakirchner43/pay-per-event-actor

Jan Kirchner

Pay Per Result 0

jkuzz/pay-per-result-0

asdf

Jan Kuželík

Example actor paid per result

mhamas/example-actor-paid-per-result

This is an example actor demonstrating "pay per result" model. When you run this actor, you are only charged for the results it produces, not for the underlying platform usage.

Matej Hamas 1

aaaaa

vratous/long-name-testing-nic

Nam aliquet diam ut dictum platea magna cum tortor placerat, amet dolor netus ante dignissim egestas faucibus himenaeos metus, nunc quisque pharetra donec felis fermentum viverra nullam. Integer interdum nascetur semper dui tempor ac viverra bibendum blandit, aenean mus felis sem venenatis vel aliqu