Add feedback to your SaaS with Cursor

Cursor can absolutely help you build a feature-request board.

That is not the hard part.

The hard part is everything that starts after the first successful demo:

host-asserted identity (opaque stable user.id)
vote uniqueness and unvote
fixed statuses (open → declined, not “completed”)
BYO adapter vs Hosted storage
draft/publish board config
moderation and spam
Hosted webhooks without leaking title/body
live entitlements (BYO $9.99 / Hosted $19.99)
deployment reality

If you are using Cursor to ship a SaaS quickly, Bootstrapware Feedback is for the moment you realize:

"Yes, Cursor can build this. No, I do not want to maintain this subsystem forever."

The right use of Cursor here

Use Cursor for what it is excellent at:

integrating a package
wiring UI into your app
connecting a BYO adapter to your API
adapting styling
generating surrounding glue code
creating/publishing board config via MCP (no post payloads)

Do not use your precious hours re-deriving an in-app feedback product from scratch unless feedback is genuinely core to what you sell.

Recommended MCP setup

Open Feedback → Keys and use Add to Cursor (OAuth).
Sign in at app.bootstrapware.co and allow workspace access.
Point Cursor at AGENTS.md rules and ask it to embed @bootstrapware/feedback.

OAuth URL-only mcp.json:

{
  "mcpServers": {
    "bootstrapware-feedback": {
      "type": "http",
      "url": "https://feedback.bootstrapware.co/mcp"
    }
  }
}

MCP tools configure boards only (list_boards, create_board, update_draft, publish_board, …). Never put post title/body into MCP. Key mint/revoke, webhooks, Hosted inbox, and billing stay dashboard-only.

A practical Cursor prompt

Install and integrate Bootstrapware Feedback into this Next.js app.

Requirements:
- Add a feedback page at /dashboard/feedback
- Render the Feedback component
- Import @bootstrapware/feedback/styles.css
- Pass user from our session (opaque id + name)
- Use boardId + publishable key from env (Hosted) OR a FeedbackAdapter to our API (BYO)
- Do not expose secret keys in the browser
- Embed-only, no public board URL
- Never send post title/body through MCP
- Statuses: open | planned | in_progress | shipped | declined
- Keep the implementation modular
- Add loading and error states around submit/vote

That is a much better use of a coding agent than "Build me a full Canny clone," because it narrows the agent's job to integration rather than reinvention.

For a reusable blank, see Agent prompt template or Give this to your coding agent.

Why this fits the Cursor workflow

Cursor users are often shipping on a short loop: idea → prompt → feature → ship.

That creates an obvious temptation to let the agent build everything.

Bootstrapware fits when you want to keep the velocity without adopting ownership of every annoying subsystem the agent can theoretically produce.

Use Cursor to wire the thing in.

Do not use Cursor to volunteer yourself as the lifetime maintainer of in-app feedback unless you mean to.