Productboard logo productboard.com

Live

Productboard API and MCP server

Productboard's API tokens need a workspace admin on the Pro plan or higher, and its API lists no endpoints for boards. Sign in to Productboard once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Productboard.

Productboard has no API for this. So we run one for you.

Productboard's own API, a GitHub MCP server and Cotlet compared
What you need Productboard's APIGitHub MCP serverCotlet
Feedback triage, insight links, statuses No Partly Yes, 12 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Productboard changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 22, 2026. Sources: Productboard developers: API v2 overview · Productboard developers: MCP server (beta) · Productboard developers: Connecting your agent · Productboard developers: API token authentication

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Productboard in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Productboard to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 12 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Productboard and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/productboard with its own method and path, such as POST /api/v1/productboard/feedbacks, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Productboard API and MCP server do?

12 tools on your own Productboard account. Agents call them as operations of the MCP tools productboard_read and productboard_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Productboard tools in Cotlet's MCP server and REST API
Tool What it does Access
list_feedback Feedback items from your insights boards, with company, user, tags, owner, processed flag and insight count. read
get_feedback One feedback item with its full text, company, user, tags and the insights that link it to features. read
search_features Features in your product hierarchy by name, with status, owner and parent. read
get_feature One feature with its description, status, owner, parent and the number of linked insights. read
list_feature_insights Insights linked to a feature: the feedback title, the highlighted quote and the importance. read
list_feature_statuses The status names your workspace uses for features and subfeatures. read
list_objectives Objectives with their status and key results. read
create_feedback Adds a feedback item with a title, text, company, user and tags. write
link_feedback_to_feature Highlights a quote in a feedback item and links it to a feature with an importance. write
unlink_insight Removes the link between a feedback item and a feature. write
mark_feedback_processed Marks a feedback item processed, or takes it back to unprocessed. write
update_feature_status Changes the status of a feature or subfeature. writeasks first

Scroll the table for all 12 tools.

Ask in plain words. Your agent does the rest.

All Productboard use cases

Is it safe to connect Productboard?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Productboard API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Productboard is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does Productboard have an API?

Productboard has a full REST API v2 for notes, entities, teams, members, webhooks and analytics, and a beta MCP server at mcp.productboard.com that works on specs (checked 22 Oct 2026). API tokens need a workspace admin on the Pro plan or higher, and the API reference lists no endpoints for boards.

How do I get access?

Sign up free, open Productboard under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 12 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Productboard yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Productboard sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: update_feature_status wait for your OK by default. You can switch that off per tool for scheduled runs.

Do I need to be a workspace admin?

No. Cotlet works in your own Productboard login, so your role decides what your agent can do. Productboard's API tokens need a workspace admin on the Pro plan or higher, which is why many makers cannot use the API at all. Viewers cannot add feedback, and create_feedback fails with APP_PERMISSION_DENIED for them.

How is this different from Productboard's own MCP server?

Productboard's MCP server is in beta. An admin turns it on under Settings > MCP Server and picks the roles that may use it, and you sign in with OAuth. Its documentation describes finding, reading, refining and commenting on specs and updating an item status. Cotlet's tools work on feedback, insight links, features, statuses and objectives.

Can it change roadmaps and boards?

No. The tools cover feedback, features, statuses and objectives. Timeline and columns boards stay in Productboard, and so do milestones, board filters and customer-specific roadmaps.

Should I use a Productboard MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Productboard changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with Productboard?

No. Cotlet is independent and not affiliated with Productboard.

Give your agent access to Productboard.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free