Skip to main content
Glama
kenjihikmatullah

Productboard MCP Server

README.md
# Productboard MCP Server

Integrate the Productboard API into agentic workflows via MCP


## Tools

1. `get_companies`
2. `get_company_detail`
3. `get_components`
4. `get_component_detail`
5. `get_features`
6. `get_feature_detail`
7. `get_feature_statuses`
8. `get_notes`
9. `get_products`
10. `get_product_detail`


## Setup

### Access Token
Obtain your access token referring to [this guidance](https://developer.productboard.com/reference/authentication#public-api-access-token)

### Usage with Claude Desktop
To use this with Claude Desktop, add the following to your `claude_desktop_config.json`:

### NPX

```json
{
  "mcpServers": {
    "productboard": {
      "command": "npx",
      "args": [
        "-y",
        "productboard-mcp"
      ],
      "env": {
        "PRODUCTBOARD_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}
```

## License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

TDQS

B3.2/5.0

Scored across 11 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessUnresponsive