Vynix MCP
Vynix: Visual Website Feedback for AI Coding Agents Capture visual website feedback with annotated screenshots, element inspection, browser annotations, DOM…
What it can do
- List Projects: List the Vynix projects you own.
- List Annotations: List a project’s annotations, optionally filtered by status, type, or priority. Start here with status "open" to see what needs fixing.
- Get Annotation: Fetch one annotation with its full captured context: page, target element (selector, XPath, styles), surrounding DOM, and runtime diagnostics (console + network).
What data it sees
Do you need an account
An API key from the service settings is required
Vynix: Visual Website Feedback for AI Coding Agents
Capture visual website feedback with annotated screenshots, element inspection, browser annotations, DOM context, console logs, network requests, and AI-ready metadata.
Vynix helps developers, designers, QA teams, product managers, agencies, and AI coding agents reproduce and fix bugs faster by turning visual feedback into structured, actionable reports.
Features
- 📸 Capture annotated screenshots
- 🎯 Inspect page elements with browser annotation
- 📝 Add visual website feedback
- 🌐 Collect URL, viewport, browser/device info, and DOM context
- 🐞 Capture console errors and network requests automatically
- 🤖 Generate AI-ready reports for MCP-compatible coding assistants
- 🔗 Create shareable feedback links
- 🔒 Cloud or self-hosted deployment
- ⚡ Connect coding agents via the Vynix MCP Server
Best For
- Website bug reporting
- Website QA
- Client feedback collection
- Browser annotation workflows
- AI-assisted debugging
- Website review and fix loops
Resources
- 🌐 Website
- 📖 Docs hub
- 🔌 MCP docs
- 🧩 Browser extension docs
- 🔧 GitHub MCP server
- 🏪 Chrome extension
- 💬 Contact
Turn website feedback, browser annotations, and visual bug reports into actionable issues with complete visual and technical context.
How to connect
How to connect Vynix MCP to Claude
The server address to paste into Claude settings:
https://vynixmcp.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Vynix MCP to ChatGPT
The server address to paste into ChatGPT settings:
https://vynixmcp.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Vynix MCP to Cursor
The server address to paste into Cursor settings:
https://vynixmcp.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (17)
Raw names from tools/list. Only developers need these.
| list_projects | List the Vynix projects you own. |
| list_annotations | List a project’s annotations, optionally filtered by status, type, or priority. Start here with status "open" to see what needs fixing. |
| get_annotation | Fetch one annotation with its full captured context: page, target element (selector, XPath, styles), surrounding DOM, and runtime diagnostics (console + network). |
| list_comments | Read the discussion thread on an annotation. |
| get_annotation_analysis | Read the latest stored AI diagnosis for an annotation (root causes, confidence, suggested fix, and likely source files). Returns null when none has been generated yet; run diagnose_annotation to create one. |
| get_annotation_screenshots | Return the region screenshots attached to an annotation as viewable images, so you can see exactly what the reporter pointed at. |
| list_annotation_issues | List the tracker (GitHub) issues opened from an annotation, with each issue’s live state. Set refresh to reconcile against GitHub (open/closed + any linked pull request). |
| list_project_issues | List every tracker issue across a project, with an open/closed/agent summary. |
| generate_prompt | Render a ready-to-paste coding prompt for an annotation, formatted for a target assistant. A deterministic template (no AI spend); for a deeper analysis use diagnose_annotation. |
| get_metrics | Overview of your projects: KPI counts, status breakdown, a daily time series, and recent activity. |
| list_members | List a project’s team members, including role and status. |
| get_activity | Recent activity feed for a project (status changes, comments, issues, members). |
| update_annotation_status | Update an annotation’s status, e.g. to mark it in_progress or completed. |
| add_comment | Add a comment to an annotation’s thread, e.g. to record what you changed. Notifies the team. |
| diagnose_annotation | Run the AI Diagnosis Engine on an annotation: it analyses the captured page, element, DOM, and runtime errors to produce ranked root causes, a confidence score, a suggested fix, and the likely source files. Calls an AI provider (uses tokens / may cost money) and stores the result. Requires AI + diagnosis enabled by the workspace admin and a key set. |
| create_github_issue | Create a GitHub issue from an annotation. Uses the project’s configured repo and assignee unless overridden. Embeds the generated AI prompt in the issue body. |
| create_share_link | Mint a read-only public review link for a project, so a stakeholder can review its annotations without an account. Reporter emails are hidden on shared views. |