Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider’s consent screen.
  • Scopes: notes:read, notes:write, entities:read, entities:write.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

​
Setup

  1. Get a Productboard workspace: Sign up at https://www.productboard.com (a free trial workspace works for testing). Public API access requires a plan with API access enabled.
  2. Register an OAuth2 application: Follow the developer documentation at https://developer.productboard.com/reference/oauth-authorization-code to register your OAuth2 client and obtain a client ID and secret. Set the redirect URI to your app’s /api/auth/productboard/callback URL.
  3. Set environment variables: Add PRODUCTBOARD_CLIENT_ID and PRODUCTBOARD_CLIENT_SECRET to your .env.
  4. Verify access: Complete the OAuth flow, then run List Entities with type=feature.

​
Provider notes

  • Tools target the Productboard REST API v2 (https://api.productboard.com/v2), which does not require the X-Version header used by the legacy v1 API
  • Access tokens expire after 24 hours; refresh tokens expire 180 days after issue or 60 minutes after use
  • Features, components, and initiatives are all ‘entities’ in v2 - filter with the type parameter
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as productboard__list_notes with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.