Vynix

What Vynix MCP server does

The Vynix MCP server exposes Vynix project feedback to MCP-compatible coding agents. Its supported context includes visual annotations, screenshots, page metadata, target elements, browser console and network details, bug reports, diagnostics, comments, and issue status. The server also supports workflows that turn feedback into coding prompts, GitHub issues, status updates, and comments.

The Vynix MCP server includes 17 production tools for read and write operations. It also publishes resources describing server metadata, tools, prompts, skills, and contextual summaries. Workflow prompts cover QA, release readiness, product-management briefings, and engineering planning.

How it works

An MCP client communicates with the local process over stdio or with a hosted deployment over Streamable HTTP. The server calls the Vynix API for projects, annotations, screenshots, and diagnostic information. GitHub operations are handled through the Vynix backend rather than by giving the agent a separate GitHub connection.

Read and mutating operations are both available. MCP annotations identify read-only, idempotent, and open-world behavior so compatible clients can apply more appropriate approval rules. The diagnose_annotation tool may invoke external AI providers configured in the Vynix workspace; other capabilities are not described as sending data to those providers.

Setup and configuration

Node.js 18 or newer is required for the package-based installation. The recommended local configuration runs the npm package with npx -y @usevynix/mcp-server. Set VYNIX_API_TOKEN for token authentication, or provide both VYNIX_API_EMAIL and VYNIX_API_PASSWORD for the fallback login flow. VYNIX_API_URL defaults to https://www.vynix.in and can be changed when needed.

The server can run locally in stdio mode or as an HTTP service. HTTP deployments use VYNIX_MCP_MODE=http and can be configured with VYNIX_MCP_HOST, VYNIX_MCP_PORT, and VYNIX_MCP_PATH. The repository also provides a Docker image and instructions for running the built application directly. A hosted Streamable HTTP endpoint is available at https://mcp.vynix.in/mcp, with OAuth discovery exposed separately.

Claude Desktop, Cursor, VS Code, and Windsurf each require MCP configuration, although VS Code uses a top-level servers object while the other examples use mcpServers. Diagnostics are written to stderr so stdout remains available for MCP protocol traffic.

Tools and capabilities

Use the Vynix MCP server when an agent must reason from evidence captured during visual testing instead of from a text-only bug description. Its workflows support reviewing feedback, investigating diagnostics, producing implementation prompts, creating or updating GitHub issues, changing workflow status, and adding comments. Resource and prompt catalogs help clients discover the available tools and workflow guidance.

Limitations and notes

The server is not read-only, so write actions may change feedback or issue state. Protect API credentials and avoid committing tokens to source control. A missing token or incomplete fallback login produces a configuration error, while an invalid token can result in a 401 response. If no tools appear, verify the client-specific configuration key and, for hosted mode, check the HTTP mode and health endpoint.

The Vynix MCP server is MIT licensed. Self-hosting is supported through local stdio execution or HTTP deployment behind infrastructure managed by the operator.