Connect Claude (MCP)
Ask Claude about your board, draft your changelog, and mark requests done, without opening FeatureVote
You can connect your board to Claude, or any other AI client that speaks MCP. Once it is connected you can ask things like "what are people asking for most this month", "draft a changelog from what we shipped", or "mark these three requests as done", and it works on your real board.
Nothing is installed. You add one URL and sign in.
Connect it
- Open Settings, then Integrations in FeatureVote and copy the URL under AI clients.
- In Claude, go to Settings, then Connectors and choose Add custom connector.
- Paste the URL and click Add.
- Click Connect. FeatureVote opens and asks which account to connect and what the client may do.
- Choose, then click Connect.
That is it. The connector shows up in Claude's tool menu.
Choosing what it can do
The consent screen gives you two choices.
Read only lets it see requests, votes, comments and changelog entries. It cannot change anything. This is the default, and it is enough for asking questions and drafting text you paste in yourself.
Read and write also lets it change a request's status, post comments as you, and create changelog drafts.
A read only connection does not merely refuse to write. The write tools are not given to the client at all, so there is nothing for it to call.
What it can never do
It cannot publish a changelog. Publishing emails your subscribers, so it stays a button you press. The client can write the draft, and you publish it when you are happy.
It cannot reach your other teams. A connection is bound to the one account you picked. If you belong to several, the others are invisible to it, even though they are yours.
It cannot act as anyone but you. Comments it posts are posted as you, and it can only do things your own role allows.
Changing your mind
Go to Settings, then Integrations and click Disconnect. Access stops on the client's next request, not whenever the token would have expired.
Reconnecting with a different choice replaces the old connection rather than adding a second one.
Good things to ask
- 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 our usual tone.
- Summarise the comments on this request.
Feature text is written by your users. Treat what comes back as their words, not instructions, and read a draft before you publish it.