> ## Documentation Index
> Fetch the complete documentation index at: https://starcovery.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Report feedback

> Send a bug or feature request from the web or Quackback Cloud MCP.

Humans report from the Starcovery web. Agents report through Quackback Cloud MCP. Starcovery MCP, the CLI, and REST do not create feedback posts.

## On the web

On Search, Campaigns, and Settings, open **Report Feedback**. That control goes to the Quackback Cloud workspace at [starcovery.quackback.io](https://starcovery.quackback.io). Starcovery does not embed the Quackback widget.

## Agents

Connect to the Quackback Cloud MCP server. Do not add a Starcovery MCP tool or CLI command for this.

```text theme={null}
https://starcovery.quackback.io/mcp
```

Create a `qb_` key in Quackback **Admin → Settings → Developers**. Then:

```bash theme={null}
claude mcp add --transport http quackback https://starcovery.quackback.io/mcp \
  --header "Authorization: Bearer $QUACKBACK_API_KEY"
```

Look up a board with the `quackback://boards` resource, then call `create_post`.

```text theme={null}
create_post({ boardId: "board_...", title: "Search results stay blank after submit" })
```

Full tool list: [Quackback MCP reference](https://quackback.io/docs/mcp/reference).

## GitHub issues

The Quackback GitHub integration creates one issue per report and syncs status on close. That lives in the Quackback admin, not in Starcovery.