Documentation

Vibe Test MCP server

Server URLhttps://api.vibe-test.tech/mcp

What it is

The Vibe Test MCP server puts Vibe Test's tools inside your AI assistant. Ask in your own words — check a branch, list bugs, fix one, run a regression — and the assistant calls Vibe Test for you. Every action runs on Vibe Test's servers, never on your computer, as you: with your own permissions and your project's credits, exactly as if you pressed the same button on the website.

Connect

Add the server to your client with its line below. The first time it connects, your browser opens to sign in.

  • Claude (claude.ai and Desktop)

    Connector

    https://api.vibe-test.tech/mcp

    Settings → Connectors → Add custom connector, paste this address, then Connect.

  • Claude Code

    Terminal

    claude mcp add --transport http vibe-test https://api.vibe-test.tech/mcp

    Run it in a terminal, then type /mcp in Claude Code and sign in.

  • Cursor

    Install link

    cursor://anysphere.cursor-deeplink/mcp/install?name=vibe-test&config=eyJ1cmwiOiJodHRwczovL2FwaS52aWJlLXRlc3QudGVjaC9tY3AifQ==

    Open it in your browser and Cursor adds the server; sign in when it connects.

  • VS Code

    Terminal

    code --add-mcp '{"name":"vibe-test","type":"http","url":"https://api.vibe-test.tech/mcp"}'

    Run it in a terminal; VS Code asks you to sign in when the server starts.

Sign in

  • Sign-in is OAuth in your browser: continue with Google or GitHub (or your Vibe Test email). Your password is never given to the assistant.
  • New to Vibe Test? Signing in creates your account and starts the free trial.
  • A consent screen then names the app and what it may do as you — read your projects, runs, bugs, tickets and chat; start runs and builds, which use credits; write on your board and trackers; report and fix bugs, and stop runs. Press Allow to connect, or Deny.
  • To disconnect, open Account → Connected apps and press Disconnect: that app loses access at once. Removing the server from your client stops it from asking again.

Tools

Every tool the server offers, read from the server itself. Read-only tools only read; the others start work or change something, exactly as the matching button on the website does.

  • See your projects

    vibe_projectsRead-only

    List your Vibe Test projects that developer tools may use: name and id, type (web / Android / iOS), open bug count, connected repositories, and the server it lives on.

  • Set up Vibe Test for your app

    vibe_get_startedMakes changes

    Set up a new Vibe Test project from this chat, the way the website's New project does it for a developer, in its order: 1 «How do you work?», 2 «Where's your code?», 3 «Review and activate».

  • Your app's logins

    vibe_setup_loginMakes changes

    The app's logins.

  • Create a new project

    vibe_create_projectMakes changes

    Create a Vibe Test project for the repository open in the editor, the way the website's "New project" does, and connect that repository to it as its Primary repository.

  • See or change your project's settings

    vibe_project_setupMakes changes

    A Vibe Test project's setup and settings.

  • See what Vibe Test can run

    vibe_catalogRead-only

    List what can be started on one Vibe Test project right now.

  • Start a test or task

    vibe_startMakes changes

    Start one Vibe Test service on a project.

  • Check a merged change again

    vibe_test_changeMakes changes

    Change Testing checks every change of a project by itself when it merges, and posts the result on the pull request; follow those checks with vibe_runs and vibe_run_status.

  • Follow a test while it runs

    vibe_run_statusRead-only

    Follow a Vibe Test run by its run number — any service: state, current step of how many, elapsed time and link; when finished, the verdict, a short summary and the bugs it found (id and title).

  • Stop a running test

    vibe_stopMakes changes

    Stop a Vibe Test run by its run number — any service — exactly as the website's Stop button does, as you: Vibe ends the run on its servers and marks it stopped by user.

  • Find past tests

    vibe_runsRead-only

    List the runs of one of your Vibe Test projects, newest first.

  • What happened

    vibe_historyRead-only

    The full timeline of what happened on a project, a ticket or bug, a run, a story flow or a pull request, in order.

  • Read a test's full report

    vibe_why_failedRead-only

    Read the full report of a finished Vibe Test run by its run number.

  • See the bugs Vibe Test found

    vibe_bugsRead-only

    List the open bugs of one of your Vibe Test projects, sorted by latest activity (most recent first).

  • Open one bug or act on it

    vibe_bugMakes changes

    Read one Vibe Test bug in full by its id (as vibe_bugs lists it, e.g. #12 or IA-1877).

  • Report, judge or fix a run's findings

    vibe_findingsMakes changes

    The findings of one run (Explore, Journeys, Regression, scenario, sanity ring, story test…), each with where its ticket stands now, and every button the website's run report has on them.

  • Check a bug again

    vibe_retest_bugMakes changes

    Start a Vibe Test re-test of one bug by its id (as vibe_bugs lists it).

  • Ask Vibe a question

    vibe_askMakes changes

    Ask Vibe — the project chat of Vibe Test — a question about a project, in the developer's words: what is broken, what a run found, what to test next, how a feature behaves, or to propose a test.

  • Read Vibe's reply

    vibe_answerMakes changes

    Read Vibe's answer to a question asked with vibe_ask, by its turn number.

  • Pick one of Vibe's suggestions

    vibe_pressMakes changes

    Press one card Vibe proposed in its answer (vibe_ask / vibe_answer list them with ids).

  • See or change your board's tickets

    vibe_ticketMakes changes

    Read or change tickets on a Vibe Test project's tracker (Jira and the trackers on its pipeline, GitHub Issues, One Studio, the Vibe Board).

  • Build a feature from one sentence

    vibe_storyMakes changes

    Take one story from a one-line request to Done on a Vibe Test project: write it, review it (with questions for the developer), build it, merge it, test it, close it.

  • Save your app's login

    vibe_test_accountMakes changes

    The logins Vibe Test signs in to the app with, on one environment of a Vibe Test project.

  • Connect your task board

    vibe_connect_trackerMakes changes

    Connect a tracker to a Vibe Test project, as Settings → Tracker does, then read back the boards, columns or labels it sees.

  • What Vibe Test can do

    vibe_helpRead-only

    What Vibe Test can do from this IDE, as example requests the developer can say.

Example requests

Say it the way you would to a teammate. The assistant picks the tool:

  • “List my Vibe Test projects.”vibe_projects
  • “Check my latest push on this branch.”vibe_test_change
  • “Show the open bugs on this project.”vibe_bugs
  • “Fix bug #9.”vibe_bug
  • “Run a regression on staging.”vibe_start

Credits and permissions

  • Reading costs nothing: projects, runs, reports, bugs, tickets and run status.
  • Starting work uses the project's plan credits, the same amount as on the website: change checks, re-tests, bug fixes, explorations, journeys, regressions, scenarios, stories, app builds, pressing a card that starts a run, and moving a ticket into a column that starts a service. The assistant says what it started and its cost.
  • Asking Vibe a question counts against your daily chat allowance, as in the website's chat.
  • The assistant can do only what you can do on the website: your projects and the ones shared with you, with your role there. What the website refuses — limits, credits, roles — the assistant is refused too.
  • A project's owner or organization admin can turn access off for that project in Settings → General → “Allow access from developer tools”; it is then hidden from every assistant.
  • Passwords and tokens you give it are write-only and never shown back. Before it writes to your tracker, the assistant shows what it will write and waits for your yes.

Support and privacy