How do I find my ScreenshotOne Access Key?

Log in to your [**ScreenshotOne dashboard**](https://screenshotone.com/app/settings), and you will find your Access Key under the 'API Keys' section. Copy and paste it below.

Can the agent capture elements by ID or Class?

Yes. Use the `take_element_screenshot` tool providing a valid CSS selector (e.g., `#header` or `.product-card`). Your agent will return a screenshot of just that element.

Is PDF generation supported for all sites?

Yes. The `generate_pdf` tool works for any publicly accessible URL, converting the website content into a high-quality PDF document instantly.

ScreenshotOne MCP Server for CrewAI 6 tools — connect in under 2 minutes

Name: ScreenshotOne
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 6 Tools Framework

Connect your CrewAI agents to ScreenshotOne through the Vinkius — pass the Edge URL in the `mcps` parameter and every ScreenshotOne tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="ScreenshotOne Specialist",
    goal="Help users interact with ScreenshotOne effectively",
    backstory=(
        "You are an expert at leveraging ScreenshotOne tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in ScreenshotOne "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 6 available tools "
        "and what they can do."
    ),
)

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About ScreenshotOne MCP Server

Empower your AI agent to orchestrate your entire visual auditing and website capturing workflow with ScreenshotOne, the reliable API for high-quality screenshots. By connecting ScreenshotOne to your agent, you transform complex capturing tasks into a natural conversation. Your agent can instantly take full-page screenshots, generate PDFs from URLs, and audit page metadata without you ever touching a browser. Whether you are monitoring site changes or archiving visual content, your agent acts as a real-time visual archiver, ensuring your records are always clear and comprehensive.

When paired with CrewAI, ScreenshotOne becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ScreenshotOne tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Visual Auditing — Take high-resolution screenshots of any URL and retrieve the direct image links instantly.
Full-page Oversight — Capture entire website pages from top to bottom to maintain a complete view of site design and content.
Document Intelligence — Generate professional PDFs from any website for easy sharing and offline auditing.
Metadata Discovery — Retrieve website titles, descriptions, and page sizes without performing a full capture.
Targeted Capturing — Take screenshots of specific CSS elements or custom viewports to focus on what matters most.

The ScreenshotOne MCP Server exposes 6 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect ScreenshotOne to CrewAI via MCP

Follow these steps to integrate the ScreenshotOne MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 6 tools from ScreenshotOne

Why Use CrewAI with the ScreenshotOne MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with ScreenshotOne through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

ScreenshotOne + CrewAI Use Cases

Practical scenarios where CrewAI combined with the ScreenshotOne MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries ScreenshotOne for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries ScreenshotOne, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain ScreenshotOne tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries ScreenshotOne against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

ScreenshotOne MCP Tools for CrewAI (6)

These 6 tools become available when you connect ScreenshotOne to CrewAI via MCP:

generate_pdf

Generate a PDF from a URL

get_page_metadata

) without capturing. Get metadata for a website (title, size, etc.) without capturing

take_element_screenshot

Take a screenshot of a specific CSS element

take_full_page_screenshot

Take a full-page screenshot of a URL

take_screenshot

Take a screenshot of a URL

take_viewport_screenshot

Take a screenshot with a specific viewport size

Example Prompts for ScreenshotOne in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with ScreenshotOne immediately.

"Take a screenshot of https://vinkius.com."

"Capture the full page of https://github.com/vinkius."

"Show metadata for https://www.google.com."

Troubleshooting ScreenshotOne MCP Server with CrewAI

Common issues when connecting ScreenshotOne to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

ScreenshotOne + CrewAI FAQ

Common questions about integrating ScreenshotOne MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.