— Hosted MCP server · every plan
Your feature
request board,
over MCP.
featurevote is a feature request tool with a hosted MCP server. Ask your AI assistant for a feedback brief, follow the evidence, then have it make the changes you approve. Catch up on requests, review your Inbox and prepare the next changelog in one chat.
One URL and a sign in, with nothing to install. It works on your real board and is on every plan, including free.
Try a conversation Illustrative demo
Example: What do people want most?
- You ask: What do people want most that we have not planned yet?
- The agent calls list_boards: Acme Feedback
- The agent calls list_features: 38 requested, with votes and weighted votes
- The agent replies: Dark mode leads with 77 votes. Keyboard shortcuts and CSV export come next. None of the three is planned yet.
featurevote.app/api/mcp— Your feedback, in one conversation
Catch up. Check the evidence. Take action.
Start with a brief for your workspace. Decide what needs attention, then tell your assistant what to do. Available on every plan, including free.
- 01
Read your feedback brief
“What changed in our feedback over the last seven days? What needs a closer look?”
Requests, raw votes and comments compared with the previous seven days, plus current queues for approvals, quiet planned work and completed requests to review for a changelog.
- 02
Check the evidence
“Show me the linked requests and read the relevant Inbox conversations before suggesting changes.”
Follow links back to the requests and inspect the conversation timelines. An open Inbox count can include automated mail or resolved threads; it does not tell you who needs a reply.
- 03
Make the changes you approve
“Close the two resolved conversations you just showed me. Leave the others open.”
With a read and write connection, your assistant can carry out your instructions using the existing tools. It can also update request statuses, assign work, leave comments and prepare changelog drafts.
The brief itself changes nothing. Reading and investigation work on a read-only connection; changes need read and write access and your instruction or approval. Your workspace role still applies. Customer replies and changelog publishing stay in the featurevote dashboard. Activity counts include team activity; raw votes are not weighted demand.
— Good things to ask
It reads more
than the votes.
Votes, and the comments behind them. Who asked, what they wrote to your Inbox, how they answered your survey. Ask about any of it in plain words, and it answers from your real board.
- 01
Decide what to build next
“What do people want most that we have not planned yet? Read the comments on the top ones and tell me what they need.”
Ranked by weighted votes, so Patreon tiers and Discord roles count the way your board counts them. Then it reads the comments and tells you what people are trying to do.
- 02
Get ready for a customer call
“I have a call with Sara from Northwind. What has she asked for and voted on?”
Her requests, votes and comments in one answer. After the call, ask it to add her vote for CSV export, and she hears about it when it ships.
- 03
Check your calls against the board
“Here are my notes from this week’s customer calls. What did people ask for that is already on the board, and what is new?”
It reads your notes next to your requests and their comments, and tells you which requests the calls back up and what looks new. With a read and write connection, give it each caller’s name and email and it adds their votes.
- 04
Triage the Inbox
“Read the CSV export conversation and leave a private note for the product team.”
It reads the conversation, leaves a note only your team sees, and can mark it done. The customer is never emailed.
- 05
Read a survey
“Summarise the product survey. What stands out in the answers?”
The totals and every written answer, summed up. When you are done it can close the survey, and the results stay.
- 06
Close out a release
“Dark mode shipped in 2.4. Mark it done and draft the changelog.”
It marks the request done, gathers what else shipped since the last changelog, and writes the draft. You read it and press publish.
Start here
“What can you do
with my featurevote account?”
A good first question. It checks what this connection and your role allow, then suggests where to start.
— You choose when you connect
Read only, or read and write.
When you sign in, featurevote asks two things. Which accounts to connect, and whether your assistant may read only, or read and write.
- Read only
- Read your feedback brief, then explore requests, votes, comments, customers, Inbox conversations, surveys and changelogs. This connection cannot make changes.
- Read and write
- Follow the brief with actions you request or approve: update a status, assign a teammate, add a comment or vote, close a resolved Inbox conversation, run a survey or draft a changelog.
- Never
- It never publishes a changelog or emails your customers. Those stay a button you press. It sees only the account you picked, and it acts as you, within your own role.
— Set up
One URL and a sign in.
Nothing to install and no token to copy. Your assistant opens featurevote, you sign in, pick the account, and you are connected.
- Claude Code
- Run this in your terminal, then type /mcp in Claude Code and sign in. It adds featurevote for all your projects.
claude mcp add --transport http --scope user featurevote https://featurevote.app/api/mcp- Claude
- In Settings, then Connectors, add a custom connector with this URL and click Connect.
https://featurevote.app/api/mcp- Other MCP clients
- Add this URL as a remote server. Any client that connects over HTTP and signs in with OAuth works the same way.
https://featurevote.app/api/mcp
Disconnect any time in Settings, then Integrations. Access stops on the next request.