How to integrate Productboard MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Productboard logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Productboard to Mastra AI 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 Mastra AI 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

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Productboard tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Productboard tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Productboard agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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 & 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 Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Productboard through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Productboard

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["productboard"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Productboard MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "productboard" for Productboard access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Productboard toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "productboard-mastra-agent",
    instructions: "You are an AI agent with Productboard tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

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

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;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        productboard: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Productboard toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Productboard and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["productboard"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      productboard: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "productboard-mastra-agent",
    instructions: "You are an AI agent with Productboard tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

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

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { productboard: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Productboard through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

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 Mastra AI?

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