VyBit

Name: vybit
Author: bitovi

Suggest features, change designs, draw mockups, and report bugs in your browser and send them to your favorite coding agent (Claude, Cursor, Copilot, etc) to be implemented. VyBit works with React or Angular apps built with Tailwind v3 or v4.

VyBit - Click and Change - HD 1080p

Watch a video going over its features

VyBit changes how you can design and build an app or website. Instead of building your design system and page designs in Sketch or Figma and then implementing it in code, you:

Step No	Task	How
1	Vibe code your design system	`Claude, build a button, card and badge. Add storybook.`
2	Use VyBit to fine-tune your design system in Storybook - Adjust colors, spacing, shadows, layout and more
3a	Use VyBit to design features - drop your design system components into pages
3b	Use VyBit to design features - sketch a feature with the design canvas
3c	Use VyBit to report bugs - send recent errors, console.logs, DOM snapshots, and events
4	Add text or voice messages for extra context

Plus, VyBit always knows what page, components, and elements you're editing, making it easier for agents to know exactly what you want!

Installation

To use VyBit:

Add its MCP tools to your agent
Start the MCP connection
Have your app or website load the VyBit Editor script

Add MCP tools to your agent

VyBit uses MCP to tell your agent to implement the changes you commit.

Add VyBit to your Agent's MCP configuration. Below we've listed what these configurations might look like for different agents. The most important things to know are:

VyBit is a Node project. So you will need NodeJS >= 18.
VyBit runs using STDIO (not HTTP), so you will often need some sort of command or stdio configuration.
VyBit needs to run where your React app's package.json is.

Copilot in .vscode/mcp.json

{
	"servers": {
		"vybit": {
			"type": "stdio",
			"command": "npx",
			"args": ["@bitovi/vybit"],
			"cwd": "${workspaceFolder}/packages/client"
		}
	},
	"inputs": []
}

Claude Code in .mcp.json

{
  "mcpServers": {
    "vybit": {
      "command": "npx",
      "args": ["@bitovi/vybit"],
      "cwd": "/path/to/your/project"
    }
  }
}

Running inside Docker

If your app runs in a Docker container, run VyBit inside the container instead of on the host. This is necessary because VyBit needs access to your project's node_modules to resolve Tailwind — which only exist inside the container, not on the host.

Replace the npx command with docker exec. For example, Claude Code in .mcp.json:

{
  "mcpServers": {
    "vybit": {
      "command": "docker",
      "args": ["exec", "-i", "<your-container-name>", "npx", "@bitovi/vybit"]
    }
  }
}

You can find your container name by running docker ps.

You also need to expose port 3333 so the browser can load the editor overlay script. Add it to your docker-compose.yml (or override file):

ports:
  - "3000:3000"
  - "3333:3333"

Then restart your containers for the port mapping to take effect.

Start the MCP connection

Different agents connect to an MCP service in different ways:

Copilot

Click start

Add the Editor script

The Editor script adds the VyBit editor panel. The script needs to be added to any pages you want to edit.

The best way to add the editor script is to have your agent do it! Paste the following into your agent:

I would like to use [VyBit](https://github.com/bitovi/vybit) on every page of this application.
Please make sure we can load the overlay script at `http://localhost:3333/overlay.js` in a non-blocking way.
Here's some suggested code to add in the `<head>` of every page in development mode:

\```html
<script>
if (location.hostname === 'localhost') {
   const s = document.createElement('script');
   s.src = 'http://localhost:3333/overlay.js';
   document.head.appendChild(s);
}
</script>
\```

Use

To start a session, you need to:

Tell your agent to start pulling changes and implementing features
Use the Editor to make changes
Commit those changes to send them to the agent

Telling your agent to start making features

In your agent, run the following prompt:

Please implement the next change and continue implementing changes with VyBit.

This will have your agent start a loop where it waits for changes, implements them, and then waits for new ones.

Use the Editor to make changes

You should see an editor icon like this:

Click it. It will open the Editor Panel.

Using the Editor to make changes

More on this later. But in short, click an element, then you can adjust the design of it, or insert a panel to draw out changes. You can also add contextual messages. These are all draft changes until you commit.

Committing changes

Once you have the changes you want to make, you can click the drafts button. This will show you a list of changes. Click Commit All to send them to the agent to be implemented:

Storybook Integrations

VyBit offers two separate Storybook integrations. Each requires its own setup. Both work with Storybook 8 and Storybook 10.

1. Drag Components from Storybook into Your Page

The VyBit editor's Components tab lists your Storybook stories so you can drag them directly onto your page. VyBit's MCP server auto-detects your running Storybook by scanning ports 6006–6010. No extra installation is needed — just make sure Storybook is running before starting VyBit.

To use a different port or URL, set the STORYBOOK_URL environment variable:

STORYBOOK_URL=http://localhost:7000 npx @bitovi/vybit

2. Use the VyBit Panel Inside Storybook

You can embed the VyBit editor panel as a tab directly inside your Storybook UI. The addon auto-detects whether you're running Storybook 8 or 10 and loads the correct entry points.

Because VyBit is typically run via npx in the MCP config (not installed locally), you need to add it as a dev dependency so Storybook can resolve the addon.

Install it in the same package where Storybook is a dependency (this may be a subdirectory in a monorepo):

npm install --save-dev @bitovi/vybit

Then register the addon in .storybook/main.ts:

export default {
  addons: ['@bitovi/vybit/storybook-addon'],
};

The VyBit editor panel will now appear as a "Vybit" tab inside your Storybook.

MCP Tools

There are other MCP tools you can use if you don't want to work in the implement loop:

Tool	Description
`implement_next_change`	Start here. Waits for the next committed change, returns implementation instructions, and requires the agent to apply it, mark it done, then call this tool again in an endless loop.
`get_next_change`	Returns the next committed change as raw patch data (no workflow instructions). Use this for custom agent workflows.
`mark_change_implemented`	Marks one or more changes as implemented by ID. Returns a directive to call `implement_next_change` again.
`list_changes`	Lists all changes grouped by status (`staged`, `committed`, `implementing`, `implemented`).
`discard_all_changes`	Clears the entire change queue.

Port Configuration

Use the PORT environment variable to change the server port (default: 3333):

PORT=4000 npx @bitovi/vybit

Contributing

Issues and PRs welcome at github.com/bitovi/vybit.

vybit