The AI-powered feedback platform that closes the loop. Collect votes, triage with AI, prioritize by revenue, and ship release notes in one click — so your team builds instead of organizing feedback.
Vote on what we should build next
Dark mode support
Add a dark color scheme option that respects system preferences
API v2 with webhooks
Real-time event notifications for post creation, votes, and status changes
SSO / SAML login
Enterprise single sign-on for team accounts with SAML 2.0
Slack integration
Get notified in Slack when new feature requests are submitted
Export to CSV
Download all feature requests and vote data as a CSV file
From collecting raw feedback to shipping polished features, VoteShip covers the entire loop.
Collect feedback on a public board or embed anywhere with the widget. Popup, inline board, roadmap, and changelog — four widget types, one script tag.
Automatic duplicate detection, smart categorization, and trend analysis. AI handles the busywork so your team focuses on building.
Share what you're building with a public roadmap. Customers see progress in real time and feel heard.
Select completed features, AI writes the release notes, and you publish to your changelog — all in one click. Posts auto-archive off the board.
Sync Stripe MRR to know what your highest-paying customers want. AI plans sprints by revenue, popularity, or quick wins.
REST API, 12 webhook events, MCP server with 34 tools, plus Slack, GitHub, Linear, and Discord integrations. Import from CSV, Nolt, or UserVoice.
VoteShip brings feature requests, roadmaps, and changelogs into your AI coding workflow through its MCP server.
Create posts, triage feedback, search duplicates, plan sprints, ship releases — all from your AI coding environment.
POST raw text from any source. VoteShip extracts the request, finds duplicates, assigns tags, and detects sentiment.
Built-in prompts for inbox triage, sprint planning, changelog generation, and feedback summaries.
Paste into Claude Code, Cursor, or any AI coding assistant. Your agent handles the rest.
Add VoteShip to this project as a feedback widget where users can submit and vote on feature requests. Guide: https://app.voteship.app/install.md
Works with Claude Code, Cursor, Windsurf, Copilot, and any AI coding assistant
Add to your MCP config. Your agent gets 34 tools, 7 resources, and 5 workflow prompts.
# Claude Code — no API key needed
claude mcp add --transport http --scope user voteship https://voteship.app/mcp
# Codex — no API key needed
codex mcp add voteship --url https://voteship.app/mcpPublic tools work without a key. Use the local npm package for authenticated project administration.
Use VoteShip when a product team or software agent needs to turn customer feedback into structured requests, find duplicates, prioritize a roadmap by votes or revenue, and close the loop with release notes. Choose the public API for customer-facing actions, the authenticated REST API for project administration, or MCP for tool-native agent workflows.
Use the REST API reference for authenticated project administration: create and update posts, manage votes and comments, organize tags, read analytics, plan roadmaps, publish releases, and configure integrations. It includes Bearer authentication, rate limits, examples, and structured error responses.
Fetch the machine-readable OpenAPI document when generating a typed client, validating requests, building an agent tool, or discovering supported paths and schemas. The production API base URL, authentication scheme, request bodies, response envelopes, and error models are defined in one JSON file.
Connect @voteship/mcp-server when an AI assistant needs native tools for feedback intake, board search, voting, triage, sprint planning, roadmaps, analytics, or changelog releases. Public mode works without a secret; project administration uses a VoteShip API key.
Read the authentication and webhook guides before building a production integration. Agents should keep secret keys server-side, send them as Bearer tokens, verify webhook HMAC signatures against the raw request body, handle retries safely, and respect rate-limit headers.
Each interface exposes the same feedback workflow at a different trust boundary. Select the narrowest option that can complete the task, keep project secrets out of browsers and transcripts, and let VoteShip return identifiers and statuses that the agent can report or use in a later step.
Use the public API or public MCP tools to submit a suggestion, browse approved requests, add a vote, or join a discussion on a known board. No secret key is required. New suggestions remain pending until the board owner reviews them, and agents should search first so existing demand is not split across duplicate posts.
Use the authenticated REST API for backend integrations that manage posts, tags, users, roadmaps, releases, analytics, and webhooks. Send the project secret as a Bearer token from a trusted server, follow the OpenAPI schema, handle structured error codes, and wait for Retry-After before repeating a rate-limited request.
Use the MCP server when an assistant should discover typed VoteShip tools, read board resources, or invoke repeatable prompts for triage, summaries, sprint planning, and changelog generation. Public mode is appropriate for customer actions; an API key unlocks project-specific administration and should only be supplied through the MCP host environment.
Start at the VoteShip Developer Hub, read when agents should use VoteShip, or fetch llms.txt for a concise machine-readable index.
Start free. Upgrade when you're ready. No surprises.
For indie hackers getting started
Everything a product team needs
For companies that need SSO & control
For large-scale feedback operations
Start collecting feedback, prioritizing features, and shipping faster, completely free.