How to integrate Productboard MCP with Claude Code

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Productboard logo
Claude Code logo
divider

Introduction

Manage your Productboard directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Productboard with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Productboard to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

Supported Tools & Triggers

Tools
Add Note FollowersTool to add multiple followers to a Productboard note.
Add Note TagAdds a tag to a Productboard note for categorization and organization.
Create Company in ProductboardTool to create a new company in Productboard.
Create Company Custom FieldTool to create a new custom field for companies.
Create ComponentTool to create a new (sub)component under a product or component.
Create Entity RelationshipTool to create a relationship between two entities in Productboard.
Create Entity (v2)Tool to create a new entity in Productboard using the v2 API.
Create FeatureTool to create a new feature or subfeature in Productboard.
Create Feature-Objective LinkTool to create a link between a feature and an objective (OKR).
Create Note LinkTool to create a link between a note and an entity.
Create Note (v2)Tool to create a new note in Productboard using the v2 API.
Create ObjectiveTool to create a new objective in Productboard.
Create Objective-Feature LinkTool to create a new link between an objective and a feature.
Create ReleaseTool to create a new release in Productboard.
Create UserTool to create a new user in Productboard.
Create Webhook SubscriptionTool to create a new webhook subscription.
Delete CompanyTool to delete a specific company.
Delete Company FieldTool to delete a specific company custom field.
Delete Custom Field ValueTool to delete a custom field value from a hierarchy entity in Productboard.
Delete Entity RelationshipTool to delete a relationship between two entities.
Delete Entity V2Tool to delete a PM entity using the v2 API.
Delete FeatureTool to delete a specific feature.
Delete Feature Objective LinkTool to delete a link between a feature and an objective.
Delete InitiativeTool to delete a specific initiative.
Delete Key ResultTool to delete a specific key result from Productboard.
Delete Note RelationshipTool to delete a note relationship.
Delete Note V2Tool to delete a note using the v2 API.
Delete Note TagTool to remove a tag from a Productboard note.
Delete ObjectiveTool to delete a specific objective from Productboard.
Delete Objective-Feature LinkTool to delete a link between an objective and a feature.
Delete ReleaseTool to delete a specific release.
Delete UserTool to delete a specific user.
Delete Webhook SubscriptionTool to delete a webhook subscription.
Get ComponentTool to retrieve details of a specific component.
Get Custom Field ValueTool to retrieve a custom field's value for a specific hierarchy entity.
Get Entity ConfigurationTool to retrieve entity configuration for a specific type.
Get Entity V2Tool to retrieve a PM entity using the v2 API.
Get Feature Release AssignmentTool to retrieve a specific feature release assignment.
Get Hierarchy Entity Custom FieldTool to retrieve a specific custom field definition for hierarchy entities.
Get Notes Configuration V2Tool to retrieve note configuration by type (simple, conversation, or opportunity).
Get Note V2Tool to retrieve a note using the v2 API.
Get ObjectiveTool to retrieve details of a specific objective.
Get ReleaseTool to retrieve details of a specific release by ID.
Get Release GroupTool to retrieve details of a specific release group.
Get Webhook SubscriptionTool to retrieve details of a specific webhook subscription.
List Analytics Member Activities V2Tool to retrieve member activity analytics data from Productboard.
List CompaniesTool to list companies.
List Company Custom FieldsLists all custom field definitions for companies in your Productboard workspace.
List Custom FieldsLists custom field definitions for hierarchy entities (Products, Components, Features).
List Custom Field ValuesLists custom field values for hierarchy entities (products, components, features) in Productboard.
List Entities Configurations V2Tool to retrieve configurations for all entity types in Productboard.
List Entity RelationshipsTool to retrieve relationships for an entity in Productboard.
List Entities V2Tool to list entities from Productboard using the v2 API.
List Feature InitiativesTool to list initiatives linked to a given feature.
List Feature ObjectivesLists all objectives (OKRs) linked to a top-level feature.
List Feature Release AssignmentsTool to list feature–release assignments.
List Feature StatusesTool to list feature statuses.
List Feedback Form ConfigurationsTool to list feedback form configurations.
List InitiativesTool to list initiatives from Productboard.
List Jira IntegrationsTool to list Jira integrations.
List Key ResultsList key results from Productboard.
List Notes Configurations V2Tool to list note configurations from Productboard v2 API.
List Note LinksTool to list links associated with a note.
List Note Relationships V2Tool to retrieve relationships associated with a note.
List Notes V2Tool to retrieve a paginated list of notes from Productboard using the v2 API.
List Note TagsTool to retrieve all tags associated with a specific Productboard note.
List Objective Linked FeaturesLists all features linked to a specific objective.
List Objective Linked InitiativesTool to list initiatives linked to a specific objective.
List Plugin IntegrationsList all plugin integrations in the Productboard workspace.
List Release GroupsLists all release groups in the Productboard workspace.
List ReleasesTool to list all releases in Productboard.
List UsersRetrieves a paginated list of all users in the Productboard workspace.
List Webhook SubscriptionsTool to list all webhook subscriptions.
Remove Note FollowerTool to remove a follower from a Productboard note.
Retrieve CompanyTool to retrieve details of a specific company.
Retrieve Company FieldTool to retrieve details of a specific company custom field.
Retrieve Company Field ValueTool to retrieve a specific company custom field value.
Retrieve FeatureTool to retrieve details of a specific feature.
Retrieve ProductTool to retrieve details of a specific product.
Retrieve UserTool to retrieve details of a specific user.
List SCIM UsersTool to list users via SCIM.
Search Entities V2Tool to search for entities across Productboard using the v2 API.
Set Company Field ValueTool to set or replace a specific company custom field's value.
Set Custom Field ValueTool to set a custom field value on a hierarchy entity.
Set Entity Parent RelationshipTool to set parent relationship on an entity.
Set Feature Release AssignmentTool to update a feature release assignment.
Set FeaturesTool to update a feature by ID.
Set Note Customer RelationshipTool to set a customer relationship on a note in Productboard.
Set ProductTool to update a product using PUT method in Productboard.
Update Company Custom FieldTool to update a company custom field name.
Update CompanyTool to update an existing company in Productboard.
Update ComponentTool to update an existing component.
Update Entity V2Tool to update a PM entity using the v2 API.
Update FeaturesTool to update a feature in Productboard.
Update Note V2Tool to update a note using the v2 API.
Update ObjectiveTool to update an existing objective in Productboard.
Update ProductTool to update a product in Productboard.
Update ReleaseTool to update an existing release in Productboard.
Update UserTool to update a user's information.

What is the Productboard MCP server, and what's possible with it?

The Productboard MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Productboard account. It provides structured and secure access to your product management workspace, so your agent can perform actions like managing feature ideas, collecting user feedback, prioritizing roadmap items, and aligning strategic goals on your behalf.

  • Centralized feedback collection: Let your agent gather, aggregate, and organize product feedback from stakeholders and customers, so nothing slips through the cracks.
  • Feature and idea management: Enable your agent to create, update, categorize, and prioritize feature ideas or product requests in your Productboard workspace.
  • Roadmap planning and alignment: Ask your agent to assist in building and updating product roadmaps, ensuring initiatives align with business objectives and customer needs.
  • Insightful prioritization workflows: Have the agent score, sort, and recommend features for development using built-in prioritization frameworks and customer impact data.
  • Collaboration and stakeholder updates: Empower your agent to share status updates, progress changes, and new plans with internal teams and stakeholders directly from Productboard.

Connecting Productboard via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Productboard) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Productboard account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["productboard"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http productboard-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Productboard. This URL will be used to connect Claude Code to Productboard.

What's happening:

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Productboard
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Productboard MCP to Claude Code

bash
claude mcp add --transport http productboard-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (productboard-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Productboard MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your productboard-composio entry in the list
  • This confirms that Claude Code can now access Productboard tools

If everything is wired up, you should see your productboard-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Productboard

The first time you try to use Productboard tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Productboard
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Productboard authorization flow
  • Return to the terminal and start using Productboard through Claude Code

Once authenticated, you can ask Claude Code to perform Productboard operations in natural language. For example:

  • "Create a new feature idea in Productboard"
  • "List all features in the current release"
  • "Add customer feedback to a specific feature"

Complete Code

Here's the complete code to get you started with Productboard and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["productboard"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http productboard-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Productboard with Claude Code using Composio's MCP server. Now you can interact with Productboard directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Productboard operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Productboard operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Productboard MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Productboard MCP?

With a standalone Productboard MCP server, the agents and LLMs can only access a fixed set of Productboard tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Productboard and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Productboard tools.

Can I manage the permissions and scopes for Productboard while using Tool Router?

Yes, absolutely. You can configure which Productboard scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Productboard data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.