— The journal · · Updated

MCP Feature Voting: Ask Your AI Assistant What to Build Next

Connect Featurevote to your AI assistant. Ask what your users want most, catch up before a customer call, or draft the changelog when something ships.

Cover Image for MCP Feature Voting: Ask Your AI Assistant What to Build Next

A customer mentions CSV export on a call. Seventeen people already voted for it on your board. An Inbox conversation from last month explains why they need it, and your product survey put reporting at the top. That is one decision, spread over four screens.

Featurevote has a hosted MCP server, so your AI assistant can read all of it and work on your board for you. Ask what people want most. Ask what Sara from Northwind has voted on before your call with her. Tell it dark mode shipped and have it draft the changelog. It works on your real board, from Claude, Claude Code, Hermes Agent, or any other MCP client that connects over HTTP and signs in with OAuth.

One URL, and you choose what it may do

Add https://featurevote.app/api/mcp to your AI assistant and sign in. Featurevote asks two things. Which account the assistant may use, and whether it gets read only or read and write. There is nothing to install and no token to copy, and it is on every plan, including the free one.

In Claude Code it is one line:

claude mcp add --transport http --scope user featurevote https://featurevote.app/api/mcp

Then type /mcp and sign in. In Claude, add a custom connector with the same URL under Settings, then Connectors. The connection guide has the steps for each.

A good first question is "what can you do with my Featurevote account?". The assistant checks what this connection and your role allow, then suggests where to start.

Monday planning

What do people want most that we have not planned yet? Read the comments on the top five and tell me what they need.

You get the ranking and the reasons in one answer. The ranking uses weighted votes, so a board that counts Patreon tiers or Discord roles ranks the way the board does. The comments tell you what people are trying to do.

Ask if something is already on the board before you add it. Search matches words in titles and descriptions, and it can also ask Featurevote's AI for likely duplicates. It suggests, you decide.

Before a call

I have a call with Sara from Northwind. What has she asked for and voted on?

Her requests, votes and comments, in one place, before you dial in. After the call, tell it she asked for CSV export. It adds her vote with her email, and she hears about it when it ships. Nothing is emailed right away.

Inbox triage

Read the CSV export conversation and leave a private note to check it with the product team.

It reads the conversation, leaves the note, and can mark the conversation done or reopen it. The note stays inside your team. The customer is never emailed, and replying stays with you in Featurevote.

Survey review

Summarise the product survey. What stands out in the answers?

It reads the totals and every written answer, then tells you what stands out. With read and write it can also start a new survey, which goes live on your board right away, or close one. The results stay.

Release day

Dark mode shipped in 2.4. Mark it done and draft the changelog from what we finished since the last one.

It marks the request done, gathers everything completed since your last changelog, and writes the draft. You read it in Featurevote and press publish when you are happy with it.

What it never does

It never publishes a changelog or emails your customers. Publishing emails your subscribers, so it stays a button you press. The assistant writes the draft, you decide when it goes out.

It never sees your other teams. A connection is bound to the one account you picked.

It never acts as anyone but you. Comments it posts carry your name, and it can only do what your own role allows.

A read only connection never gets the write tools at all, so there is nothing for it to change. Disconnect any time in Settings, then Integrations, and access stops on the next request.

One habit worth keeping. Requests, comments and Inbox messages are your users' words, so treat what the assistant reads back as evidence, not instructions, and read a draft before you publish it.

Try it on your own board

  1. Add https://featurevote.app/api/mcp to your AI assistant.
  2. Sign in, pick the account, pick read only.
  3. Ask it what your users want most.

When you want it to make changes too, connect again with read and write. It is on every Featurevote plan, including the free one. See it in action on the MCP page.

Build what your users are actually asking for.

Featurevote is the feedback board behind these notes — free to start, no credit card.