P

productboard.com

3 integrations · MCP · REST

Productboard exposes a REST API v2 at `https://api.productboard.com` authenticated by bearer API token, OAuth 2.0 authorization-code, or server-to-server JWT-bearer tokens, a SCIM API at `https://api.productboard.com/scim/v2` with auth not confirmed from the recorded docs, and a beta MCP server at `https://mcp.productboard.com` authenticated via OAuth Dynamic Client Registration plus PKCE.

discovered 2mo ago
MCP servers1
REST · OpenAPI2
Credentials
Productboard personal access tokenapi_keyGet key ↗

In Productboard's developer docs, Productboard lists API Token (PAT) as a supported authentication method for REST API v2. Use the API token instructions in Authentication and API Token Authentication to generate a token in your Productboard workspace/account, then send it on REST API requests.

Productboard OAuth 2.0 app (authorization code)oauth2Set up OAuth ↗

For a server-side integration acting on Productboard users' behalf, create/configure an OAuth app per the OAuth 2.0 (Authorization Code) guide, then use Productboard's authorization-code flow to obtain bearer tokens for the REST API.

Productboard server-to-server OAuth app (JWT bearer)oauth2_ccSet up OAuth ↗

For backend automation without a user present, configure a server-to-server integration following OAuth Server-to-Server (JWT). Productboard documents this as an OAuth 2.0 JWT bearer flow that returns bearer access tokens for API calls.

OAuth 2.0oauth2
OAuth 2.0 — self-onboarding

Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.

conventions · 1/8 published

Publish these signals → /publishing