Skip to content
PixelFixer

Capture visual bugs with the context engineers need

Point at the broken element, describe what should happen, and PixelFixer attaches the page, screenshot, viewport, browser state, and available console or network signals to the report.

Create an accountCompare plans

Free for up to 3 projects. No card required.

Real task view/demo-team/website-bugs
PixelFixer task detail: a pinned screenshot marks the broken button, with viewport, selector, console and network context attached automatically

A report should contain the information needed to reproduce the issue

A screenshot without the page, viewport, browser state, and selected element often leaves the developer searching for the conditions again.

Incomplete report

  • No exact page or environment
  • Manual cropped screenshot
  • Unknown viewport and browser
  • Questions sent back to the reporter

PixelFixer report

  • Exact page URL
  • Screenshot captured with the report
  • Viewport and selected element
  • Browser and OS metadata
  • Console and network data where available

From report to resolved issue

The work stays on one project board instead of moving between email, chat, and spreadsheets.

  1. 01

    Connect a project

    Create a team and project, then install the widget or use the browser extension to capture issues.

  2. 02

    Capture the context

    Click on the problem area, write the expected result, and send the report to the board.

  3. 03

    Triage and resolve

    Assign the task, set priority and status, keep comments in context, and close the issue.

What the team gets

The focus is on capturing reliable context and working through the queue.

Visual capture

Click the element on the page and create the report at the exact location.

Automatic context

The report includes the page, viewport, browser metadata, selector, and available browser diagnostics.

Team board

Move issues through custom columns, assign owners, set priority, and keep discussion in context.

API and MCP

Read and create issues from scripts, internal tools, or an MCP client using scoped tokens.

Give automation access to the same issue queue

PixelFixer exposes a REST API, webhooks, and an MCP server. Create a scoped token in Settings → API Tokens and connect your assistant to the project.

Works with editors and assistants that support MCP. Each token acts with your permissions and project scope.

Read the MCP setup guide
MCP configuration example
{
  "mcpServers": {
    "pixelfixer": {
      "command": "npx",
      "args": [
        "-y",
        "@mudravaorg/mcp-server"
      ],
      "env": {
        "PIXELFIXER_API_URL": "https://pixelfixer.mudrava.com",
        "PIXELFIXER_API_TOKEN": "pf_your_token"
      }
    }
  }
}

Plans based on real usage

Start with the Free plan and increase limits when the team needs them.

Free

For a small team evaluating the workflow.

$0 /month

0 per year

  • Visual capture and automatic context
  • Kanban board, comments, and priorities
  • Browser and device metadata
  • API and MCP access
Create an account

Pro

Coming soon

For a team with several active projects and regular QA.

$19 /month

159 per year

  • 25 projects for active workstreams
  • Space for a larger QA and product team
  • Higher task limit for each project
  • More attachment storage

Paid plans are being rolled out. Request early access and we'll email you at launch.

Enterprise

Coming soon

For organizations that need larger limits and a direct agreement.

$49 /month

419 per year

  • Custom project limits
  • Unlimited team members
  • Unlimited tasks
  • 50 GB attachment storage

Paid plans are being rolled out. Request early access and we'll email you at launch.

Questions before you start

How do I start?

Create an account, create a team and project, then connect the widget or extension. You can also create reports through the API.

Which channels can create issues?

The embeddable widget, the browser extension, manual entry in the dashboard, API requests, and MCP clients.

What data is attached to a report?

Page URL, screenshot, viewport, browser and OS metadata, selected element, plus console or network data when it is available in the capture context.

Can reports stay internal?

Yes. Internal comments and project permissions keep team discussion separate from external feedback.

Can I manage limits later?

Plan limits apply to the team's current plan. Projects, members, tasks, storage, and API capacity are enforced from the plan configuration.

Who operates the infrastructure?

The service is hosted and operated by MUDRAVA on our own infrastructure. A self-hosted deployment is not offered.

Start with one project

Create an account and connect the first website to see how reports turn into work.

Create an account