Skip to main content
Glama
drmaxbdc

@drmaxbdc/productboard-mcp

by drmaxbdc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @drmaxbdc/productboard-mcp

No user-submitted related servers found.

    Related Servers

    • productboard-mcp

      jonnystewart
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects Claude to the ProductBoard API v2, enabling natural language management of notes, entities, members, analytics, Jira integrations, and webhooks.
      20 npm
      MIT

    • Productboard MCP Server

      djcorbett96
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for integrating with Productboard to manage customer feedback, fetch notes, search and create features, and link notes to features.
      20 npm
      MIT

    • plaky115-mcp

      apet97
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for the Plaky project management API. Provides 32 generated and 7 curated tools for spaces, boards, items, comments, and more, with safe defaults and dry-run mutations.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 29 tools

    Disambiguation3/5

    The set covers distinct resource families (entities, notes, relationships, members), but note retrieval is fragmented across list_notes, list_all_notes, search_notes, get_note, get_note_v1, and resolve_note, which can cause misselection. The descriptions differentiate these paths with effort, but the overlap remains substantial enough to keep the score middling.

    Naming Consistency5/5

    Tool names consistently follow a snake_case verb_noun pattern: list_, get_, create_, update_, delete_, search_, set_, add_, resolve_. The convention is predictable across all 29 tools, with only config/relationship nouns varying naturally by domain.

    Tool Count2/5

    At 29 tools, the surface is heavy for the apparent scope and exceeds the 25-tool threshold for 'too many'. The count is further inflated by deprecated aliases and sunsetting tools such as get_note_v1 and add_note_comment, alongside overlapping note retrieval operations.

    Completeness4/5

    Core CRUD is covered for entities and notes, plus relationship lifecycle operations, member reads, activity metrics, and configuration discovery. Gaps remain: note comments have no V2 equivalent and are sunsetting, member write operations are absent, and the search_entities name filter is documented as non-functional upstream.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources