
The direct line from user to engineer.
Search your feedback board, clusters and survey answers from your AI, then turn them into GitHub, Linear or Jira issues.
https://usero.io/mcpNo API key? Call with the user's email (and clientName, the agent you are), show them the userCode it returns, ask them to press the button in their inbox and type the code on the page, then poll every 5 seconds without ending your turn; it returns the key once. Save it in the MCP client config, then (name, optional repo) and to finish setup. Connected via OAuth? You are already signed in, so skip signup and call . A new account has one empty client and no feedback: offer first, its public link needs no code to share.
Feedback: for the id, then for themes or for text, date or source; or for detail. Filing: files into the caller's product inbox, pins one to a second of a replay or user test recording, send_feedback_about_usero into the Usero team inbox. App reviews: to sync App Store or Play reviews, for progress. Intercom: for what is connected and when it last synced, sync_intercom to pull now. Fixes: opens a GitHub, Linear or Jira issue for a feedback item on the connected tracker; opens a pull request server-side on the connected repo, then poll . Forms: and to read, to build (returns the public link), before update_form, to remove; for the funnel, for a GitHub issue URL. Theming: once, for a one-hour preview URL, update_form to save. User tests: returns the share link; and to review, and for sessions (fullTranscript: true for the whole transcript), for what participants said about a phrase across every session (verbatim segments and filed insights, no generated answer), to pay (confirm with the user first). Referrals: referralBonusDollars on or update_user_test turns them on; add_referrer gives anyone a link into the client's open tests (list_referrers, set_referrer_disabled to manage); list_referrals shows the people they referred, review_referral decides flagged bonuses, release_referral_bonus marks one paid (confirm with the user first). AI runs: , then for findings. Board: for public board posts still waiting on a team reply, most voted first; set_board_post_target to set, move or clear the month a post is aimed at (voters see it as a chip); logs a request a user made in a ticket as a vote on a board post, shows who is behind a post's count; shows posts and comments held for review, approves or rejects one. Plan: get_usage for this month's usage against the plan's monthly amounts. Limits: the server cannot resolve, edit or delete feedback or change client settings. Quote users verbatim and never invent counts.
1 in the Claude listing