Vibelens Mcp
Let your agent visualize code changes with inline annotations inside VS Code or Cursor so you can review diffs faster before merge or release.
Overview
vibelens-mcp is a MCP server for the Ship phase that lets AI agents visualize code changes with inline annotations in VS Code and Cursor.
What is this MCP server?
- VibeLens MCP bridge for AI-driven visualization of code changes
- Inline annotations aimed at VS Code and Cursor workflows
- npm package vibelens-mcp v0.1.0 with stdio transport
- Requires YOUR_API_KEY for the VibeLens service
- Server version 0.1.0
- npm identifier vibelens-mcp
- 1 required secret env var YOUR_API_KEY
What problem does it solve?
Agent-generated patches are hard to trust when you only see raw diffs without contextual inline visualization in your editor.
Who is it for?
Solo builders using Cursor or VS Code who rely on agents for frequent edits and want a visual review layer before shipping.
Skip if: Teams in plain terminal-only workflows without VibeLens/editor support, or users who will not provision a VibeLens API key.
What do I get? / Deliverables
After you wire the server and API key, your agent can surface VibeLens-style annotated change views so you approve or reject edits with clearer spatial context.
- Agent-triggered visualizations of code changes with inline annotations
- Faster human review of AI-generated edits inside the editor
- MCP stdio bridge v0.1.0 between agent and VibeLens service
Recommended MCP Servers
Journey fit
How it compares
Editor-integrated change visualization MCP, not a standalone static code review checklist skill.
Common Questions / FAQ
Who is vibelens-mcp for?
Indie developers in VS Code or Cursor who want their agent to trigger VibeLens visualizations when reviewing AI-produced code changes.
When should I use vibelens-mcp?
Use it during ship review—before merge or release—when you need inline annotated views of diffs instead of parsing large unstructured patches.
How do I add vibelens-mcp to my agent?
Install the npm package vibelens-mcp, add stdio MCP configuration in Cursor or VS Code, set YOUR_API_KEY, and ensure the VibeLens editor integration is available in your environment.