mcp-browser-verify
mcp-browser-verify
Activation
- UI bug, layout mismatch, flow verification, auth journey, “sprawdź w przeglądarce”.
Procedure
- Define scenario: URL, credentials (if any), steps, expected result.
- Run scripted navigation.
- Capture evidence: screenshots + console/network errors.
- Report deltas + actionable fix hints.
Output
- Scenario + evidence + pass/fail + next fix step.
More from janjaszczak/cursor
mcp-memory-recall
Recall and reuse prior decisions, constraints, and artifacts using MCP memory (e.g., Neo4j). Use when the user references past work (“jak ostatnio”, “kontynuuj”), when resuming a project thread, or when a repeated topic suggests existing decisions.
7task-planning-shrimp
Plan, split, and track multi-step work using Shrimp Task Manager MCP (or equivalent). Use for multi-file refactors, migrations, or any work that benefits from task tracking.
7mcp-github-ops
Use GitHub MCP for issue/PR context, diffs, reviews, and automations. Use when the task references PR/issue numbers, review requests, or requires repo metadata beyond local git.
7solid-enforcer
Enforce SOLID design principles during code generation, refactors, and code review (SRP/OCP/LSP/ISP/DIP). Use when changing architecture, introducing new abstractions, reducing coupling, eliminating type-switches, or reviewing PRs for maintainability.
7mcp-shrimp-execution-loop
Combine Shrimp task tracking with execution loops (plan → execute → verify → update status). Use for multi-step deliveries where progress tracking matters.
6mcp-grafana
Query dashboards/logs/alerts to support incident analysis and regressions. Use when troubleshooting involves observability, incidents, latency, error rates.
6