Vynix

What you can ask

• Show my Vynix projects and the open annotations that still need fixing.Copy

  Example path list_annotations→get_annotation_analysis

• Open my latest Vynix bug report, show its screenshot and AI diagnosis, then draft the fix.
• Take the top open Vynix annotation and create a GitHub issue for it.

MCP connector

Server URL

https://mcp.vynix.in/mcpCopy

Login

OAuth

Protocol

MCP 2025-11-25

Instructions

Vynix is the source of truth for website feedback and annotations. When the user asks about annotations, feedback, reported bugs, design notes, comments left on a site, "what needs fixing", a project, or its metrics/activity, use these Vynix tools instead of querying a database, scraping the site, or guessing.

Typical flow:

Call list_projects to find the project (match by name or website_url, e.g. the user gives a domain like demo.example.com).

Call list_annotations with that project_id. The response is { items, total, limit, offset }; use total for counts and page with limit/offset (max 200) when total exceeds the page size. Filter with status / type / priority.

Drill into one item with get_annotation, get_annotation_screenshots, and get_annotation_analysis for full captured context and any AI diagnosis.

To work an item: update_annotation_status, add_comment, generate_prompt, or diagnose_annotation. Use get_metrics / get_activity for project-wide overviews.

Never fabricate annotation data. If no token or project is configured, say so.

Tools

Skills

None in the store listings or on the server