Connect Vynix to Claude Code
Updated July 6, 2026
Claude Code lives in your terminal and edits your repo directly. Connect Vynix over MCP and Claude can list your open feedback, read the exact element and errors behind each note, and close the loop, all without you describing the bug twice.
Why connect Claude Code to Vynix
Claude Code is strongest when it has precise context. Vynix gives it exactly that: instead of "the pricing card is misaligned", Claude receives the selector, the computed styles, the viewport it broke at, and any console error captured at the moment the note was left. It reads that over MCP and goes straight to the right file.
Before you begin
- The Vynix widget installed on the site you collect feedback on.
- At least one annotation in a Vynix project.
- Claude Code installed and signed in.
- Node.js 18 or newer (the server runs via npx).
Get your Vynix API token
Create a personal API token in your Vynix account and copy it. The MCP server uses it to authenticate as you; it is revocable at any time.
Add the Vynix MCP server to Claude Code
The fastest way is the Claude Code CLI, which registers the server and its environment in one command:
claude mcp add vynix \ --env VYNIX_API_TOKEN=your-token-here \ -- npx -y @usevynix/mcp-server
Prefer a file you can commit? Add the same server to a project .mcp.json so your whole team shares it:
{
"mcpServers": {
"vynix": {
"command": "npx",
"args": ["-y", "@usevynix/mcp-server"],
"env": { "VYNIX_API_TOKEN": "your-token-here" }
}
}
}Run /mcp inside Claude Code to confirm the vynix server is connected and its tools are listed.
What Claude can do with your feedback
- Answer "what feedback do I have?" with the open batch and full context per note.
- Read an annotation's element, DOM, styles, and console and network errors.
- Generate a coding prompt or run an AI diagnosis with ranked root causes and likely files.
- Update status, add a comment, and open a GitHub issue, all in place.
A typical loop in Claude Code
Say "address my Vynix feedback on the checkout project." Claude lists the open notes, reads each one's captured context, makes the edits across your repo, and marks the notes resolved with a short comment on what it changed. You review the diff; the reviewers see the notes close.
Frequently asked questions
- CLI or .mcp.json, which should I use?
- Use the CLI for a quick personal setup. Use a committed .mcp.json when you want everyone on the repo to get the Vynix server automatically.
- Is my token safe?
- The token stays in your local Claude Code config and is sent only to the Vynix API as you. It is revocable from your account, so you can roll it whenever you like.
- Does it cost anything to run?
- The MCP server and the deterministic prompt generation are free. Running an AI diagnosis uses your own configured AI provider key, so that step is metered by your provider.