Vynix

in.vynixPublished by vynix.inOfficial publisherv0.1.4Updated Oct 27, 2026

Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper ToolsAI & ML

Overview

AI-generated overview

Vynix MCP gives coding agents access to Vynix visual feedback, bug reports, screenshots, diagnostics and GitHub issue workflows.

What you can do
  • List projects, annotations, members and activity, and read a single annotation's captured page, element, DOM and runtime diagnostics
  • View region screenshots and comment threads attached to annotations
  • Read stored AI diagnoses, or run the AI Diagnosis Engine to get ranked root causes, confidence, a suggested fix and likely source files
  • Render ready-to-paste coding prompts for a target assistant
  • Create GitHub issues from annotations and list tracker issues per annotation or project
  • Update annotation status, add comments, and mint read-only public review links
When to use it
Useful when a team collects visual bug reports and feedback in Vynix and wants a coding agent to work from the real captured context instead of descriptions. It suits triage, diagnosis, prompt generation and GitHub issue handoff inside an existing Vynix workspace.
Requirements
A Vynix account and a personal access token in VYNIX_API_TOKEN (email/password fallback variables are also documented). Runs as a remote Streamable HTTP endpoint or locally via npx with Node.js 18+; VYNIX_API_URL is optional and defaults to the Vynix site. Network access to the Vynix API and, for issue tools, GitHub via the Vynix backend.
Before you install
Not read-only: tools change annotation status, post comments that notify the team, create GitHub issues and mint public share links. diagnose_annotation calls an external AI provider, uses tokens and may cost money. The API token is a credential and should not be committed; prefer short-lived tokens. Only diagnosis sends data to third-party AI providers, per the README.

Installation

In SourceWeft

  1. Open Vynix in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/in.vynix%2Fvynix-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "vynix": {
      "type": "http",
      "url": "https://mcp.vynix.in/mcp"
    }
  }
}

README

Vynix MCP Server

[npm version] [npm downloads] [license] [ci] [vynix-mcp MCP server]

Model Context Protocol server for Vynix. It gives coding agents direct access to visual feedback, bug reports, screenshots, diagnostics, comments, and issue workflows so agents can reason from real context instead of guessing.

Why Vynix

  • Feedback with evidence: page metadata, target element, screenshot, console/network context.
  • End-to-end execution: inspect feedback, diagnose, generate coding prompts, create GitHub issues, update status, comment.
  • Agent-safe hints: read-only/idempotent/open-world annotations for better approval behavior in MCP clients.
  • Registry-ready metadata for modern MCP directories.

Architecture

mermaid
flowchart LR  A[MCP Client\nClaude/Cursor/Copilot/VS Code] -->|stdio or streamable-http| B[Vynix MCP Server]  B --> C[Vynix API]  B --> D[GitHub API via Vynix backend]  C --> E[Projects]  C --> F[Annotations]  C --> G[Screenshots and diagnostics]

Features

  • 17 production tools for read and write workflows.
  • Resource catalog for server metadata, tool/prompt/skill references, and contextual summaries.
  • Workflow prompts for QA, release readiness, PM briefings, and engineering planning.
  • Dual transport support: stdio and Streamable HTTP.
  • Auth via API token or email/password refresh flow.

Installation

Node.js 18+ is required.

NPX (recommended)

json
{  "mcpServers": {    "vynix": {      "command": "npx",      "args": ["-y", "@usevynix/mcp-server"],      "env": {        "VYNIX_API_URL": "https://www.vynix.in",        "VYNIX_API_TOKEN": "PASTE_YOUR_TOKEN_HERE"      }    }  }}

npm global install

bash
npm install -g @usevynix/mcp-servervynix-mcp

Docker

bash
docker run --rm -i \  -e VYNIX_API_URL=https://www.vynix.in \  -e VYNIX_API_TOKEN=PASTE_YOUR_TOKEN_HERE \  ghcr.io/usevynix/vynix-mcp:latest

Local development

bash
git clone https://github.com/UseVynix/vynix-mcp.gitcd vynix-mcpnpm installnpm run buildnpm run checknode dist/index.js

Client Configuration

Claude Desktop

Use claude_desktop_config.json:

json
{  "mcpServers": {    "vynix": {      "command": "npx",      "args": ["-y", "@usevynix/mcp-server"],      "env": {        "VYNIX_API_TOKEN": "PASTE_YOUR_TOKEN_HERE"      }    }  }}

Diagnostics are written to stderr; stdout is reserved for the protocol stream.

Cursor

Use ~/.cursor/mcp.json.

json
{  "mcpServers": {    "vynix": {      "command": "npx",      "args": ["-y", "@usevynix/mcp-server"],      "env": {        "VYNIX_API_TOKEN": "PASTE_YOUR_TOKEN_HERE"      }    }  }}

VS Code

Use .vscode/mcp.json with top-level servers:

json
{  "servers": {    "vynix": {      "command": "npx",      "args": ["-y", "@usevynix/mcp-server"],      "env": {        "VYNIX_API_TOKEN": "PASTE_YOUR_TOKEN_HERE"      }    }  }}

Windsurf

Use your Windsurf MCP config file with this server block:

json
{  "mcpServers": {    "vynix": {      "command": "npx",      "args": ["-y", "@usevynix/mcp-server"],      "env": {        "VYNIX_API_TOKEN": "PASTE_YOUR_TOKEN_HERE"      }    }  }}

ChatGPT connectors

For hosted mode, use the Streamable HTTP endpoint:

  • Base URL: https://mcp.vynix.in/mcp
  • OAuth discovery: /.well-known/oauth-authorization-server

Generic mcp.json

See examples/configs/mcp.json.

Authentication

Environment variables:

  • VYNIX_API_URL (optional, default: https://www.vynix.in)
  • VYNIX_API_TOKEN (recommended)
  • VYNIX_API_EMAIL and VYNIX_API_PASSWORD (fallback login mode)
  • VYNIX_MCP_MODE (stdio or http)
  • VYNIX_MCP_HOST, VYNIX_MCP_PORT, VYNIX_MCP_PATH (HTTP mode)

Generate a token from: https://www.vynix.in/mcp

Tools, Prompts, and Resources

Examples

Troubleshooting

  • Not configured error: set VYNIX_API_TOKEN or both VYNIX_API_EMAIL and VYNIX_API_PASSWORD.
  • 401 errors: regenerate token and verify API URL.
  • No tools listed: confirm the MCP config key (mcpServers vs servers) for your client.
  • Hosted mode not reachable: verify VYNIX_MCP_MODE=http and check /health.

FAQ

Does this send data to third-party AI providers?

Only diagnose_annotation can invoke external AI providers through your Vynix workspace configuration.

Is this read-only?

No. It includes read tools and write tools. MCP annotations identify mutating/open-world calls so clients can request confirmation.

Can I self-host?

Yes. Run in stdio mode locally or HTTP mode behind your own infrastructure.

Contributing

See CONTRIBUTING.md. For local validation run:

bash
npm run check

Security

  • Never commit API tokens.
  • Prefer short-lived tokens where possible.
  • See SECURITY.md (create one if your org requires a disclosure policy).

License

MIT

Changelog

CHANGELOG.md

Source: README.md at commit d60e3db

Tools

17

list_projects

List projects

List the Vynix projects you own.

Takes no parameters.

list_annotations

List annotations

List a project’s annotations, optionally filtered by status, type, or priority. Start here with status "open" to see what needs fixing.

Parameterstypelimitoffsetstatuspriorityproject_idrequired

get_annotation

Get annotation

Fetch one annotation with its full captured context: page, target element (selector, XPath, styles), surrounding DOM, and runtime diagnostics (console + network).

Parametersannotation_idrequired

list_comments

List comments

Read the discussion thread on an annotation.

Parametersannotation_idrequired

get_annotation_analysis

Get AI diagnosis

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.

Parametersannotation_idrequired

get_annotation_screenshots

Get screenshots

Return the region screenshots attached to an annotation as viewable images, so you can see exactly what the reporter pointed at.

Parametersannotation_idrequired

list_annotation_issues

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).

Parametersrefreshannotation_idrequired

list_project_issues

List project issues

List every tracker issue across a project, with an open/closed/agent summary.

Parametersproject_idrequired

generate_prompt

Generate coding 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.

Parameterstargetannotation_idrequired

get_metrics

Get metrics

Overview of your projects: KPI counts, status breakdown, a daily time series, and recent activity.

Takes no parameters.

list_members

List members

List a project’s team members, including role and status.

Parametersproject_idrequired

get_activity

Get activity

Recent activity feed for a project (status changes, comments, issues, members).

Parametersproject_idrequired

update_annotation_status

Update status

Update an annotation’s status, e.g. to mark it in_progress or completed.

Parametersstatusrequiredannotation_idrequired

add_comment

Add comment

Add a comment to an annotation’s thread, e.g. to record what you changed. Notifies the team.

Parametersbodyrequiredannotation_idrequired

diagnose_annotation

Run AI diagnosis

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.

Parametersmodelproviderannotation_idrequired

create_github_issue

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.

Parametersrepoassigneesannotation_idrequired

Version history

1
  1. v0.1.4LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts