Skip to main content
Glama

Server Details

Manage feature requests, votes, roadmaps, and changelogs from any MCP client.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
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

A4.3/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

Four tools is well-scoped for a public feedback board interaction surface. Each tool covers a needed user action without unnecessary bloat or duplication.

Completeness4/5

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 tools
add_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 boardA
Read-onlyIdempotent
Inspect

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 voteA
Destructive
Inspect

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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Official 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.