Productboard MCP connector
Connect Productboard to Elaichi and Claude, ChatGPT, Cursor and the Elaichi Agent can find, read and update product specs, feedback notes, comments and feature status, each person acting inside their own Productboard access with every change logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Productboard to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Productboard once
-
Open Connections, choose Add connection, and pick Productboard.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Productboard. Productboard's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Productboard MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Productboard MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Productboard MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Productboard to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Productboard through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Product
Catch the feature up after a customer call
Ask the agent to add your call notes to the feature in Productboard and move its status, so the record reflects the conversation before you move on to the next meeting.
-
Customer success
Check where a requested feature stands
Before a renewal call, ask what status the features a customer asked for are in and read the latest comments, straight from Productboard.
-
Support
Attach a ticket's feedback to the right feature
When a customer describes a gap, have the agent find the matching feature in Productboard and add the feedback as a note so the product team sees it.
-
Engineering
Read the spec without leaving the editor
From Cursor, pull up the feature description and acceptance notes in Productboard, then leave a question in the comments for the product manager.
-
Sales
Answer roadmap questions during a demo
Ask which release a feature sits in and what its status is in Productboard, then give the prospect a straight answer instead of a follow-up email.
-
Leadership
Summarize what changed this week
Ask for the features whose status moved this week in Productboard, with a short summary of the open comments on each.
Try asking
- “Which features changed status this week in the Mobile app product?”
- “Attach this call summary to the SSO feature as a note”
- “Summarize open comments on features planned for the Q3 release”
Compare
Elaichi vs Zapier MCP vs Composio for Productboard
All three can connect Productboard to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Productboard tools | Allow or restrict single Productboard tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Productboard call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting Productboard gets you
5 screens from the product, each doing one job for your Productboard account.
The agent
Ask about any feature in plain language.
Type a question and get answers from live Productboard features, notes and comments.
- features
- notes
- comments
- releases
Ask Elaichi to work across your apps.
Which features changed status this week in the Mobile app product?
Attach this call summary to the SSO feature as a note
Summarize open comments on features planned for the Q3 release
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects Productboard to every client.
Claude, ChatGPT and Cursor reach Productboard through one governed endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Productboard toolbox.
Product, support and sales each see a toolbox scoped to the Productboard work they do.
- Product
- Customer success
- Support
- Engineering
ElaichiToolboxesShared connections
Teammates use Productboard without seeing a credential.
One person connects Productboard, shares it with teams, and nobody else handles a login.
- Product core
- Mobile
- Platform
- Customer success
ElaichiConnectionsAudit log
Every Productboard change names the person behind it.
When, who, what happened and which feature, kept in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
The weekly Productboard digest writes itself.
New notes are fetched, grouped and drafted into a digest a person approves before posting.
Productboard digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch features
Productboard
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Productboard
Queued
Collections and dashboards
Productboard health, computed on a schedule.
Features created over 14 days and a team breakdown, counted without a model involved.
Productboard health
Refreshed 4 minutes ago · every 15 minutes · from the features collection
Features
1,284 ↓ 12%
Notes
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Features created
Last 14 days
By team
Share of activity
Product core 34%
Mobile 27%
Platform 21%
Customer success 18%
FAQ
Frequently asked questions
How do I connect Productboard to Claude?
Two steps. In Elaichi, choose Productboard and connect it, which opens Productboard's own sign-in page where you sign in and approve access, with no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Productboard features, notes and comments are available in the conversation.
Does Productboard work with ChatGPT and Cursor as well as Claude?
Yes. Once Productboard is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Productboard once and every client you use picks it up.
What can an AI agent actually do with my Productboard data?
It can find features and specs in Productboard, read their descriptions, notes and comments, add new comments or feedback notes, and change a feature's status. What is available depends on what your Productboard account has set up, so the agent works with the products, features and releases you already use. Short, concrete asks, like naming the feature and the change you want, work better than long paragraphs.
Does connecting Productboard give the AI access to my whole workspace?
No. Each person signs in to Productboard as themselves, so the agent sees only the products, features and notes that person can already see in Productboard. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Productboard itself allows.
Can I stop an agent from deleting or changing things in Productboard?
Yes. Restrictions in Elaichi work per action, so you can allow reading features and notes in Productboard while blocking status changes or edits. A restricted action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however it is worded, can reach it.
What happens to a Productboard connection when someone leaves?
Offboarding that person in Elaichi ends their access to Productboard through every client at once. If they had shared a Productboard connection with a team, it keeps working for everyone else. Disconnecting Productboard once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Productboard MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Productboard is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Productboard?
Yes. Both let Claude, ChatGPT or Cursor use Productboard. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Productboard call.
How is Elaichi different from Composio for Productboard?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Productboard: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Productboard in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.