PagePixels MCP. Snap visuals from URLs and custom HTML.

PagePixels MCP Server: Visual Asset Generation for Your AI Agent

Listen, forget anything that sounds like a marketing pitch about 'unlocking potential.' This server gives your agent something much more practical: the ability to grab high-fidelity pictures of web content. It's not just taking JPEGs; it runs rendering code on live URLs or raw HTML blocks and captures those visuals for you.

Instant Snapshots & Live Captures

You wanna see what a page looks like right now? You can use quick_snap to take an immediate screenshot of any URL. Your agent hits the tool, drops a web address, and bam—you get a picture of it instantly.

If you need more control than just the quick snap, you've got quick_snap_with_options. This one lets you specify advanced parameters. You can tell your agent exactly what viewport size to use or if you need the whole page scrolled out—not just the first visible fold. It gives you granular control over how that live URL is captured.

Snapping Custom Code

Sometimes, a webpage doesn't exist yet, or maybe you're testing a chunk of code locally. That’s where snap_custom_html comes in. You pass it raw HTML code—a block right there in the prompt—and it renders that code into an image snapshot for you. It bypasses the need to connect to a live web server, letting you visualize content directly from the source code.

Managing Automated Monitoring (Scheduling)

If you gotta monitor something over time—like checking if a price changed or if a banner broke—you don't wanna manually snap it every hour. You set up automated monitoring using scheduled configurations. This whole cycle is managed by four tools, keeping your agent in control of the entire process.

First, you use create_screenshot_config. This tool sets up an entirely new, recurring job. You define the URL and the schedule—say, every midnight on Tuesdays—and it'll take automated screenshots for you. It’s how you build out continuous visual checks without writing any code.

Need to look at what you already set up? list_screenshot_configs gives you a summary of all your scheduled jobs. You can see if they're active or if they've been deleted.

If you want the full skinny on one specific job, you use get_screenshot_config. Just drop in the unique ID, and it spits out every detail about that single configuration.

Change your mind? If the URL changes or you gotta shift the schedule but don't wanna delete everything, you can use update_screenshot_config. This modifies an existing job—changing its parameters without losing the whole setup. It’s safer than starting over.

When the monitoring is done and you don't need those scheduled snaps anymore, you call delete_screenshot_config. That tool stops the automated process and cleans up that configuration record entirely.