Productboard MCP Server
Related Servers
Alternatives to Productboard MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceEnables interaction with the Productboard REST API, providing tools to manage features, notes, companies, objectives, initiatives, key results, releases, webhooks, users, products, and components.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with your Productboard workspace, allowing features, products, notes, objectives, key results, and releases management.20MIT
- FlicenseBqualityDmaintenanceEnables AI assistants to interact with a Productive.io workspace for managing projects, tasks, time entries, budgets, and invoices through natural language.33-
- AlicenseBqualityDmaintenanceEnables interaction with Featurebase API to manage feature requests, feedback posts, comments, and upvotes. Supports creating, updating, and organizing customer feedback through natural language commands.12505 npm8MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to interact with ProjectHub for comprehensive project management through natural language. It provides 25 tools to manage tasks, workspaces, time tracking, notes, and discussions via the ProjectHub API.477 npmMIT
- AlicenseBqualityBmaintenanceMCP server for the Productboard API v2. Provides 30 tools covering entities, notes, relationships, configurations, members, and analytics.2934 npmMIT
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose targeting specific resources (companies, components, features, notes, products) with consistent get/list patterns. There is no ambiguity between tools as each operates on a different entity type with clear boundaries.
All tools follow a perfect verb_noun pattern with 'get_' prefix, consistently using snake_case throughout. The naming convention is completely predictable with 'get_<resource>s' for list operations and 'get_<resource>_detail' for detail operations.
11 tools is reasonable for a Productboard integration covering multiple entity types. The count feels slightly heavy since some operations could potentially be consolidated, but each tool serves a distinct purpose and the scope justifies the number.
The tool surface is severely incomplete for a product management platform. While read operations are well-covered for multiple entity types, there are no create, update, or delete operations, making this a read-only API that cannot support full product management workflows.