Percy MCP Server for CrewAI 10 tools — connect in under 2 minutes
Connect your CrewAI agents to Percy through the Vinkius — pass the Edge URL in the `mcps` parameter and every Percy tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="Percy Specialist",
goal="Help users interact with Percy effectively",
backstory=(
"You are an expert at leveraging Percy 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 Percy "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 10 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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 Percy MCP Server
Inject precision quality assurance workflows directly bounding LLM models via the Percy Visual Testing API (by BrowserStack). Programmatically verify pixel regressions executing queries evaluating visual boundaries natively across target projects. Inspect deep status arrays parsing CI build limits dynamically, extract metrics evaluating granular snapshot checkpoints asynchronously, and force immediate test baseline approvals seamlessly directly from explicit prompt commands naturally.
When paired with CrewAI, Percy becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Percy 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
- Project Navigation — Read bounded parameters tracking Percy deployments isolating configurations determining explicitly specific active QA targets natively
- Automated Build Oversight — Track specific arrays extracting dynamic checks returning pipeline checkpoints (approved/failed/unreviewed limits) explicitly seamlessly
- Visual Snapshot Operations — Log natively extracting bounds verifying comparison properties logging rendering differences mapping exact explicit width constraints
- Baseline Affirmations — Mutate bounding loops forcing active execution of JSON logic structurally bypassing native clicks allowing test approvals implicitly (
approve_buildorapprove_snapshot)
The Percy MCP Server exposes 10 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 Percy to CrewAI via MCP
Follow these steps to integrate the Percy 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 10 tools from Percy
Why Use CrewAI with the Percy MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Percy 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
Percy + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Percy MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Percy 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 Percy, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Percy 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 Percy against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Percy MCP Tools for CrewAI (10)
These 10 tools become available when you connect Percy to CrewAI via MCP:
approve_build
/approve` moving the test suite to green. Approve all unreviewed snapshots in a Percy build. Marks the entire build as visually approved for deployment
approve_snapshot
Approve a single Percy snapshot. Marks it as visually correct, updating the baseline for future comparisons
get_build_details
Get full details of a Percy build including state, total/unreviewed snapshot counts, approved/rejected snapshots, branch, commit SHA, and finalized timestamp
get_project_details
Get full details of a Percy project including name, slug, default branch, auto-approve enabled, browser targets, and build count
get_snapshot_details
Get full details of a Percy snapshot including name, review state, widths, fingerprint, and comparison count
list_browsers
List all supported browser families on Percy. Returns browser names, versions, and OS combinations for cross-browser visual testing
list_builds
List builds for a Percy project. Each build contains snapshots from a test run. Returns build IDs, states (processing/finished/failed), branch names, commit SHAs, and snapshot counts
list_comparisons
List visual comparisons for a Percy snapshot. Each comparison shows the diff between baseline and head at a specific width/browser. Returns diff images, diff percentages, and browser info
list_projects
List all projects on Percy (BrowserStack). Percy is the leading visual regression testing platform that captures snapshots and detects pixel-level UI differences across builds. Uses JSON:API format. Returns project names, slugs, and browser configs
list_snapshots
List snapshots in a Percy build. Each snapshot is a captured page/component at specific widths and browsers. Returns snapshot names, review states (unreviewed/approved/rejected), and diff percentages
Example Prompts for Percy in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Percy immediately.
"Log explicitly the builds targeting structural limits seamlessly isolating project 'org-slug/my-app' dynamically checking bounding states natively."
"Reverse check explicit structures extracting limits comparing properties cleanly bounding snapshot ID 'snap_778' natively efficiently."
"Force explicit validation mutating boundaries executing structurally an approval across build ID '8910' automatically natively flawlessly securely."
Troubleshooting Percy MCP Server with CrewAI
Common issues when connecting Percy to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Percy + CrewAI FAQ
Common questions about integrating Percy MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
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?
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?
Can CrewAI agents call multiple MCP tools in parallel?
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)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect Percy with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Percy to CrewAI
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.