Vynix MCP server

A Model Context Protocol server that gives AI coding agents (Claude, Copilot, Cursor and more) direct access to your Vynix annotations, so an agent can read the feedback, see the captured context and screenshots, run an AI diagnosis, generate a fix prompt, open a GitHub issue, update status, and comment, all without leaving the editor.

Every tool carries MCP annotations (read-only / idempotent / open-world hints) so a client can auto-approve safe reads and confirm before writes, AI spend, or GitHub calls.

Tools

Read-only:

Writes (a client should confirm these):

Related MCP server: yo-bug

Prompts

Install

The server is published on npm. Most MCP clients (Cursor, VS Code, Claude Desktop and more) just need a command and a token, and npx fetches and runs it automatically with no global install. Requires Node.js 18+:

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

Generate your token from the Vynix dashboard at https://www.vynix.in/mcp. Config file locations: Cursor ~/.cursor/mcp.json, VS Code .vscode/mcp.json, Claude Desktop claude_desktop_config.json. VS Code uses a top-level "servers" key instead of "mcpServers"; everything else is identical.

Configure

Authenticate with either a token (recommended) or email and password:

• VYNIX_API_URL - your Vynix API base URL (default https://www.vynix.in).

• VYNIX_API_TOKEN - a token generated at https://www.vynix.in/mcp, or

• VYNIX_API_EMAIL + VYNIX_API_PASSWORD - the server logs in on demand and refreshes the token automatically when it expires.

Build from source

For contributors who want to run the server from a local checkout:

git clone https://github.com/vynix-in/vynix-mcp.git
cd vynix-mcp
npm install
npm run build
npm start          # runs dist/index.js over stdio
npm run dev        # watch mode with tsx
npm test           # smoke test: launches the server and verifies the tool + prompt surface

Then point your client at the built file instead of npx:

{
  "mcpServers": {
    "vynix": {
      "command": "node",
      "args": ["/absolute/path/to/vynix-mcp/dist/index.js"],
      "env": {
        "VYNIX_API_URL": "https://www.vynix.in",
        "VYNIX_API_TOKEN": "PASTE_YOUR_TOKEN_HERE"
      }
    }
  }
}

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