6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Read and edit Productboard specs, log customer feedback and comment from Claude.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Productboard MCP server connects your Productboard workspace to Claude and Claude Code. Its 26 listed tools search and read product specs, edit spec documents, post comments, work with features and initiatives, and log customer feedback. A workspace admin must turn MCP on first. Sign-in is OAuth, and your Productboard role sets the ceiling on what it can change.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
mcp.productboard.com.Because a workspace admin has not turned MCP on, or your role is not on the allowed list. An admin enables it under Settings → MCP Server with Enable MCP for this workspace, and chooses roles under Who can use MCP. If no role is selected, every role can connect. Connections paused while MCP was off resume when it is turned back on.
No. Productboard ignores the scope a client requests and gives each MCP token the scopes of your role. Makers get read and write access to documents, entities and notes; Contributors lose entity and field writes; Viewers can only read. Scopes are an upper limit, and your role permissions inside Productboard still decide what Claude can see and change on your behalf.
Because its access ended. Productboard lists two causes: a workspace admin selected Disconnect all under Settings → MCP Server, or the connection went unused for 180 days. Reconnect to restore it. Productboard also asks you to sign in every time you authorise a client, even if you are already signed in, and requires multi-factor authentication first if your workspace uses it.
No, not at this address. Productboard states that mcp.productboard.com serves workspaces hosted in the US region. If your workspace is hosted elsewhere, the connection fails or loops back to the sign-in page. Productboard's troubleshooting guide lists region as one of the first things to check, alongside the exact server URL and signing in to the right workspace.
WWW-Authenticate header naming mcp.productboard.com/.well-known/oauth-protected-resource, which names the server itself as the authorization server and publishes no scopes (2026-11-18) · retrieved 2026-11-18Connect Productboard once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.