> For the complete documentation index, see [llms.txt](https://docs.flowcp.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowcp.ai/reference/feedback.md).

# User feedback

Every hosted MCP server includes a built-in `send_feedback` tool that lets MCP clients (and the AI agents driving them) send feedback about your server — a bug report, a missing capability, a confusing tool description, or praise. Submissions land on your app's **Feedback** page, where you review them and track what you've acted on.

## The `send_feedback` tool

The tool is registered automatically on every server session, in both production (`/mcp/:serverId`) and development (`/mcp/dev/:devSlug`) endpoints. It never calls your API — a submission is stored directly by FlowCP, scoped to your workspace and server.

| Input      | Type   | Required | Description                                                       |
| ---------- | ------ | -------- | ----------------------------------------------------------------- |
| `message`  | string | yes      | The feedback itself, up to 4,000 characters                       |
| `category` | enum   | no       | `bug`, `missing_capability`, `docs`, `praise`, or `other`         |
| `rating`   | number | no       | Overall experience with the server, `1` (poor) to `5` (excellent) |
| `toolName` | string | no       | The specific tool the feedback is about                           |

If one of your own enabled tools is already named `send_feedback`, FlowCP skips the built-in so your tool is never shadowed.

### Rate limits

Submissions are limited to **10 per hour per end user per server** (servers using a shared-credential auth mode share one bucket per server). Calls over the limit return an error to the client without storing anything.

## The Feedback page

The app's **Feedback** tab (under **Support** in the sidebar) aggregates submissions across **all of the app's servers**, including development endpoints — entries from a dev endpoint carry a **Dev** badge.

Each entry shows the message, category, rating, the tool it refers to, the MCP client name and version, the model (when reported), the submission time, and a truncated user hash — the same privacy-safe connection key the [execution logs](/reference/execution-logs.md) use.

### Review workflow

Every entry has a status:

| Status       | Meaning                                           |
| ------------ | ------------------------------------------------- |
| **New**      | Not yet looked at (the default)                   |
| **Reviewed** | Seen by a maintainer, action still pending        |
| **Resolved** | Addressed — fixed, shipped, or consciously closed |

Use **Mark reviewed** / **Mark resolved** on an entry to move it through the workflow, or delete it permanently with the trash button. The status tabs at the top show live counts so you can see your backlog at a glance.

### Filtering

| Filter         | Options                                                 |
| -------------- | ------------------------------------------------------- |
| **Status**     | All (default), New, Reviewed, Resolved                  |
| **Time range** | All time (default), Last 24h, Last 7 days, Last 30 days |
| **Category**   | Bug, Missing capability, Docs, Praise, Other            |

## Privacy

Feedback messages are free-text written by the client, but FlowCP never stores tokens, request bodies, or any end-user PII beyond the truncated user hash. Feedback is scoped to your workspace — you only see feedback for your own apps and servers.