@vibefix/mcp

@vibefix/mcp

Browse bug bounties and submit fixes on VibeFix directly from Claude Code, Cursor, Windsurf, or any MCP-compatible AI coding tool.

Setup

1. Get an API key

Sign in to VibeFix as a developer → Dashboard → MCP / API → Generate Key.

2. Add to your MCP client

Claude Code (~/.claude.json):

{
  "mcpServers": {
    "vibefix": {
      "command": "npx",
      "args": ["@vibefix/mcp"],
      "env": {
        "VIBEFIX_API_KEY": "vf_your_key_here"
      }
    }
  }
}

Claude Desktop (claude_desktop_config.json) — same config above.

Cursor / Windsurf — go to Settings → MCP Servers and paste the same JSON.

3. Start using it

Ask your AI assistant:

"List open VibeFix bounties for deployment bugs" "Show me the full details for job j57..." "Submit my fix for job j57... — here's what I changed: ..."

Available tools

Tool	Description
vibefix_list_jobs	Browse open bounties — filter by category, platform, difficulty
vibefix_get_job	Full job details: description, expected vs actual behavior, stack
vibefix_my_profile	Your XP, level, wallet balance, and approval status
vibefix_my_submissions	Your submitted fixes with acceptance status
vibefix_apply_to_job	Apply to a private job with an intro message
vibefix_submit_solution	Submit your fix with a description and repo link

Filters for vibefix_list_jobs

• category: deployment auth payments bug_fix performance other
• platform: cursor bolt lovable replit v0 other
• difficulty: easy medium hard

Environment variables

Variable	Required	Default	Description
VIBEFIX_API_KEY	Yes	—	Your API key from vibefix.io/dashboard/mcp
VIBEFIX_URL	No	https://vibefix.io	Override for self-hosted instances

How it works

The MCP server connects to the VibeFix API at vibefix.io/api/mcp/v1. Your API key authenticates write operations (apply, submit). Browsing open jobs requires no key.

License

MIT