Plan drift and cost impact, cluster triage, scaling, reliability and cloud-bill allocation on data you supply.
Early AccessEvery agent is free to connect — no card, no checkout.
We use essential cookies to keep you signed in. With your consent we also use non-essential cookies for analytics. Read our privacy policy
Browse › Software Development › Mobile Code Reviewer
Reviews a mobile change with severities that still mean something.
A preview derived from this agent’s definition — not a live run. Nothing runs and no key is sent until you connect. FindAgent runs it on the hosted connection.
Audit a whole changeset for correctness, duplication, loose typing, dead code and missing states, with each finding naming a concrete fix.
Compare a change against what was actually asked for, separating the work requested from the refactors, renames and cleanups that arrived alongside it.
Examine every failure path in a change — swallowed errors, collapsed conditions, missing surfacing to the user, and fallbacks that read as real answers.
Review the concerns unique to a mobile change — released-client compatibility, permissions, lifecycle, storage migration, battery and network assumptions.
Grade review findings honestly — separating what blocks from what is preference — so severity keeps meaning something and the important findings still get read.
Assemble the review into a report with a clear verdict, findings ordered by severity, and an explicit statement of what was not reviewed.
This MCP server runs on your own machine — FindAgent only points you at it. Run the command below, then add it to your MCP client. Nothing is hosted or proxied on our side.
npx -y @findagent/mcp runPaste this into your client config (e.g. claude_desktop_config.json or a Cursor mcp.json), then restart the client.
{
"mcpServers": {
"mobile-code-reviewer": {
"command": "npx",
"args": [
"-y",
"@findagent/mcp",
"run"
]
}
}
}Plan drift and cost impact, cluster triage, scaling, reliability and cloud-bill allocation on data you supply.
Keeps asking until a request is genuinely buildable, then writes the use case, criteria and ticket drafts.
Maps your module graph, scores blast radius, plans migrations and composes a validated unified diff.
Stops an infrastructure or dependency change that opens a hole.
Flags the days your GA4 metrics deviate from their baseline — with the numbers computed, not guessed.
Decides whether a change can merge: diff review, test evidence, breaking-change and tech-debt scoring.
Decides what your ad data can actually support, and refuses the rest