😤 The Problem Every Dev Team Has

Your QA team logs bugs in Google Sheets. Smart. Organized. Totally fine.

Then the dev gets pinged.

Here's what actually happens next:

1. Open the sheet (Tab 1)

2. Find your assigned bug (scroll, scroll, find the row)

3. See a Snipboard screenshot link — click it (Tab 2)

4. Look at the image. Describe it mentally.

5. Switch back to your code (Tab 3 — or VSCode — or wherever)

6. Try to fix something you're now half-remembering

7. Go back to the sheet (Tab 1, again)

8. Manually type Devdone — or mis-type DevDone and break the dropdown

That's 6+ context switches. Per bug. Every single time.

20 bugs a day? You just spent your morning on tab gymnastics.

And the worst part? Your AI assistant never saw the screenshot. You're out here describing UI bugs in plain text like it's 2019.

Related MCP server: chrome-devtools-mcp

💡 There Is a Better Way

buglens is an MCP server that plugs directly into your editor and closes the entire loop — automatically.

Pull the bug → AI sees the screenshot → Fix the code → Devdone auto → Done ✅

Your AI reads the sheet live (not a CSV export — live), fetches the Snipboard link, actually sees the visual bug, fixes your code, and marks it Devdone. You never left your editor. You never opened a tab. You never typed a status.

🎯 How It Works

🌳 Project Structure

• 📄 __init__.py

• 📄 server.py — Main MCP server containing 8 registered tools

• 📄 GEMINI.md — Gemini agent specific configurations

• 📄 CLAUDE.md — Claude agent specific configurations

• 📄 AGENTS.md — General cross-agent context metrics

• 📄 VIBE.md — Guidelines for autonomous vibe coding sessions

• 📄 DEV.md — Developer workspace log book

• 📜 pyproject.toml — Project metadata and package dependencies

• 🚫 .gitignore — Ignore specs for builds, credentials, and virtual envs

• 📖 README.md — This roadmap documentation

Installation

1. Create venv

python3 -m venv venv source venv/bin/activate

2. Install from GitHub

pip install git+https://github.com/iambilalshahid/buglens.git

3. Or for local dev

git clone https://github.com/iambilalshahid/buglens.git cd buglens pip install -e .

[Jump to Gemini Installation](./AGENTS/GEMINI.md)

</details>

<details>
<summary><b>Clone for local dev / contribution</b></summary>

```bash
git clone https://github.com/iambilalshahid/qa-sheet-mcp.git
cd qa-sheet-mcp
python3 -m venv venv
source venv/bin/activate
pip install -e .

⚙️ Configuration

Add this block to your mcp.json — works with Cursor, Claude Desktop, and Antigravity.

{
  "mcpServers": {
    "qa-sheet": {
      "command": "python",
      "args": ["-m", "qa_sheet_mcp.server"],
      "env": {
        "SHEET_ID": "your-sheet-id-here",
        "WORKSHEET_NAME": "Admin bug report",
        "GOOGLE_CREDS_PATH": "./credentials.json",
        "QA_ASSIGN_TO": "Bilal",
        "QA_PROBLEM_TYPE": "FE"
      }
    }
  }
}

🔄 Status Workflow

Every transition is validated. No more typos silently breaking your dropdown.

stateDiagram-v2
    [*] --> Open
    Open --> InProgress
    InProgress --> Devdone
    InProgress --> ServerDone
    Devdone --> QA
    ServerDone --> QA
    QA --> Verified
    QA --> ReOpen
    ReOpen --> InProgress
    Verified --> [*]

Valid values: Open · In-Progress · Devdone · QA · Re-Open · Verified · Discussion · Hold · Server Done

🛠️ The 7 Tools

🤝 Contribute

Open source, solo-built, PRs welcome — especially for:

• New tool ideas (comment on a bug row? bulk update?)

• More integrations: Notion, Jira, Linear

• Better vision prompting strategies

git clone https://github.com/iambilalshahid/qa-sheet-mcp.git
git checkout -b feature/your-idea
git commit -m "Add: your feature"
git push origin feature/your-idea
# → Open a Pull Request

👤 Author

Bilal Shahid — Solo Dev GitHub: @iambilalshahid