Connecting your agent

Step 1: Turn on MCP access in Productboard

MCP access is controlled by your workspace admin.

1. Go to Settings → MCP Server in your workspace (https://YOUR-SPACE.productboard.com/settings/mcp-server).
2. Turn on Enable MCP for this workspace.
3. Under Who can use MCP, choose which roles may connect an agent — for example, makers with admin access, makers, contributors, or viewers. If you don't select any role, every role can connect.

That's it on the Productboard side. Turning MCP off later pauses existing connections: members stay authorized, but their agents' requests are blocked until MCP is turned back on. To revoke every connection instead, use Disconnect all in the Danger zone section — members then need to reconnect.

Step 2: Connect your agent

You connect your agent to a single address: https://mcp.productboard.com, which serves workspaces hosted in the US region. Signing in happens through your browser, using your existing Productboard login.

Claude

Add Productboard to Claude as a custom connector with the server URL https://mcp.productboard.com, then sign in to Productboard when prompted. On Team and Enterprise plans, an organization owner adds the connector first; each member then connects and signs in individually.

Find out more about custom connectors in Claude.

Claude Code

1. In your terminal, add the server:

   Bash

   claude mcp add --transport http productboard https://mcp.productboard.com

2. Start Claude Code by running claude.

3. Run the /mcp command, choose productboard, and select Authenticate.

4. Your browser opens. Complete the sign-in, and you're connected.

Cursor

Add the server to your MCP configuration (mcp.json):

{
  "mcpServers": {
    "productboard": {
      "url": "https://mcp.productboard.com"
    }
  }
}

Find out more about Cursor and MCP configuration.

When you first use the connection, Cursor opens your browser to sign in to Productboard. Once that's done, you're connected.

Other MCP clients

The server uses standard remote MCP with OAuth sign-in, so most agents that support remote MCP servers can connect to the same address. Point your client at https://mcp.productboard.com and follow its instructions for adding a remote server.

Authorisation

MCP is currently accessible only via OAuth Dynamic Client Registration (DCR) with PKCE. For the full registration and token flow, see OAuth for MCP Clients (Dynamic Client Registration + PKCE).