So what makes Scrapling MCP better than Playwright MCP and other known free MCPs that automate browsers or scrape the web? Scrapling MCP in v0.5 can achieve the same browser automation as others, but: - It provides Chainable browser actions. Unlike any other MCP, the agent makes one call to the MCP to take an action in the browser, then thinks, then makes another call for the following action, and so on. In Scrapling, the agent can send a sequence of actions to run in the browser without repeating calls, saving tokens and letting the agent plan ahead. For example, a website that shows a game to test whether you are human, based on your quick reactions, can be solved this way. The actions cover all waiting conditions, so a sequence can include clicking a button, waiting 5 seconds, ensuring the network is stable, typing in an input field, pressing Enter, waiting for a specific selector to appear, waiting for all JavaScript to execute, and then finishing. Imagine Scrapling doing all of that for the Agent instead of the agent sending the calls one by one! - The MCP can see and interact with closed shadow-DOM elements like CAPTCHAs. I don't think this needs explaining, but it means you can rest assured the agent can interact with anything the website throws at you. Previously, you had to give your agent access to computer-use add-ons so it could see the screen and interact with elements like this through coordinates; now it can do it directly through the browser. - There is a lot of focus on saving tokens! Here, we block ads; let you select elements instead of the whole page for all operations; let you save browser state and repeat it later; and protect against prompt injection better than most tools. For example, we delete all hidden elements and zero-width elements, so we save more tokens while protecting you more! - Stuff we already had from before: * We provide a Cloudflare solver that doesn't require AI. * You can do requests through Scrapling without browsers that fake TLS fingerprints, so you only use browsers when you have to (and with a lot of control). * Control over what reaches the AI. Extract selected elements as Markdown, HTML, or text. Search page snapshots or read captured API responses. This can reduce unnecessary output. Other than that, you will find the things that you already see in other tools, like moving and clicking the mouse, using the keyboard and typing slowly, interacting with dropboxes and similar elements, doing drag and drop with the mouse, executing JavaScript on the page, interacting with dialog popups, seeing the requests that are happening in the background and the parts that the Agent is interested in each request, and full control over the type of content returned to the agent to be HTML/Markdown/Text content and so on. Now tell me, have you tried this update yet, and what do you think? 🔥

Check out the video on YouTube: youtube.com/watch?v=NHwWEiTO… Full release notes: github.com/D4Vinci/Scrapling… Full migration guide on moving to v0.5 translated to 10 languges: scrapling.readthedocs.io/en/…

Last night, someone did 12 PRs within 10 minutes to Scrapling. First, I blocked him, closed all PRs without reading them, and labeled them all as "AI-Slop". This is not the first time this has happened, and you can't convince me that PRs spanned this quickly were reviewed. From what I have seen so far, they don't. Now don't get me wrong, I use Fable and Astra a lot to help me manage Scrapling stuff and the development process as a solo maintainer, even with all the help I get from our awesome contributors. But the question is: how long will we have to deal with those low-quality AI-slop bombs that waste every project maintainer's time? I see this in nearly every open-source project, and most of it comes from accounts that look like that dude's: hundreds of PRs a month across many known projects and languages, and they call themselves "AI-forward Engineer" or something similar! Is that the future now, and do we just have to accept it? Low-quality PRs everywhere, as long as you ship fast? Will @github ever provide an option to block this? I guess we will never know!