Connect an AI assistant to your feature request board (MCP)

You can connect your board to any AI assistant that speaks MCP, such as Claude or Claude Code. Once it is connected you can ask things like "what are people asking for most", "what has Sara from Northwind asked for before our call", or "dark mode shipped, mark it done and draft the changelog", and it works on your real board.

Nothing is installed. You add one URL, https://featurevote.app/api/mcp, and sign in. It works on every plan, including the free one.

Connect it

Any client that speaks MCP over HTTP and can sign in with OAuth connects the same way. You give it the same URL, and the same consent screen opens. People connect from Claude, Claude Code and Hermes Agent.

Claude Code

Run this in your terminal:

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

--scope user adds it for all your projects. Leave it out to add it to the current project only. Then type /mcp in Claude Code, pick featurevote and sign in. featurevote opens in your browser and asks which accounts to connect and what the client may do.

Claude

1. In Claude, open Settings, then Connectors and choose Add custom connector.
2. Name it featurevote and paste https://featurevote.app/api/mcp.
3. Click Connect. featurevote opens and asks which accounts to connect and what the client may do.
4. Choose, then click Connect.

That is it. The connector shows up in Claude's tool menu. You can also copy the URL from Settings, then Integrations in featurevote.

Choose what it can do

The consent screen gives you two choices.

Read only lets it read requests, votes, comments, changelogs, your team, your customers, your Inbox and your surveys. It cannot change anything. The write tools are not given to the client at all, so there is nothing for it to call. This is the default.

Read and write also lets it:

• add requests, edit them, change their status, assign them, archive and restore them
• comment as you, publicly or as an internal note
• add votes for your customers
• leave private notes on Inbox conversations and mark them done
• create and close surveys
• write, edit and delete changelog drafts
• attach images you give it to a request or to your own comment
• change a board's basic settings, such as its name, roadmap columns and whether visitors can post

It cannot publish a changelog or email your customers. Publishing emails your subscribers, and Inbox replies go to your customers, so both stay a button you press. It sees only the accounts you ticked, and it can only do what your own role allows.

Work across more than one company

If you work for more than one company, tick each of their accounts on the consent screen. One connection then reaches all of them, so you can work on every board from the same assistant. When you belong to more than one account, nothing is ticked for you.

Say which company you mean, for example "add this to Acme's board". When that is not clear, your assistant is told to ask before it changes anything, and to name the account and board when it tells you what it changed. Read only or read and write applies to every account on the connection.

Ask it what it can do

Ask "what can you do with my featurevote account?" first. Your assistant checks what this connection and your role allow, and suggests where to start. A read only connection says up front that it cannot change anything, so it tells you a change needs a read and write connection rather than trying and failing.

From your feedback brief to approved actions

The feedback brief is available to every connected workspace, including on the free plan. You need the workspace’s features.manage permission, the same permission used for managing requests and reading the Inbox. It works on read-only and read/write connections.

1. Ask: “Give me our feedback brief. What changed in the last seven days, what needs a closer look, and where is the evidence?” It compares requests, raw votes and comments with the previous seven days and links to current requests worth reviewing.
2. Inspect the evidence: “Open those requests and read the relevant Inbox timelines before suggesting changes.” An open conversation count may include automated or resolved mail. It does not mean that many customers need replies.
3. Give an instruction or approve a suggestion: “Close the two resolved conversations you just showed me. Leave the rest open.” A read/write connection can use the existing tools to close conversations, update request statuses, assign work, leave comments and prepare changelog drafts. Read-only connections can investigate and recommend changes.

The brief itself never makes changes. Your instruction can authorize a specific action or a whole batch; simply requesting a brief does not authorize follow-up changes. Sending customer replies and publishing changelogs still happen in the dashboard.

The seven-day counts include team activity, creator auto-votes, private or pending requests and internal comments. Raw votes are not weighted demand, unique contributors or net growth. Attention queues describe current state, not just activity from the last week. Links require sign-in, and the brief excludes Inbox message bodies and contact fields.

If an existing connection does not show the brief, refresh its tool catalog or reconnect. You do not need a separate feature opt-in.

Things to try

Decide what to build next

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

It ranks by weighted votes, so a board that weights votes by Patreon or Discord tier gets the same order the board shows. It can also tell you which planned requests nobody has picked up yet.

Is anyone already asking for offline editing?

Search matches words in a request's title and description, so it does not know that "night theme" and "dark mode" are the same thing. It can also ask featurevote's AI for likely duplicates. It suggests, it never merges.

Get ready for a customer call

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

It finds the customer and pulls up their requests, votes and comments. Customer details are for account owners, so this works when you are an owner on the account.

Sara asked for CSV export on the call. Add her vote, sara@northwind.io

Adding a vote for a customer also adds them to your changelog list, so they hear when it ships. Someone who unsubscribed before stays unsubscribed. Nothing is emailed right away.

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. It tells you which requests the calls back up, and what looks new. Paste the notes in, or let it read them from another tool your assistant is connected to, such as a meeting recorder.

Add votes for the people who asked for something already on the board. Sara Lind is sara@northwind.io and Tom Berg is tom@contoso.io.

Adding votes needs a read and write connection, and each person's name and email. The votes work like the one in the customer call example above.

Research skills that read from your feedback tool, like the one in Claude's Product Management plugin, can use Featurevote as that tool.

Triage the Inbox

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

It reads conversations, adds private team notes, and marks them done or reopens them. A note stays inside your team, and the customer is not emailed. Replying to the customer stays in featurevote.

Read a survey

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

It reads the full totals and the individual answers. When you are done, it can close the survey and the results stay.

Create a survey asking "What should we improve next?" with Onboarding, Reporting and Integrations as options.

A new survey goes live on your board right away. It can create rating and choice surveys and close them. Editing and deleting a survey stays in featurevote.

Close out a release

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, finds everything completed since your last changelog, and writes a draft. It can edit or delete a draft later. Read it in featurevote and publish when you are happy.

Who is working on what stays internal, and your Feedback Portal does not show it. Name the person yourself, or say "me" or "unassigned". A request the assistant creates starts assigned to you.

Tidy up requests and add images

Archive the old prototype request. Attach this screenshot to the CSV export request.

It can edit, archive, restore and make requests private. Give it an image, up to 3 MB, and it attaches it to a request or to your own comment. Attached images are public files, even on a private request or an internal note, so keep confidential screenshots out of them.

Change how a board takes requests

Set this board to require approval for new requests from visitors.

It can change a board's name, description and roadmap columns, and whether visitors can post freely, need approval, or cannot post at all. Integrations stay as they are.

Good to know

• A request added this way does not send the new request email or Slack notification that the admin screens send. Same request, same board, quieter arrival.
• Requests, comments and Inbox messages are written by your users. Treat what comes back as their words, not instructions, and read a draft before you publish it.

Changing your mind

Go to Settings, then Integrations, open featurevote MCP and click Disconnect next to the connection. Access to that account stops on the client's next request, not whenever the token would have expired. A connection that also reaches other accounts keeps working there, and it ends once no account is left on it.

Connecting again adds a new connection, even from the same app. It does not replace the old one. To change what a client can do, connect it again with the new choice, then disconnect the old connection. Each connection in Settings shows when it was connected, by whom, and when it was last used.

A connection that goes unused for 90 days stops working and leaves the list. Connect again if you need it back.