VoteShip
Server Details
Manage feature requests, votes, roadmaps, and changelogs from any MCP client.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- MattKilmer/voteship-agent-toolkit
- GitHub Stars
- 0
- Server Listing
- @voteship/mcp-server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool maps to a distinct public action: viewing the board, submitting a request, voting, and commenting. There is no meaningful overlap or ambiguity between the four operations.
All tool names follow a consistent verb_noun snake_case pattern: add_public_comment, browse_board, submit_feature_request, upvote_post. The naming is predictable and easy to scan.
Four tools is well-scoped for a public feedback board interaction surface. Each tool covers a needed user action without unnecessary bloat or duplication.
Core public workflows are covered: browse approved requests, submit a new request, vote, and comment. Minor gaps exist, such as no way to read existing comments or track the status of a pending submission, but these are not severe for the stated purpose.
Available Tools
4 toolsadd_public_commentComment on a public requestAInspect
Use this when the user wants to add public context or a follow-up to a known VoteShip feature request. Add a comment to a feature request on a public VoteShip board. No API key needed. Requires an author name.
Inputs: body (required), post_id (required), author_name (required). Returns: result
browse_boardBrowse a feature boardARead-onlyIdempotentInspect
Use this when the user wants to inspect, compare, or interact with approved requests on a public VoteShip board. View approved feature requests on a public VoteShip board. No API key needed. Returns posts sorted by vote count and renders an interactive board in MCP Apps clients.
Inputs: project_slug. Returns: posts, boardUrl, projectSlug
submit_feature_requestSubmit a feature requestAInspect
Use this when the user wants to send new product feedback to a public VoteShip board without administering the project. Submit a feature request to any public VoteShip board. No API key needed. The post is created as PENDING and requires board owner approval. Include metadata.source to identify your agent.
Inputs: title (required), email, source, description, +1 more. Returns: result
upvote_postToggle a feature-request voteADestructiveInspect
Use this when the user explicitly wants to add or remove their agent identity's vote on a known VoteShip post. Vote or unvote on a feature request (toggles). Uses a deterministic anonymous ID so the same agent on the same machine has a consistent identity. No API key needed.
Inputs: post_id (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Manage FeatureOS feedback boards, roadmaps, changelogs and help-center articles from any MCP client.
Read user feedback and draft your changelog from any MCP client.
Connect to a Sleekplan workspace for customer feedback, roadmap, changelog, and surveys. Feedback: search and filter posts, read threads with votes and voters, create and update, merge duplicates, check for similar requests, pull stats. Triage: apply tags and statuses, assign owners, reply in comments. Surveys: read NPS, CSAT, and multi-question responses and summaries. Changelog: draft and publish release notes for what you ship. Users: manage end users and segments! Find out more at https://sleekplan.com/mcp/
Manage Nitrozen.io changelog projects, entries and API tokens from any MCP client.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceOfficial MCP server for FeatureJet, enabling agents to read and act on customer feedback boards: list/search posts, file feature requests, and pull top-voted planned items.MIT- AlicenseAqualityCmaintenanceManage posts, channels, organizations, and ideas through any MCP-compatible LLM client.29 npmMIT

FeatureOS MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables Claude, Cursor, Gemini CLI, and other MCP clients to manage live FeatureOS workspaces in plain language, including triaging feature requests, merging duplicates, assigning owners, tagging posts, publishing changelogs, and updating help-center articles.Apache 2.0- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for Canny feedback management. Enables managing customer feedback, prioritizing features, and streamlining product development through natural language.337 npm11Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.