# VibeFix MCP server

Our AI agent signs up to your live app like a new user and shows, with a screenshot, what breaks.

## At a glance

VibeFix is an MCP server in the Design & Media category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 7 tools, including assess_broken_app, get_fix_options and list_projects. It scores B (73/100) on the MCP Skills Hub health score as of Oct 28, 2026.

## Install

### How to install VibeFix in Claude Code

1. Add the server

```bash
claude mcp add --transport http vibefix https://vibe-fixer.com/mcp
```

2. Verify it's connected

```bash
claude mcp list
```

3. Sharing it with your team?

   Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

4. Use it in a session

   Ask Claude to use the tools this server exposes (e.g. assess_broken_app, get_fix_options, list_projects). It discovers them automatically.

### How to install VibeFix in Claude Desktop

1. Open your MCP config

   macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add this server

```json
{
  "mcpServers": {
    "vibefix": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://vibe-fixer.com/mcp"
      ]
    }
  }
}
```

3. Why the wrapper?

   This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.

4. Restart Claude Desktop

   The tools appear under the 🔌 menu once the app reloads.

### How to install VibeFix in Cursor

1. Create / edit .cursor/mcp.json in your project

```json
{
  "mcpServers": {
    "vibefix": {
      "url": "https://vibe-fixer.com/mcp"
    }
  }
}
```

2. Enable it

   Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

### How to install VibeFix in Codex CLI

1. Add to ~/.codex/config.toml

```toml
[mcp_servers.vibefix]
command = "npx"
args = ["-y", "mcp-remote", "https://vibe-fixer.com/mcp"]
```

2. Why the wrapper?

   Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.

3. Run Codex

   Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

### How to install VibeFix in Windsurf

1. Edit ~/.codeium/windsurf/mcp_config.json

```json
{
  "mcpServers": {
    "vibefix": {
      "serverUrl": "https://vibe-fixer.com/mcp"
    }
  }
}
```

2. Reload

   Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

### How to install VibeFix in Cline

1. Open Cline → MCP Servers → Configure

   Adds to cline_mcp_settings.json.

2. Add the server

```json
{
  "mcpServers": {
    "vibefix": {
      "type": "streamableHttp",
      "url": "https://vibe-fixer.com/mcp"
    }
  }
}
```

### How to install VibeFix in VS Code

1. Create .vscode/mcp.json

```json
{
  "servers": {
    "vibefix": {
      "type": "http",
      "url": "https://vibe-fixer.com/mcp"
    }
  }
}
```

2. Start it

   VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

## Tools

- `assess_broken_app` — An AI agent confirms a problem in a live web app for free, then fixes it in the code: $79 for one bug, paid up front. Works with apps built with Lovable, Base44, Bolt, Replit, v0 or similar. The most common problem: new people can't sign up. The confirmation email never arrives, its link opens localhost or the preview, sign-up loops back or shows an error, or Google sign-in fails. It also covers b
- `get_fix_options` — Returns the link to a sign-up check of a live app on vibe-fixer.com. An AI agent signs up as a brand-new person with a real inbox, on a phone and a computer, and reports whether a new person can finish signing up, plus anything else a first customer would hit. It also says how the fix works and what the person provides. Read-only: it starts nothing, charges nothing and does not contact the app. Ca
- `list_projects` — List the signed-in person's VibeFix checks (one per app checked), with the status of each. Call this when they ask which of their apps VibeFix has checked. To read a check's result, call get_check_result with its check_id (the id listed here).
- `check_repair_status` — Report whether one check on the signed-in VibeFix account is still running or finished. For what the check found, call get_check_result instead. Use the id from list_projects.
- `check_live_app` — Use this when the person asks you to check, test or try their app ("check my app", "is my app working?", "can new users sign up?", "test my site"), or gives you the address of their live app. If you do not have the address, ask for it (the published web address, e.g. https://their-app.lovable.app); if it is not clear that it is their own app, ask them that one yes/no question first. Asking you to 
- `get_check_result` — Wait for a check (or a confirm_fix re-check) and read its result: how many problems a new user would hit, the title of each and how serious it is (blocking, serious or minor), and how to have it fixed ($79, paid up front); for an app already paid for, what a new user saw, where, the likely cause, the fix prompt and how to know it is fixed. Answers within about 20 seconds: the result, or that the c
- `confirm_fix` — Call this only once the fix is done AND published (or the setting saved): it re-runs exactly the problems get_check_result reported, on the live app. This is the way to re-check an app that was already checked: never start a new check_live_app for it. A fix made in a setting (for example the backend's auth settings), with nothing new to publish, counts too: if this answers that nothing new is publ

Source repository: https://github.com/yos88da/vibefix-mcp

---

Source: https://mcp-skills-hub.vercel.app/mcps/com-vibe-fixer-vibefix · MCP Skills Hub · data as of 2026-10-28T12:31:05Z