VoteShip
Manage feature requests, votes, roadmaps, and changelogs from any MCP client.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Manage feature requests, votes, roadmaps, and changelogs from any MCP client.
Server tool list (4)
Raw names from tools/list. Only developers need these.
| submit_feature_request | 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. |
| browse_board | 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. |
| upvote_post | 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. |
| add_public_comment | 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. |