FixThis
Capture Jetpack Compose UI issues locally and hand structured feedback plus source fix candidates to your agent without sending screens to a cloud review service.
Overview
FixThis is a MCP server for the Build phase that provides local-first Jetpack Compose UI feedback and source fix candidates to AI agents over stdio.
What is this MCP server?
- Local-first MCP handoff for Jetpack Compose UI feedback
- Surfaces source-level fix candidates alongside UI issue context
- npm package @beyondwin/fixthis with stdio transport (version 1.2.0)
- Keeps review loop on-machine for privacy-sensitive or offline Android work
- Purpose-built for Compose, not generic React or SwiftUI lint MCPs
- Server version 1.2.0
- npm identifier @beyondwin/fixthis with stdio transport
- Repository: github.com/beyondwin/FixThis
Community signal: 8 GitHub stars.
What problem does it solve?
Android solo devs struggle to give their agent precise Compose UI context without cloud screenshot pipelines or vague textual descriptions.
Who is it for?
Indie Android developers shipping Jetpack Compose apps who want a private MCP bridge between UI review and agent-driven patches.
Skip if: Web or iOS projects, teams that want hosted visual QA SaaS, or backend-only workflows with no Compose UI.
What do I get? / Deliverables
FixThis hands local UI feedback and candidate fixes into the agent thread so Compose changes stay fast, private, and reviewable in your repo.
- Structured local UI feedback packaged for agent consumption
- Source fix candidates aligned to reported Compose UI issues
- Private on-device review loop without mandatory cloud UI services
Recommended MCP Servers
Journey fit
Compose UI iteration is core Build work on Android clients, especially when polishing layouts and fixing visual regressions. Frontend subphase fits because the server targets UI feedback and candidate Kotlin/Compose source changes, not backend APIs or store launch.
How it compares
Compose-specific local UI handoff MCP, not a general Playwright or SSRS reporting server.
Common Questions / FAQ
Who is FixThis for?
Solo builders and small teams developing Jetpack Compose Android UIs who want local MCP-based feedback tied to source fix suggestions.
When should I use FixThis?
Use it during Build frontend work when Compose screens need iterative UI fixes and you want the agent to receive structured local handoff data.
How do I add FixThis to my agent?
Install @beyondwin/fixthis from npm, configure stdio MCP in your client, and follow github.com/beyondwin/FixThis for project-side Compose integration.