Productboard MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRODUCTBOARD_ACCESS_TOKEN | Yes | Your Productboard API access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_productsB | Returns detail of all products. This API is paginated and the page limit is always 100 |
| get_product_detailC | Returns detailed information about a specific product |
| get_featuresA | Returns a list of all features. This API is paginated and the page limit is always 100 |
| get_feature_detailC | Returns detailed information about a specific feature |
| get_componentsA | Returns a list of all components. This API is paginated and the page limit is always 100 |
| get_component_detailC | Returns detailed information about a specific component |
| get_feature_statusesA | Returns a list of all feature statuses. This API is paginated and the page limit is always 100 |
| get_notesC | Returns a list of all notes |
| get_note_detailC | Returns detailed information about a specific note |
| get_companiesB | Returns a list of all companies. This API is paginated and the page limit is always 100 |
| get_company_detailC | Returns detailed information about a specific company |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.