Connect FeatQ to v0
v0 is an AI app builder from the Next.js team, not an MCP client, so it does not connect to the FeatQ server directly. (MCP, the Model Context Protocol, is the standard coding agents like Claude Code use to call FeatQ tools.) With v0 the loop is: install the feedback widget with one prompt, collect votes, then paste the top spec from your board into v0 to build it. If you export the project and work locally with a coding agent, you also get the native MCP route.
Setup: one prompt
Paste this prompt into v0. Replace YOUR_BOARD_SLUG with the slug from your board URL.
Add this script tag just before the closing body tag of my app: <script src="https://featq.com/widget.js" data-board="YOUR_BOARD_SLUG" async></script>v0 adds the script and your app gets a floating feedback button connected to your board.
To ship what users vote for: copy the top-ranked spec from your board (Generate spec on any request, or this API call) and paste it into v0’s chat.
curl -H "Authorization: Bearer fq_YOUR_KEY" https://featq.com/api/v1/top-specWhat it looks like in practice
Shipping a voted-for feature in v0 looks like this:
You: [paste the FeatQ spec for "Comment reactions", your top request with 31 votes] Build this. v0: The spec describes emoji reactions on comments, one reaction per user per comment, and the accessibility notes from the thread. Updating the comment component... v0: Done. Reactions render under each comment with keyboard support. You: [back on FeatQ, mark "Comment reactions" as done. FeatQ updates your changelog and emails the 31 voters.]
One quirk to know
In a v0 Next.js project, ask for the widget script in the root layout (via next/script or at the end of the body) rather than inside a single component, so the feedback button shows on every page.
Frequently asked questions
Practical answers about agents, voting, embeds, and pricing.
Not inside v0 itself. But v0 projects export to Next.js, and once you work on the code locally with Claude Code or Cursor, you can connect that agent to your board over MCP with the same key.
Yes. It is a plain script tag with no framework dependencies. Put it in the root layout so it loads on every route.
By votes plus half-weight comments, with the score fading as requests age. The top-spec API call always returns a spec for the current leader.
Users vote in the widget, you paste the top spec into v0, v0 builds it, you mark the request done, and FeatQ updates your changelog and emails the voters.
Still have questions? Contact us