Vibe MCP Server

Client library for integrating browser games with Vibe Eyes MCP debug server. Exposed over MCP by the vibe mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A lightweight client library to integrate browser games with the Vibe Eyes MCP debug server for real-time debugging, visualization, and analysis.

• Automatic canvas screenshot capture and streaming
• Console log and error collection with timestamps
• Global error and unhandled promise rejection handling
• SVG visualization display in a dedicated debug window
• Complete debug stats with SVG size measurements
• Minimal performance impact on games

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at vibe-eyes-client on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by monteslu; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Vibe's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the vibe mcp server does with a few real requests.