# How to integrate Productboard MCP with LangChain

```json
{
  "title": "How to integrate Productboard MCP with LangChain",
  "toolkit": "Productboard",
  "toolkit_slug": "productboard",
  "framework": "LangChain",
  "framework_slug": "langchain",
  "url": "https://composio.dev/toolkits/productboard/framework/langchain",
  "markdown_url": "https://composio.dev/toolkits/productboard/framework/langchain.md",
  "updated_at": "2026-05-12T10:22:51.282Z"
}
```

## Introduction

This guide walks you through connecting Productboard to LangChain using the Composio tool router. By the end, you'll have a working Productboard agent that can create a new feature idea in productboard, list all features in the current release, add customer feedback to a specific feature through natural language commands.
This guide will help you understand how to give your LangChain agent real control over a Productboard account through Composio's Productboard MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Productboard with

- [OpenAI Agents SDK](https://composio.dev/toolkits/productboard/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/productboard/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/productboard/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/productboard/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/productboard/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/productboard/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/productboard/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/productboard/framework/cli)
- [Google ADK](https://composio.dev/toolkits/productboard/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/productboard/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/productboard/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/productboard/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/productboard/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Connect your Productboard project to Composio
- Create a Tool Router MCP session for Productboard
- Initialize an MCP client and retrieve Productboard tools
- Build a LangChain agent that can interact with Productboard
- Set up an interactive chat interface for testing

## What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.
Key features include:
- Agent Framework: Build agents that can use tools and make decisions
- MCP Integration: Connect to external services through Model Context Protocol adapters
- Memory Management: Maintain conversation history across interactions
- Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

## 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.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `PRODUCTBOARD_ADD_NOTE_FOLLOWERS` | Add Note Followers | Tool to add multiple followers to a Productboard note. Use when you need to bulk-add existing users as followers to a specific note by their email addresses. |
| `PRODUCTBOARD_ADD_NOTE_TAG` | Add Note Tag | Adds a tag to a Productboard note for categorization and organization. Use this action to apply tags to notes based on their content, priority, source, or any other classification criteria. Tags help organize and filter notes in Productboard. If the specified tag doesn't exist in the workspace, it will be automatically created. Tags are case-sensitive. Common use cases: - Categorize notes by priority (e.g., "Urgent", "High Priority") - Label feature requests vs. bugs (e.g., "feature-request", "bug") - Mark notes for review stages (e.g., "needs review", "approved") - Associate notes with time periods (e.g., "Q1-2026", "Sprint-5") |
| `PRODUCTBOARD_CREATE_COMPANY` | Create Company in Productboard | Tool to create a new company in Productboard. Use when you need to add a company record after gathering its details and optional metadata. |
| `PRODUCTBOARD_CREATE_COMPANY_FIELD` | Create Company Custom Field | Tool to create a new custom field for companies. Use when you need to define custom company attributes in Productboard after confirming the field schema. |
| `PRODUCTBOARD_CREATE_COMPONENT` | Create Component | Tool to create a new (sub)component under a product or component. Use after determining the parent component ID. |
| `PRODUCTBOARD_CREATE_ENTITIES_RELATIONSHIPS_V2` | Create Entity Relationship | Tool to create a relationship between two entities in Productboard. Use when you need to establish a parent, child, link, or dependency relationship between entities. |
| `PRODUCTBOARD_CREATE_ENTITIES_V2` | Create Entity (v2) | Tool to create a new entity in Productboard using the v2 API. Use when you need to create products, components, features, subfeatures, initiatives, objectives, key results, releases, or release groups. |
| `PRODUCTBOARD_CREATE_FEATURE` | Create Feature | Tool to create a new feature or subfeature in Productboard. Use when you need to add a feature to a product or component, or create a subfeature under an existing feature. |
| `PRODUCTBOARD_CREATE_FEATURE_OBJECTIVE_LINK` | Create Feature-Objective Link | Tool to create a link between a feature and an objective (OKR). Use when associating a feature with a specific objective to track alignment. |
| `PRODUCTBOARD_CREATE_NOTE_LINK` | Create Note Link | Tool to create a link between a note and an entity. Use when associating a note with a productboard entity. |
| `PRODUCTBOARD_CREATE_NOTES_V2` | Create Note (v2) | Tool to create a new note in Productboard using the v2 API. Use when you need to create simple text notes or conversation-style notes with optional relationships to customers, companies, or external links. |
| `PRODUCTBOARD_CREATE_OBJECTIVES` | Create Objective | Tool to create a new objective in Productboard. Use when you need to create a strategic objective with optional details like owner, parent, status, and timeframe. |
| `PRODUCTBOARD_CREATE_OBJECTIVES_LINKS_FEATURES` | Create Objective-Feature Link | Tool to create a new link between an objective and a feature. Use when associating a feature with an objective (OKR). |
| `PRODUCTBOARD_CREATE_RELEASE` | Create Release | Tool to create a new release in Productboard. Use when you need to create a release with a name, description, and assigned release group. |
| `PRODUCTBOARD_CREATE_USERS` | Create User | Tool to create a new user in Productboard. Use when you need to add a user with email, name, and/or external identifier. |
| `PRODUCTBOARD_CREATE_WEBHOOK` | Create Webhook Subscription | Tool to create a new webhook subscription. Use when you need to register a public endpoint to receive webhooks from Productboard. |
| `PRODUCTBOARD_DELETE_COMPANY` | Delete Company | Tool to delete a specific company. Use when you have confirmed the company ID and need to remove it from Productboard. |
| `PRODUCTBOARD_DELETE_COMPANY_FIELD` | Delete Company Field | Tool to delete a specific company custom field. Use after confirming the field ID and ensuring no dependencies remain. |
| `PRODUCTBOARD_DELETE_CUSTOM_FIELD_VALUE` | Delete Custom Field Value | Tool to delete a custom field value from a hierarchy entity in Productboard. Use when you need to remove a custom field value from a product, component, or feature after confirming the field and entity IDs. |
| `PRODUCTBOARD_DELETE_ENTITIES_RELATIONSHIPS_V2` | Delete Entity Relationship | Tool to delete a relationship between two entities. Use when you need to remove a specific relationship type between entities in Productboard. |
| `PRODUCTBOARD_DELETE_ENTITIES_V2` | Delete Entity V2 | Tool to delete a PM entity using the v2 API. Use when you need to permanently remove an entity from Productboard. Returns 204 on success. |
| `PRODUCTBOARD_DELETE_FEATURE` | Delete Feature | Tool to delete a specific feature. Use when you have confirmed the feature ID and deleted its subfeatures before removal. |
| `PRODUCTBOARD_DELETE_FEATURE_OBJECTIVE_LINK` | Delete Feature Objective Link | Tool to delete a link between a feature and an objective. Use when you need to remove the association between a specific feature and objective. |
| `PRODUCTBOARD_DELETE_INITIATIVES` | Delete Initiative | Tool to delete a specific initiative. Use when you have confirmed the initiative ID and need to permanently remove it from Productboard. |
| `PRODUCTBOARD_DELETE_KEY_RESULTS` | Delete Key Result | Tool to delete a specific key result from Productboard. Use when you need to remove a key result that is no longer relevant or was created in error. |
| `PRODUCTBOARD_DELETE_NOTES_RELATIONSHIPS_V2` | Delete Note Relationship | Tool to delete a note relationship. Use when you need to remove a specific relationship between a note and another entity (customer or link) in Productboard. |
| `PRODUCTBOARD_DELETE_NOTES_V2` | Delete Note V2 | Tool to delete a note using the v2 API. Permanently removes the note and all its associated data. Returns 204 on success. |
| `PRODUCTBOARD_DELETE_NOTE_TAG` | Delete Note Tag | Tool to remove a tag from a Productboard note. Use when you need to detach a specific tag from a note after tagging. |
| `PRODUCTBOARD_DELETE_OBJECTIVES` | Delete Objective | Tool to delete a specific objective from Productboard. Use when you have confirmed the objective ID and need to permanently remove it. |
| `PRODUCTBOARD_DELETE_OBJECTIVES_LINKS_FEATURES` | Delete Objective-Feature Link | Tool to delete a link between an objective and a feature. Use when you need to remove the association between a specific objective and feature. |
| `PRODUCTBOARD_DELETE_RELEASE` | Delete Release | Tool to delete a specific release. Use when you have confirmed the release ID and need to remove it from Productboard. |
| `PRODUCTBOARD_DELETE_USER` | Delete User | Tool to delete a specific user. Use when you have confirmed the user ID and need to remove it from Productboard. |
| `PRODUCTBOARD_DELETE_WEBHOOK` | Delete Webhook Subscription | Tool to delete a webhook subscription. Use when you need to remove a webhook subscription from Productboard. |
| `PRODUCTBOARD_GET_COMPONENT` | Get Component | Tool to retrieve details of a specific component. Use when you have the component ID to fetch its full details including description, parent hierarchy, owner, and timestamps. |
| `PRODUCTBOARD_GET_CUSTOM_FIELD_VALUE` | Get Custom Field Value | Tool to retrieve a custom field's value for a specific hierarchy entity. Use when you need to get the current value of a custom field on a product, component, or feature. |
| `PRODUCTBOARD_GET_ENTITIES_CONFIGURATIONS_V2` | Get Entity Configuration | Tool to retrieve entity configuration for a specific type. Use when you need to understand the structure, fields, and relationships available for an entity type in Productboard. |
| `PRODUCTBOARD_GET_ENTITIES_V2` | Get Entity V2 | Tool to retrieve a PM entity using the v2 API. Use when you need to fetch details of a specific entity by its UUID. Returns entity data with optional field filtering. |
| `PRODUCTBOARD_GET_FEATURE_RELEASE_ASSIGNMENT` | Get Feature Release Assignment | Tool to retrieve a specific feature release assignment. Use when you need to check if a particular feature is assigned to a specific release. Returns assignment status (true/false) and entity references. |
| `PRODUCTBOARD_GET_HIERARCHY_ENTITIES_CUSTOM_FIELDS` | Get Hierarchy Entity Custom Field | Tool to retrieve a specific custom field definition for hierarchy entities. Use when you have a custom field ID to fetch its complete details including type, name, description, and options. |
| `PRODUCTBOARD_GET_NOTES_CONFIGURATIONS_V2` | Get Notes Configuration V2 | Tool to retrieve note configuration by type (simple, conversation, or opportunity). Use when you need to understand the fields, relationships, and constraints for a specific note type. |
| `PRODUCTBOARD_GET_NOTES_V2` | Get Note V2 | Tool to retrieve a note using the v2 API. Use when you need to fetch details of a specific note by its UUID. |
| `PRODUCTBOARD_GET_OBJECTIVE` | Get Objective | Tool to retrieve details of a specific objective. Use when you have the objective ID to fetch its full details including name, description, status, timeframe, and owner. |
| `PRODUCTBOARD_GET_RELEASE` | Get Release | Tool to retrieve details of a specific release by ID. Use when you need complete information about a single release. |
| `PRODUCTBOARD_GET_RELEASE_GROUP` | Get Release Group | Tool to retrieve details of a specific release group. Use when you have the release group ID to fetch its full details. |
| `PRODUCTBOARD_GET_WEBHOOKS` | Get Webhook Subscription | Tool to retrieve details of a specific webhook subscription. Use when you have the webhook ID to fetch its complete configuration. |
| `PRODUCTBOARD_LIST_ANALYTICS_MEMBER_ACTIVITIES_V2` | List Analytics Member Activities V2 | Tool to retrieve member activity analytics data from Productboard. Use when you need to analyze member engagement metrics, activity patterns, or usage statistics. Supports date-range filtering and pagination. |
| `PRODUCTBOARD_LIST_COMPANIES` | List Companies | Tool to list companies. Use when you need a paginated list of companies with optional filters. |
| `PRODUCTBOARD_LIST_COMPANY_FIELDS` | List Company Custom Fields | Lists all custom field definitions for companies in your Productboard workspace. This endpoint returns metadata about company custom fields (field schemas), not the actual values. Use this to discover available company fields before setting or retrieving field values. Returns field ID, name, type, and optional description/settings for each field. |
| `PRODUCTBOARD_LIST_CUSTOM_FIELDS` | List Custom Fields | Lists custom field definitions for hierarchy entities (Products, Components, Features). Returns metadata about custom fields (name, type, description) but not their values. Use this to discover available custom fields before querying their values for specific entities. |
| `PRODUCTBOARD_LIST_CUSTOM_FIELD_VALUES` | List Custom Field Values | Lists custom field values for hierarchy entities (products, components, features) in Productboard. Returns only non-empty values. Filter by custom field type or specific field ID. Combine filters to narrow results (e.g., get specific field values for a specific entity). Use links.next for pagination if more results exist. |
| `PRODUCTBOARD_LIST_ENTITIES_CONFIGURATIONS_V2` | List Entities Configurations V2 | Tool to retrieve configurations for all entity types in Productboard. Use when you need to understand available fields, relationships, and metadata for entity types like features, components, products, etc. |
| `PRODUCTBOARD_LIST_ENTITIES_RELATIONSHIPS_V2` | List Entity Relationships | Tool to retrieve relationships for an entity in Productboard. Use when you need to find parent, child, or link relationships between entities. |
| `PRODUCTBOARD_LIST_ENTITIES_V2` | List Entities V2 | Tool to list entities from Productboard using the v2 API. Use when you need a paginated list of PM entities (products, components, features, subfeatures, initiatives, objectives, key results, releases, or release groups) with optional filters. |
| `PRODUCTBOARD_LIST_FEATURE_INITIATIVES` | List Feature Initiatives | Tool to list initiatives linked to a given feature. Use when you need to retrieve all initiatives associated with a feature after confirming its ID. |
| `PRODUCTBOARD_LIST_FEATURE_OBJECTIVES` | List Feature Objectives | Lists all objectives (OKRs) linked to a top-level feature. Returns objective IDs and hypermedia links. Note: This endpoint only works with top-level features, not subfeatures. Use PRODUCTBOARD_LIST_FEATURES to obtain valid feature IDs first. |
| `PRODUCTBOARD_LIST_FEATURE_RELEASE_ASSIGNMENTS` | List Feature Release Assignments | Tool to list feature–release assignments. Use when you need to retrieve assignments for a specific feature or release with optional state or date filters; paginate using links.next. |
| `PRODUCTBOARD_LIST_FEATURE_STATUSES` | List Feature Statuses | Tool to list feature statuses. Use when you need to retrieve all feature status records in a paginated form. Follow 'links.next' for additional pages. |
| `PRODUCTBOARD_LIST_FEEDBACK_FORM_CONFIGURATIONS` | List Feedback Form Configurations | Tool to list feedback form configurations. Use when you need a paginated list of feedback form configurations. |
| `PRODUCTBOARD_LIST_INITIATIVES` | List Initiatives | Tool to list initiatives from Productboard. Use when you need a paginated list of initiatives with optional filters for archived status, owner, and status. Follow 'links.next' URL to retrieve additional pages. |
| `PRODUCTBOARD_LIST_JIRA_INTEGRATIONS` | List Jira Integrations | Tool to list Jira integrations. Use when you need to retrieve Productboard's connected Jira integrations with optional pagination. |
| `PRODUCTBOARD_LIST_KEY_RESULTS` | List Key Results | List key results from Productboard. Key results are measurable outcomes that track progress toward objectives. Use this action to: - Get all key results in the workspace - Filter key results by parent objective, status, owner, or archived state - Track progress on objectives through their associated key results Returns paginated results with comprehensive details including progress metrics, ownership, and status. Note: If key results are not enabled in the workspace, this returns an empty list gracefully. |
| `PRODUCTBOARD_LIST_NOTES_CONFIGURATIONS_V2` | List Notes Configurations V2 | Tool to list note configurations from Productboard v2 API. Use when you need to discover available fields, relationships, and validation rules for different note types (simple, conversation, opportunity, feature, initiative). |
| `PRODUCTBOARD_LIST_NOTES_LINKS` | List Note Links | Tool to list links associated with a note. Returns entities (products, components, features, or subfeatures) linked to the specified note. |
| `PRODUCTBOARD_LIST_NOTES_RELATIONSHIPS_V2` | List Note Relationships V2 | Tool to retrieve relationships associated with a note. Returns entities (users, companies, features, components, products) linked to the specified note via customer or link relationships. |
| `PRODUCTBOARD_LIST_NOTES_V2` | List Notes V2 | Tool to retrieve a paginated list of notes from Productboard using the v2 API. Use when you need to list notes with advanced filtering by archived/processed status, owner, creator, source, or date ranges. Supports field selection to optimize response size. |
| `PRODUCTBOARD_LIST_NOTE_TAGS` | List Note Tags | Tool to retrieve all tags associated with a specific Productboard note. Use when you need to view the current tags applied to a note for filtering, categorization, or analysis purposes. |
| `PRODUCTBOARD_LIST_OBJECTIVES_LINKS_FEATURES` | List Objective Linked Features | Lists all features linked to a specific objective. Returns feature IDs and hypermedia links for each linked feature. |
| `PRODUCTBOARD_LIST_OBJECTIVES_LINKS_INITIATIVES` | List Objective Linked Initiatives | Tool to list initiatives linked to a specific objective. Use when you need to retrieve all initiatives associated with an objective after confirming its ID. |
| `PRODUCTBOARD_LIST_PLUGIN_INTEGRATIONS` | List Plugin Integrations | List all plugin integrations in the Productboard workspace. Plugin integrations allow you to add columns to the Productboard Features board that integrate with third-party systems (e.g., Jira, GitHub). They enable a "push button" workflow to send features to external systems. Returns a paginated list of plugin integration objects, each containing id, name, and description. Use the links.next URL in pageUrl parameter to fetch subsequent pages. |
| `PRODUCTBOARD_LIST_RELEASE_GROUPS` | List Release Groups | Lists all release groups in the Productboard workspace. Release groups allow organizing multiple sets of releases (e.g., sprints, development cycles, internal releases, or marketing launches). Use this action to discover available release groups, their IDs, names, and whether they are archived. Returns the first 100 release groups. Follow the 'links.next' URL to retrieve additional pages if more than 100 groups exist. |
| `PRODUCTBOARD_LIST_RELEASES` | List Releases | Tool to list all releases in Productboard. Use when you need a paginated list of releases; follow links.next for more pages. |
| `PRODUCTBOARD_LIST_USERS` | List Users | Retrieves a paginated list of all users in the Productboard workspace. Returns user details including id, name, email, externalId, and companyId. The API paginates results (up to 100 users per page). Use the 'next' URL from the response links to fetch subsequent pages if available. |
| `PRODUCTBOARD_LIST_WEBHOOKS` | List Webhook Subscriptions | Tool to list all webhook subscriptions. Use when you need to retrieve all registered webhook endpoints and their configurations. |
| `PRODUCTBOARD_REMOVE_NOTE_FOLLOWER` | Remove Note Follower | Tool to remove a follower from a Productboard note. Use after confirming the note ID and follower email are correct. |
| `PRODUCTBOARD_RETRIEVE_COMPANY` | Retrieve Company | Tool to retrieve details of a specific company. Use when you have the company ID to fetch its full details. |
| `PRODUCTBOARD_RETRIEVE_COMPANY_FIELD` | Retrieve Company Field | Tool to retrieve details of a specific company custom field. Use when you have the custom field ID and need its metadata. |
| `PRODUCTBOARD_RETRIEVE_COMPANY_FIELD_VALUE` | Retrieve Company Field Value | Tool to retrieve a specific company custom field value. Use when you need the current value of a custom field for a given company by its IDs. |
| `PRODUCTBOARD_RETRIEVE_FEATURE` | Retrieve Feature | Tool to retrieve details of a specific feature. Use when you need complete info on one feature. |
| `PRODUCTBOARD_RETRIEVE_PRODUCT` | Retrieve Product | Tool to retrieve details of a specific product. Use when you have the product ID to fetch its full details. |
| `PRODUCTBOARD_RETRIEVE_USER` | Retrieve User | Tool to retrieve details of a specific user. Use when you have the user ID to fetch its full details. |
| `PRODUCTBOARD_SCIM_LIST_USERS` | List SCIM Users | Tool to list users via SCIM. Use when checking for existing users before creation. |
| `PRODUCTBOARD_SEARCH_ENTITIES_V2` | Search Entities V2 | Tool to search for entities across Productboard using the v2 API. Use when you need to find entities by various criteria like IDs, name, type, status, owner, parent, or archived status. Supports pagination for large result sets. |
| `PRODUCTBOARD_SET_COMPANY_FIELD_VALUE` | Set Company Field Value | Tool to set or replace a specific company custom field's value. Use when you need to update a company's custom field after confirming the field ID and ensuring the new value matches the field type. |
| `PRODUCTBOARD_SET_CUSTOM_FIELD_VALUE` | Set Custom Field Value | Tool to set a custom field value on a hierarchy entity. Use when you need to update a product, component, or feature field with a specific value after confirming the field and entity IDs. |
| `PRODUCTBOARD_SET_ENTITIES_RELATIONSHIPS_PARENT_V2` | Set Entity Parent Relationship | Tool to set parent relationship on an entity. Use when establishing hierarchical relationships between entities in Productboard. |
| `PRODUCTBOARD_SET_FEATURE_RELEASE_ASSIGNMENT` | Set Feature Release Assignment | Tool to update a feature release assignment. Use when you need to assign a feature to a release (set assigned=true) or remove it from a release (set assigned=false). |
| `PRODUCTBOARD_SET_FEATURES` | Set Features | Tool to update a feature by ID. Use when you need to modify feature properties like name, description, status, parent, timeframe, or archived flag. |
| `PRODUCTBOARD_SET_NOTES_RELATIONSHIPS_CUSTOMER_V2` | Set Note Customer Relationship | Tool to set a customer relationship on a note in Productboard. Use when you need to associate a note with a user or company customer entity. |
| `PRODUCTBOARD_SET_PRODUCT` | Set Product | Tool to update a product using PUT method in Productboard. Use when you need to modify a product's name, description, or owner with full replacement semantics. |
| `PRODUCTBOARD_UPDATE_COMPANIES_CUSTOM_FIELDS` | Update Company Custom Field | Tool to update a company custom field name. Use when you need to rename an existing company custom field in Productboard. |
| `PRODUCTBOARD_UPDATE_COMPANY` | Update Company | Tool to update an existing company in Productboard. Use when you need to modify company details such as name, description, domain, or source metadata. |
| `PRODUCTBOARD_UPDATE_COMPONENT` | Update Component | Tool to update an existing component. Use when you need to modify component name, description, owner, or parent entity. |
| `PRODUCTBOARD_UPDATE_ENTITIES_V2` | Update Entity V2 | Tool to update a PM entity using the v2 API. Use when you need to modify entity fields or apply patch operations to products, components, features, subfeatures, initiatives, objectives, key results, releases, or release groups. |
| `PRODUCTBOARD_UPDATE_FEATURES` | Update Features | Tool to update a feature in Productboard. Use when modifying feature details like name, description, status, owner, parent, or timeframe. |
| `PRODUCTBOARD_UPDATE_NOTES_V2` | Update Note V2 | Tool to update a note using the v2 API. Supports two update methods: direct field updates via 'fields' parameter or granular patch operations via 'patch' parameter. Use 'fields' for simple updates (e.g., changing name), and 'patch' for array operations like adding/removing tags. |
| `PRODUCTBOARD_UPDATE_OBJECTIVES` | Update Objective | Tool to update an existing objective in Productboard. Use when you need to modify objective properties such as name, description, owner, status, timeframe, or archive state. |
| `PRODUCTBOARD_UPDATE_PRODUCT` | Update Product | Tool to update a product in Productboard. Use when you need to modify a product's name, description, or owner. |
| `PRODUCTBOARD_UPDATE_RELEASE` | Update Release | Tool to update an existing release in Productboard. Use when you need to modify release properties such as name, description, state, archived status, release group, or timeframe. |
| `PRODUCTBOARD_UPDATE_USER` | Update User | Tool to update a user's information. Use when you need to modify a user's name, email, or external ID. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Productboard MCP server is an implementation of the Model Context Protocol that connects your AI agent to Productboard. It provides structured and secure access so your agent can perform Productboard operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

No description provided.

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

No description provided.
```python
pip install composio-langchain langchain-mcp-adapters langchain python-dotenv
```

```typescript
npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates your requests to Composio's API
- COMPOSIO_USER_ID identifies the user for session management
- OPENAI_API_KEY enables access to OpenAI's language models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

No description provided.
```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
```

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
```

### 5. Initialize Composio client

What's happening:
- We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
- Creating a Composio instance that will manage our connection to Productboard tools
- Validating that COMPOSIO_USER_ID is also set before proceeding
```python
async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
```

```typescript
const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
```

### 6. Create a Tool Router session

What's happening:
- We're creating a Tool Router session that gives your agent access to Productboard tools
- The create method takes the user ID and specifies which toolkits should be available
- The returned session.mcp.url is the MCP server URL that your agent will use
- This approach allows the agent to dynamically load and use Productboard tools as needed
```python
# Create Tool Router session for Productboard
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['productboard']
)

url = session.mcp.url
```

```typescript
const session = await composio.create(
    userId as string,
    {
        toolkits: ['productboard']
    }
);

const url = session.mcp.url;
```

### 7. Configure the agent with the MCP URL

No description provided.
```python
client = MultiServerMCPClient({
    "productboard-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
```

```typescript
const client = new MultiServerMCPClient({
    "productboard-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
```

### 8. Set up interactive chat interface

No description provided.
```python
conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Productboard related question or task to the agent.\n")

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
```

```typescript
let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Productboard related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
```

### 9. Run the application

No description provided.
```python
if __name__ == "__main__":
    asyncio.run(main())
```

```typescript
main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
```

## Complete Code

```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['productboard']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "productboard-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Productboard related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())
```

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['productboard']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "productboard-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Productboard related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
```

## Conclusion

You've successfully built a LangChain agent that can interact with Productboard through Composio's Tool Router.
Key features of this implementation:
- Dynamic tool loading through Composio's Tool Router
- Conversation history maintenance for context-aware responses
- Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

## How to build Productboard MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/productboard/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/productboard/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/productboard/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/productboard/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/productboard/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/productboard/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/productboard/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/productboard/framework/cli)
- [Google ADK](https://composio.dev/toolkits/productboard/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/productboard/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/productboard/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/productboard/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/productboard/framework/crew-ai)

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page.
- [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes.
- [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights.
- [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement.

## Frequently Asked Questions

### 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 LangChain?

Yes, you can. LangChain 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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)