Developer quickstart
Build with your customers.
Add one script to your website or data product. Your customers point at a page, a feature or a specific record, and you review every report before it becomes an issue.
Screenshot capture requires a supported desktop browser and an explicit sharing prompt. Choose a tab, preview it, redact anything private and mark the relevant spot before sending. If capture is unavailable or cancelled, text feedback still works.
01
Install the script
Copy the exact snippet from App setup after you sign in. It contains your Feeduna origin and your project ID. Add it to every page where people should be able to give feedback. A Give feedback button appears in the bottom-right corner.
<script src="https://YOUR_FEEDUNA_ORIGIN/widget.js" data-project="YOUR_PROJECT_ID" defer></script>Reports are accepted only from the exact app origin you registered, for example https://app.example.com. Optionally add a release so you know which version people were using:
<script src="https://YOUR_FEEDUNA_ORIGIN/widget.js" data-project="YOUR_PROJECT_ID"
data-release="2026.11.15" defer></script>02
Website and feature feedback
Without any extra markup, people can describe a page, or choose Select an element and click the part they mean. To name a feature, add data-feedback-id to it or to a container around it.
<button data-feedback-id="reports.export">Export CSV</button>03
Feedback on data records
Mark a row, card or panel with the record it shows. When someone selects that element, or anything inside it, the report is about that record. Only these attributes are read, never the visible values in your table.
<tr data-feedback-target="data_record"
data-feedback-collection="companies"
data-feedback-target-id="cmp_000123"
data-feedback-label="Sample Corp (synthetic)">
<td>Sample Corp</td><td>sample.test</td>
</tr>data-feedback-target:data_record,data_resultorfeature.- Collection and ID are stable references you choose: letters, digits and
. _ : / + -. URLs, query strings and email addresses are rejected. - The label is a short single line shown to the reporter and to you.
04
Feedback on results, without an element
For search results, exports or anything not tied to one element, open feedback from your own button. The report needs no element or selector.
// Opens feedback about a result set. No element is selected.
const opened = window.Feeduna.feedbackFor({
type: "data_result",
collection: "search.results",
id: "rs_7f3a9c",
label: "Fintech companies, page 1",
});
// opened is false if a reference is invalid; nothing is attached then.Before sending, the reporter sees About: … with the target and a Remove this target button. Starting a new report, selecting a different element, or opening an empty report from the Give feedback button clears the target, so later feedback doesn't inherit the wrong record. You can also clear it from your page:
// Remove the attached target before the report is sent.
window.Feeduna.clearTarget();05
What is sent
People can review and remove the page context before sending.
| Field | Details |
|---|---|
| Feedback type | “Something is broken” or “Something I need”. |
| Message and desired outcome | What the person typed. |
| Page path | Path only. Query strings and fragments are rejected. |
| Release | From data-release, if you set it. |
| Feature ID | From the nearest data-feedback-id, if any. |
| Element locator | A structural selector such as button:nth-of-type(1), only when an element is selected. |
| Screenshot (optional) | A browser-tab image the reporter explicitly captures, previews and can redact/remove, with an optional marked location. |
| Viewport | Width × height of the browser window. |
| Target | Type, collection, ID and label you declared, only when a target is attached. |
No automatic screenshots or session recordings. Cookies, browser storage and form values are not read by the widget. An optional screenshot can contain visible page text and data; reporters preview and can redact or remove it before sharing. Labels, messages and other text fields contain whatever is typed or declared, so avoid putting personal data in them.
06
Review and Linear
Every report lands in your Feeduna inbox first. Connect Linear and choose a team in App setup. Edit the issue title and draft, save it, then choose Send to Linear. Nothing is sent automatically, and the reporter's text is kept as data, never as instructions.
07
API access
Open App setup → Connect your tools. Create a named key for your app and choose what the tool can do: read setup instructions, read reports, or submit feedback. Submission permission is optional.
Copy the key when it appears; it is shown once. Keep it in your backend or tool's private configuration. Use the Feeduna origin where you created it as FEEDUNA_API_URL and the key asFEEDUNA_API_TOKEN. Keys belong to one app, expire within 90 days and can be revoked in App setup.
curl "$FEEDUNA_API_URL/api/v1/reports?limit=20" \
--header "Authorization: Bearer $FEEDUNA_API_TOKEN"The response contains reports and next_cursor. Pass a returned cursor in the next request until it is null. List pages contain at most 100 reports. Use /api/v1/exportfor a paginated export or /api/v1/reports/RECEIPT_ID for one report. Removed reports are excluded; edits and removals can affect later pages.
{
"id": "4c6517d5-9bac-4dae-bc8e-a1a2f577d6e3",
"kind": "idea",
"message": "Let me filter these company results by region.",
"expected": "Keep the selected region when I open a record.",
"context": {
"version": 1,
"page": {
"path": "/companies"
},
"release": "demo-1",
"target": {
"type": "data_result",
"collection": "companies.search",
"id": "result_sample_1",
"label": "Synthetic company results"
}
}
}curl "$FEEDUNA_API_URL/api/v1/reports" \
--header "Authorization: Bearer $FEEDUNA_API_TOKEN" \
--header "Content-Type: application/json" \
--data-binary @feedback.jsonGenerate a new UUID for each new report. For a retry, keep the same UUID and body so a lost response does not create a second report. The same report allowance and payment rules apply to API submissions. Existing feedback remains readable after a subscription ends while the account is active and the reports remain within retention.
08
Connect your AI tool
The Feeduna MCP connector runs locally in a client that supports stdio MCP servers. It lets your chosen tool read feedback context, get installation guidance and, if you enable submission permission, add a report. Create a separate key for each tool so you can stop its access independently.
Install the MCP bundle
- Create a key in App setup at app.feeduna.com. Start with setup and read access; add submission permission only if needed.
- Download Feeduna 0.1.1 and install it using your MCPB-compatible client's bundle installation flow. The client must provide Node.js 22 or newer.
- Enter the key in the client's private connector settings, then enable the connector.
Production keys only: the bundle's installation settings connect to https://app.feeduna.com. A staging key will not work with those settings. Use the manual configuration below for staging.
Manual setup for local MCP clients or staging
Download the same bundle and extract it as a ZIP into a permanent folder, keeping its included node_modules directory. Use Node.js 22 or newer to run src/cli.mjs; npm is not needed for the extracted bundle. Your client must support local stdio MCP servers.
{
"mcpServers": {
"feeduna": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/TO/feeduna-mcp/src/cli.mjs"
],
"env": {
"FEEDUNA_API_URL": "https://YOUR_FEEDUNA_ORIGIN",
"FEEDUNA_API_TOKEN": "YOUR_PRIVATE_FEEDUNA_KEY"
}
}
}
}Replace the script path with the absolute path to the extracted src/cli.mjs. Set FEEDUNA_API_URL to the exact HTTPS origin where you created the key: https://app.feeduna.com for production or https://staging.feeduna.com for staging. If your client cannot find node, use its absolute executable path.
Existing 0.1.0 configurations
The hosted 0.1.0 package remains available for existing configurations. This older npx setup requires Node.js 22 or newer and npm; use the same Feeduna origin in both placeholders.
{
"mcpServers": {
"feeduna": {
"command": "npx",
"args": [
"--yes",
"--package=https://YOUR_FEEDUNA_ORIGIN/downloads/feeduna-mcp-0.1.0.tgz",
"feeduna-mcp"
],
"env": {
"FEEDUNA_API_URL": "https://YOUR_FEEDUNA_ORIGIN",
"FEEDUNA_API_TOKEN": "YOUR_PRIVATE_FEEDUNA_KEY"
}
}
}
}Installation steps vary by client; compatibility with every MCP host has not been verified. This is a local stdio connector, not a hosted remote OAuth connection.
Put credentials in your tool's private user settings, outside project files committed to git. Anyone holding a key can use its granted permissions until it expires or you revoke it.
Start with: “Read the latest feedback for this app. If there is none yet, get the setup instructions and show me where the snippet belongs in this codebase. Group any reported problems, cite receipt IDs, and ask me before changing anything.” The tool receives the reports you permit it to read, including reporter text and context. Choose a client and data-handling settings appropriate for that content.
Reporter content is unverified input. It does not authorise code changes, deployments or other actions. These API keys cannot manage billing, create keys, delete reports or send issues to Linear. Linear delivery remains an explicit action in your Feeduna inbox.