An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Test Regression Runner to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Stop running full test suites when only a few files changed.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through Test Regression Runner.

  1. 01

    Analyze regression differences

    This capability performs a deep comparison between your current test results and the established baseline. It highlights the specific delta between the two runs.

  2. 02

    Run targeted tests

    This capability executes only the specific subset of tests that are affected by your recent file modifications. It saves time by skipping irrelevant suites.

  3. 03

    Get test baseline

    This capability retrieves the recorded results from your last successful or most relevant test run. It provides the reference point for regression detection.

Real work

What teams actually run

01

Rapid Local Verification

Run only the tests relevant to your current work instead of the whole project.

02

Regression Hunting

Compare a new test run against a baseline to find exactly what broke.

03

Flaky Test Debugging

Use historical data to spot tests that fail intermittently.

04

Pre-commit Validation

Verify that a specific change won't break existing functionality before pushing code.

One connector, every AI

Test Regression Runner works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Test Regression Runner to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

916ms average. Fast in production.

Test Regression Runner is checked daily against the live service.

Daily averagePeak 1022ms
Oct 3Today
Fastest day
693ms
Slowest day
1022ms
14-day trend
Improving-6%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Test Regression Runner, so you can see the experience inside your AI.

It does not authenticate your account with Test Regression Runner. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Test Regression Runner Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_FUTu0rNg9ewlNxeYf3VMM26Dw5zkdRvD4N14LHYB/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Test Regression Runner capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "test-regression-runner-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_FUTu0rNg9ewlNxeYf3VMM26Dw5zkdRvD4N14LHYB/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Test Regression Runner in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Test Regression Runner owners hand off.

Software engineers and DevOps professionals who need faster feedback on code changes.

  • 01

    Backend Engineer

    Hands off specific file paths to the agent to verify logic changes.

  • 02

    QA Automation Engineer

    Uses the capability to identify flaky tests and regression patterns.

  • 03

    DevOps Engineer

    Integrates targeted testing into local development workflows to reduce CI load.

FAQ

Questions Test Regression Runner owners ask.

  • 01

    How does this MCP save time?

    It identifies only the tests affected by your specific file changes, so you don't have to run the entire suite every time.

  • 02

    Can it detect flaky tests?

    Yes, it detects non-deterministic flakiness by comparing current results against a historical baseline.

  • 03

    What clients can I use this with?

    You can use this with any MCP-compatible client like Claude, Cursor, Windsurf, or VS Code.

  • 04

    Do I need to host the MCP myself?

    No, Vinkius hosts and manages the MCP for you. You just connect your client and start working.

  • 05

    How does it know which tests to run?

    It analyzes which tests are impacted by the specific file modifications you provide.

  • 06

    How does targeted testing work?

    The system maps modified source files to their corresponding test files using naming conventions, ensuring only relevant tests are run via run_targeted_tests.

  • 07

    What is a regression in this context?

    A regression is a failure in a part of the system that was previously working, identified by comparing the current run against a baseline.

  • 08

    How can I detect flaky tests?

    You can use analyze_regression_differences to identify patterns where tests pass and fail inconsistently without code changes.

Explore

More in Developer Tools

Suggestions

Connect Test Regression Runner to Claude, Cursor, ChatGPT & more