featurevote

app.featurevotePublished by featurevote.appOfficial publisherv0.1.0Updated Oct 24, 2026

Read requests and votes; with write access, manage feedback and draft changelogs. OAuth required.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Lets an assistant read feature requests and votes, and with write access manage feedback and draft changelogs.

What you can do
This remote MCP server connects an assistant to a feature-voting and feedback service. It exposes tools for reading feature requests and their votes, and, when write access is granted, for managing feedback items and drafting changelogs. The registry description lists no individual tool names, so the exact set of operations is not specified.
When to use it
Worth adding when you want an assistant to review incoming product feedback, summarize feature requests and vote counts, or help prepare changelog drafts from within the same workflow. It is aimed at product and support teams that already collect feedback in this service.
Requirements
A remote endpoint at over streamable HTTP. OAuth is required to authenticate. No packages, environment variables, or headers are declared.
Before you install
OAuth grants the assistant access to your account data; write access allows it to manage feedback and draft changelogs, which may change or create content. Grant read-only access unless write operations are intended, and review what the server sends to the third-party service.

Installation

In SourceWeft

  1. Open featurevote in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.featurevote%2Ffeaturevote/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "featurevote": {
      "type": "http",
      "url": "https://featurevote.app/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 15, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.