Send User Feedback to Your Coding Agent via MCP

Your users already tell you what’s broken. The hard part is getting that information to the place where the fix happens. Today that place is often a coding agent. This guide connects the two.

1. Create an API key

In the dashboard, open Settings → API keys and create a key with the issues:read and issues:write scopes. Keys start with fb_live_. API access is available on Pro and Business.

2. Connect your coding agent via MCP

Most coding agents support MCP. For example, in Claude Code:

claude mcp add --transport http feedbot https://mcp.feedbotai.com/mcp \
  --header "Authorization: Bearer $FEEDBOT_API_KEY"

Or in Codex:

[mcp_servers.feedbot]
url = "https://mcp.feedbotai.com/mcp"
bearer_token_env_var = "FEEDBOT_API_KEY"

Your agent now sees tools like list_product_issues, get_issue and mark_issue_fixed.

3. Ask for the fix

Try a prompt like:

Look at the top 3 open Feedbot issues for this project, reproduce the first one and propose a fix.

Each issue comes with user quotes, the number of reports, affected pages and suggested acceptance criteria. That’s usually enough context for the agent to find the right code.

No MCP? Use the CLI

npx feedbot pull

This writes open issues to .feedbot/issues/<id>.md. Any agent that can read files can work with them. When you’re done:

npx feedbot resolve 42 "Fixed CSV export in Safari"

Close the loop

Marking an issue as fixed does two things. The bot stops working around the problem in its answers, and, if you enable it, it tells the users who reported the issue that it’s been fixed.

See the agent docs for all tools and endpoints.