Productboard MCP Server
MCP server for integrating with Productboard to manage customer feedback, fetch notes, search and create features, and link notes to features.
README
Productboard MCP Server
MCP server that lets Claude Code fetch notes, search features, create features, and link notes to features in Productboard. Includes a triage skill for processing customer feedback.
Setup
- Clone and build:
git clone git@github.com:djcorbett96/kojo-productboard-mcp.git
cd kojo-productboard-mcp
npm install
npm run build
-
Get a Productboard API token from your workspace admin settings under Integrations > Notes API.
-
Add to your Claude Code MCP config (
.mcp.jsonin your project root or~/.claude/mcp.jsonfor global):
{
"mcpServers": {
"productboard": {
"command": "node",
"args": ["/path/to/kojo-productboard-mcp/build/index.js"],
"env": {
"PRODUCTBOARD_API_TOKEN": "your-token-here",
"PRODUCTBOARD_TRIAGE_COMPONENT_ID": "",
"PRODUCTBOARD_DEFAULT_STATUS_ID": ""
}
}
}
}
| Env Variable | Required | Description |
|---|---|---|
PRODUCTBOARD_API_TOKEN |
Yes | Your Productboard API token |
PRODUCTBOARD_TRIAGE_COMPONENT_ID |
For feature creation | Component ID where new triage features are created. Find this in Productboard's feature board URL or via the API. |
PRODUCTBOARD_DEFAULT_STATUS_ID |
For feature creation | Status ID for new features (e.g., "New idea"). Use GET /feature-statuses with X-Version: 1 header to list available statuses. |
Claude Code launches the server automatically -- no need to run it manually.
Tools
fetch_notes
Fetches notes from Productboard with optional filtering.
| Parameter | Type | Description |
|---|---|---|
tags |
string[] | Filter to notes containing at least one of these tags |
keywords |
string | Full-text search on note titles and content |
createdFrom |
string | Notes created on/after this date -- "past month", "past week", "past 7 days", or "2024-01-15" |
state |
string | Filter by processing state: "processed" or "unprocessed" |
limit |
number | Max notes to return (default: 100, max: 1000) |
All parameters are optional. The server handles pagination automatically.
search_features
Searches existing features by keyword. Paginates through all features and performs client-side matching on names and descriptions.
| Parameter | Type | Description |
|---|---|---|
query |
string | Search term to match against feature names and descriptions (required) |
limit |
number | Max matching features to return (default: 25, max: 100) |
create_feature
Creates a new feature in Productboard. Requires PRODUCTBOARD_TRIAGE_COMPONENT_ID and PRODUCTBOARD_DEFAULT_STATUS_ID env vars.
| Parameter | Type | Description |
|---|---|---|
name |
string | Feature name (required) |
description |
string | Feature description (supports HTML) |
parentComponentId |
string | Override the default triage component |
statusId |
string | Override the default status |
link_note_to_feature
Links a customer feedback note to a feature for tracking and prioritization.
| Parameter | Type | Description |
|---|---|---|
noteId |
string | The note ID to link (required) |
featureId |
string | The feature ID to link to (required) |
Triage Skill
The repo includes a Claude Code skill for triaging unprocessed Productboard notes. It fetches notes, matches them to existing features, proposes new features when needed, and waits for your approval before taking action.
Skill Setup
Copy the skill into your project's Claude Code skills directory:
cp -r /path/to/kojo-productboard-mcp/.claude/skills/triage /your/project/.claude/skills/triage
Or symlink it:
ln -s /path/to/kojo-productboard-mcp/.claude/skills/triage /your/project/.claude/skills/triage
Usage
Run the skill in Claude Code with your product area tags:
/triage Warehouse, Procurement
/triage AP past month
/triage Platform, Integrations past 2 weeks
The skill will:
- Fetch unprocessed notes matching your tags
- Search for existing features that match each note
- Present a triage report with proposed actions (link to existing feature, create new feature, or flag for manual review)
- Wait for your approval before creating any features or linking any notes
The fetch_notes and search_features calls are pre-approved in the skill config. You'll only be prompted to approve create_feature and link_note_to_feature calls.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.