Can't connect, or sign-in keeps looping
If your client reports that it couldn't reach or connect to the server, or you keep ending up back at the sign-in page:
- Check the server URL. It should be
https://mcp.productboard.com, with no extra path. - Check your workspace's region.
https://mcp.productboard.comserves workspaces hosted in the US region. - Sign in to the right workspace. The connection uses the workspace you sign in to, so if you belong to several, sign in to the one you want to connect. If your account isn't an active member of that workspace, Productboard shows "Your account is not an active member of this workspace. Sign in to the workspace you want to authorize and try again."
- Expect to sign in each time you connect. Productboard asks you to sign in again whenever you authorize a client, even if you're already signed in. If your workspace requires multi-factor authentication, you'll complete that before the consent screen.
- Finish sign-in in the browser that opens, and make sure it allows cookies for
productboard.com. - Still stuck? Remove the server from your client, add it again, and sign in from scratch.
"MCP access is not enabled for this workspace"
When you try to connect, Productboard shows an Authorization error page: "MCP access is not enabled for this workspace, or your role is not allowed to authorize MCP applications." Requests from an agent that was already connected fail with a Forbidden error instead.
If MCP is turned off for your workspace, ask a workspace admin to turn on Enable MCP for this workspace under Settings → MCP Server. Connections paused while MCP was off resume when it's turned back on — no need to reconnect.
Only workspace admins see the MCP Server settings page. If an admin can't find it, let us know through Feedback & Help.
Your role isn't allowed to use MCP
The same error appears when MCP is on but your role isn't on the allowed list. Workspace admins choose which roles can connect under Who can use MCP in Settings → MCP Server. Members whose role isn't selected are blocked from connecting, even if MCP is enabled. If no role is selected, every role can connect.
Ask a workspace admin to add your role. If your role is removed after you connect, your agent's requests are blocked until it's added back.
Access expired or was revoked
If an agent that used to work starts asking you to sign in again, or reports that it's unauthorized, its access has ended. This happens when:
- A workspace admin selected Disconnect all under Settings → MCP Server, which revokes every MCP connection in the workspace.
- The connection wasn't used for 180 days, so its sign-in expired.
Reconnect to restore access. In Claude Code, run /mcp, choose productboard, and select Authenticate. In other clients, reconnect the server or remove it and add it again.
If Productboard shows "Invalid client_id." after you sign in, your client's registration with Productboard was removed. Remove the server from your client and add it again so the client registers afresh.
Too many registration requests (HTTP 429)
When a client connects for the first time, it registers itself with Productboard. Registration is limited to 60 requests per minute and 500 requests per day per IP address, so networks where many people share an IP address can hit the limit. If your client reports HTTP 429 while connecting, wait and try again: the per-minute limit resets within a minute, the daily limit the next day.
Building your own client? Register once and reuse the client_id. See OAuth for MCP Clients.
Getting better results
- Agent isn't using the connection? Start your request with "use productboard…" so it reaches for the right tools.
- Agent returns IDs instead of names? Ask it to use names — "use the spec name, not the ID."
- Search takes a few turns? Specs are found by name, owner, tags, and more. If the first search misses, refine your wording or name the spec directly.
Still stuck, or have feedback on the MCP server? Let us know through Feedback & Help.