Add one URL to your AI client and ask what your users want most, or have it draft your changelog. Here is how the MCP connector works.
Writing a changelog is not hard work, it is copying. You open the board, scroll for what was marked done since the last entry, remember which of those anyone actually asked for, and turn the list into a paragraph. Twenty minutes of moving text between two tabs, every few weeks, which is exactly why it slips.
Featurevote boards now speak MCP, the open standard AI clients use to reach real systems. Connect your board and that job becomes a sentence: "draft the next changelog from what we finished since the last one." The client reads the board, finds the completed requests, and writes the draft. You read it and publish.
MCP is a standard rather than one company's feature, so this is not a Claude integration that happens to use an open protocol. It is one endpoint and one consent screen, and any client that speaks MCP can use them. Claude is where we tested it, and the walkthrough below uses it, but nothing in the connection is specific to it.
Nothing to install
You add a URL, not a package. In Featurevote, open Settings → Integrations and copy the URL under AI clients. Then hand that URL to your client — in Claude, that is Settings → Connectors, then Add custom connector.
Featurevote then asks you two things on a consent screen we run ourselves: which account the client may reach, and whether it gets read only or read and write. Choose, confirm, and the connector shows up in the client's tool menu.
That is the whole setup. There is no API key to store and no token to paste into a config file, and if your account uses two-factor authentication you will be asked for a code before the connection is made.
What you can ask it
The useful questions are the ones that were tedious to answer by hand:
- What has the most demand that we have not planned yet?
- Which requests were marked done since the last changelog?
- Draft the next changelog from those, in the tone we usually use.
- Is anyone already asking for offline mode, or would this be the first?
- Summarise what people said in the comments on this request.
Votes come through weighted, so a board using Patreon tiers or Discord roles answers "most wanted" the way the board itself ranks it, not by a flat headcount.
Read only is not a promise, it is an absence
A read only connection can see requests, votes, comments and changelog entries. It cannot change anything, and the reason it cannot is worth stating plainly: the write tools are never handed to the client. There is nothing there to call and nothing to refuse. Read only is the default, and for asking questions and drafting text you paste in yourself, it is all you need.
Read and write adds four things: change a request's status, post a comment as you, create a changelog draft, and add a new request to a board.
What it will never do
It cannot publish a changelog. Publishing emails your subscribers, so it stays a button a human presses. The client writes the draft, you decide when it goes out.
It cannot reach your other teams. A connection is bound to the single account you picked on the consent screen. Other accounts you belong to are invisible to it.
It cannot act as anyone but you. Comments it posts are posted under your name, and it can only do what your own role on that account allows.
Disconnecting is one click in Settings → Integrations, and access stops on the client's next request rather than whenever a token would have expired.
The parts that are still rough
Search matches words in a request's title and description. It does not understand synonyms, so a search for "dark mode" will not surface a request that only ever says "night theme". Try the words your users would have used.
A request created through the connector does not send the new-request email or Slack notification that the admin screens send. Same request, same board, quieter arrival. Worth knowing if you rely on that notification to spot new items.
The connection needs a client that speaks the current MCP transport over HTTP and can sign in with OAuth, which most current ones do. Claude is the one we have run against production end to end. If yours cannot connect, tell us which client it is and we will look at it.
And one habit worth keeping: feature requests and comments are written by your users. When the client reads them back to you, treat that text as what your users said, not as instructions to anyone, and read a draft before you publish it.
Try it on your own board
- In Featurevote, open Settings → Integrations and copy the URL under AI clients.
- Add it to your client as a custom connector.
- Click Connect, pick the account, pick read only, confirm.
- Ask it what your users want most.
The connector is part of every Featurevote plan, including the free one. The full details live in the MCP docs.