
Webpage DOM & CSS Analyzer
Deprecated
Pricing
Pay per usage

Webpage DOM & CSS Analyzer
Deprecated
Example showing how to use headless Chromium with Puppeteer to open a web page, fetch the list of DOM nodes on the pages and obtain CSS styling information for each HTML element. The actor uses the Chrome DevTools Protocol to access the required browser functionality.
0.0 (0)
Pricing
Pay per usage
3
Total users
73
Monthly users
1
Last modified
3 years ago
You can access the Webpage DOM & CSS Analyzer 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": { "local-actors-mcp-server": { "command": "npx", "args": [ "-y", "@apify/actors-mcp-server", "--actors", "jancurn/example-analyze-dom-css" ], "env": { "APIFY_TOKEN": "<YOUR_API_TOKEN>" } } }}
Configure MCP server with Webpage DOM & CSS Analyzer
You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:
{ "mcpServers": { "remote-actors-mcp-server": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=jancurn/example-analyze-dom-css", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported 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.