2,500+ MCP servers ready to use
Vinkius

Percy MCP Server for Cline 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Percy through the Vinkius and Cline gains direct access to every tool — from data retrieval to workflow automation — without leaving the terminal.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Percy and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "percy": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Percy
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 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.

Cline operates autonomously inside VS Code — it reads your codebase, plans a strategy, and executes multi-step tasks including Percy tool calls without waiting for prompts between steps. Connect 10 tools through the Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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_build or approve_snapshot)

The Percy MCP Server exposes 10 tools through the Vinkius. Connect it to Cline 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 Cline via MCP

Follow these steps to integrate the Percy MCP Server with Cline.

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

02

Add remote server

Click "Add MCP Server" and paste the configuration above

03

Enable the server

Toggle the server switch to ON

04

Start using Percy

Ask Cline: "Using Percy, help me..."10 tools available

Why Use Cline with the Percy MCP Server

Cline provides unique advantages when paired with Percy through the Model Context Protocol.

01

Cline operates autonomously — it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Percy + Cline Use Cases

Practical scenarios where Cline combined with the Percy MCP Server delivers measurable value.

01

Autonomous feature building: tell Cline to fetch data from Percy and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Percy tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Percy and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Percy for real-time status and let Cline generate hotfix patches based on the findings

Percy MCP Tools for Cline (10)

These 10 tools become available when you connect Percy to Cline via MCP:

01

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

02

approve_snapshot

Approve a single Percy snapshot. Marks it as visually correct, updating the baseline for future comparisons

03

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

04

get_project_details

Get full details of a Percy project including name, slug, default branch, auto-approve enabled, browser targets, and build count

05

get_snapshot_details

Get full details of a Percy snapshot including name, review state, widths, fingerprint, and comparison count

06

list_browsers

List all supported browser families on Percy. Returns browser names, versions, and OS combinations for cross-browser visual testing

07

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

08

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

09

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

10

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 Cline

Ready-to-use prompts you can give your Cline agent to start working with Percy immediately.

01

"Log explicitly the builds targeting structural limits seamlessly isolating project 'org-slug/my-app' dynamically checking bounding states natively."

02

"Reverse check explicit structures extracting limits comparing properties cleanly bounding snapshot ID 'snap_778' natively efficiently."

03

"Force explicit validation mutating boundaries executing structurally an approval across build ID '8910' automatically natively flawlessly securely."

Troubleshooting Percy MCP Server with Cline

Common issues when connecting Percy to Cline through the Vinkius, and how to resolve them.

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Percy + Cline FAQ

Common questions about integrating Percy MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Connect Percy to Cline

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.