productboard-mcp

An MCP (Model Context Protocol) server for the Productboard API. Enables AI assistants (Claude, Cursor, etc.) to interact with your Productboard workspace.

Tools

Installation

Option 1: One-click install (.mcpb bundle) — Recommended

Download the latest `.mcpb` file from the Releases page and drag it into Claude Desktop (Developer → Extensions → Install), or double-click it in a compatible MCP client.

The bundle is self-contained — no cloning or building required.

After installing, set your `PRODUCTBOARD_API_TOKEN` in the extension settings.

Option 2: Local install (manual)

# 1. Clone the repo
git clone https://github.com/Enreign/productboard-mcp.git
cd productboard-mcp

# 2. Install dependencies and build
npm install --include=dev
npm run build

Then add to your `claude_desktop_config.json`:

{
  "mcpServers": {
    "productboard": {
      "command": "node",
      "args": ["/absolute/path/to/productboard-mcp/dist/index.js"],
      "env": {
        "PRODUCTBOARD_API_TOKEN": "your-api-token-here",
        "LOG_LEVEL": "error"
      }
    }
  }
}

> Important: Set `LOG_LEVEL` to `error` (not `info`). MCP uses stdio for communication — info-level logs printed to stdout will interfere with the protocol and cause the server to lock up.

Option 3: npx

> ⚠️ Coming soon — not yet published to npm. Use Option 1 or 2 above.

{
  "mcpServers": {
    "productboard": {
      "command": "npx",
      "args": ["-y", "@enreign/productboard-mcp"],
      "env": {
        "PRODUCTBOARD_API_TOKEN": "your-api-token-here",
        "LOG_LEVEL": "error"
      }
    }
  }
}

Getting a Productboard API Token

1. Log in to your Productboard workspace

2. Go to Profile & Settings → API Access

3. Click Generate API key and copy the token

Configuration

Required

Optional

> Note for MCP clients: Always set `LOG_LEVEL=error` when using with Claude Desktop, Cursor, or any stdio-based MCP client. Higher log levels write to stdout and will break the MCP protocol.

OAuth2 (optional)

Troubleshooting

"MCP server locks up / produces error logs"

→ Add `"LOG_LEVEL": "error"` to the `env` block in your MCP config. Info logs written to stdout interfere with the stdio transport.

"npx fails / package not found"

→ The package is not yet published to npm. Use the `.mcpb` bundle or local install above.

"command not found after local build"

→ Point `args` at the full absolute path to `dist/index.js`, not the `productboard-mcp.js` wrapper.

License

MIT