How to Use the PagePixels MCP in CrewAI

Q: How do I limit which PagePixels tools a CrewAI agent can use?

You can use CrewAI's toolfilter configuration or expose only specific endpoints through your MCP Server setup. This prevents research agents from executing destructive tools like deletescreenshotconfig.

Q: Does PagePixels support asynchronous rendering inside CrewAI teams?

Yes, agents can trigger quicksnapwithoptions asynchronously. The crew's orchestrator manages the background tasks, letting other agents continue working while the screenshot renders.

Coordinate teams of specialized agents to run automated visual audits using CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect PagePixels MCP to CrewAI

Create your Vinkius account to connect PagePixels to CrewAI — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup PagePixels with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Multi-agent visual monitoring with CrewAI

`quick_snap` allows your visual QA agent in CrewAI to capture instant screenshots of staging environments for immediate analysis. While one agent triggers the capture, another specialized agent analyzes the resulting image for layout anomalies. This separation of labor keeps your testing pipelines efficient. Using this MCP Server, the crew shares visual context across memory channels, escalating rendering bugs to your developers automatically.

Collaborative screenshot configuration management

`create_screenshot_config` enables your configuration manager agent to establish standardized testing parameters for different viewports. A separate execution agent then uses these configuration IDs to run PagePixels screenshot captures, ensuring perfect consistency across runs. CrewAI's hierarchical execution model coordinates this process. The manager agent defines the specifications, while the tester agent calls the server to run the captures, eliminating configuration drift.

Dynamic HTML rendering for email testing

`snap_custom_html` lets your content creation crew render dynamic HTML email templates to verify layout styling before dispatching. The copywriting agent drafts the HTML, the designer agent requests the render, and the reviewer agent checks the image. This workflow replaces manual inbox testing. By running the rendering tool directly inside the agent loop, your crew verifies CSS styling and absolute positioning in seconds.

Setup guide

Set up PagePixels MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke PagePixels tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="PagePixels Analyst",
    goal="Access and analyze PagePixels data via MCP.",
    backstory="Expert analyst with direct PagePixels access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent PagePixels transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="PagePixels Analyst",
        goal="Access and analyze PagePixels data via MCP.",
        backstory="Expert analyst with direct PagePixels access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent PagePixels transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by PagePixels. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect PagePixels now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about PagePixels MCP in CrewAI

Yes, because the MCP Server maintains state on the PagePixels backend. One agent can call create_screenshot_config, and any other agent in the crew can access that configuration using its unique ID.

You can use CrewAI's tool_filter configuration or expose only specific endpoints through your MCP Server setup. This prevents research agents from executing destructive tools like delete_screenshot_config.

Yes, agents can trigger quick_snap_with_options asynchronously. The crew's orchestrator manages the background tasks, letting other agents continue working while the screenshot renders.

The execution agent catches the error returned by the MCP Server. It can then request a fresh capture with different parameters or escalate the issue to the moderator agent.

All URL queries and rendered image binaries reside within the secure PagePixels infrastructure. Your CrewAI agents retrieve only the final image URLs over HTTPS, keeping your internal network structure and raw visual assets isolated from public access.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript