Connect an AI assistant to featurevote (MCP)

featurevote’s hosted MCP connection works on every plan, including Free. Use a client that supports MCP over HTTP and OAuth, with the URL https://featurevote.app/api/mcp.

Claude: Open Settings → Connectors → Add custom connector, name it featurevote, and enter the URL. Click Connect, choose your account and permissions, then confirm.

Claude Code: Run:

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

Use --scope user for all projects, or omit it for the current project only. Then enter /mcp, select featurevote, and sign in.

Read only is the default. It allows reading requests, votes, comments, changelogs, team and customer information, Inbox conversations, and surveys, subject to your role. Write tools are not provided to a read-only client.

Read and write also allows managing requests and assignments, commenting as you, adding customer votes, managing Inbox notes and conversation status, creating and closing surveys, managing changelog drafts, attaching images, and changing basic board settings.

The connection only accesses the account you select and what your own role allows. It cannot publish changelogs or email customers; publish changelogs and send customer replies in the dashboard. Start by asking what the connection can do with your account.

The feedback brief works on read-only and read/write connections, including Free workspaces. You need the workspace’s features.manage permission.

Ask for a brief of what changed in the last seven days, what needs attention, and the supporting evidence. The brief compares requests, raw votes, and comments with the previous seven days and links to current requests for review. Inspect requests and relevant Inbox timelines before approving changes: an open conversation count can include automated or resolved mail and is not a count of customers needing replies.

Requesting a brief never authorizes changes. Give a specific instruction or approve a batch of actions separately. Read-only connections can investigate and recommend; read/write connections can carry out approved actions.

If the brief is missing, refresh the client’s tool catalog or reconnect. No separate feature opt-in is needed.

The brief’s seven-day counts include team activity, creator auto-votes, private or pending requests, and internal comments. Raw votes do not measure weighted demand, unique contributors, or net growth. Attention queues show current state, not just the last week’s activity. Brief links require sign-in; the brief excludes Inbox message bodies and contact fields.

Request rankings use weighted votes, matching the board’s order when Patreon or Discord weighting is enabled. Request search matches words in titles and descriptions, not equivalent meanings. AI duplicate suggestions are available, but the MCP assistant does not merge requests.

Account owners can look up a customer’s requests, votes, and comments. Adding votes requires read/write access and each person’s name and email. Adding a customer vote also adds the customer to the changelog list, but preserves an existing unsubscribe choice and sends no immediate email.

The assistant can read Inbox conversations, add private team notes, mark conversations done, and reopen them. Private notes do not email the customer. Send customer replies from featurevote.

The assistant can read survey totals and individual answers. With write access it can create rating and choice surveys or close surveys while keeping results. A survey created through MCP goes live immediately. Edit and delete surveys in featurevote.

For releases, the assistant can mark requests done and draft a changelog from work completed since the last changelog. It can edit or delete drafts, but you review and publish in featurevote. Assignments remain internal; requests created by the assistant start assigned to you.

With write access, the assistant can edit, archive, restore, and make requests private. It can attach an image up to 3 MB to a request or your own comment. Attached image files are public even on private requests or internal notes. Do not attach confidential screenshots.

The assistant can change a board’s name, description, roadmap columns, and visitor posting rules. Integrations remain unchanged.

Requests created through MCP do not send the new-request email or Slack notification sent by admin screens.

Open Settings → Integrations → featurevote MCP and click Disconnect beside the connection. Access stops on the client’s next request.

Reconnecting creates a new connection; it does not replace an old one. To change permissions, connect again with the new access choice, then disconnect the old connection. Settings shows when each connection was added, who connected it, and when it was last used.

Connections unused for 90 days stop working and leave the list. Connect again to restore access.