# Feedjolt [Health: Active]

**Category:** 📋 Product Management  
**Repository:** https://www.feedjolt.com/?utm_source=directory&utm_medium=listing&utm_campaign=fj_dir_allmcps  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/feedjolt

## Description
Feedjolt is a customer feedback board for SaaS product teams. Requests come in through a public portal, an embeddable widget, a per-workspace email address, Slack, or the REST API, and land in one inbox. Customers vote on posts, and Feedjolt also ranks requests by ARR, renewal risk and blocked deals, so the loudest request isn't automatically the top one.

Feedjolt's AI flags likely duplicates for a person to review, and agents work the board over MCP with the permissions a person grants. The MCP server works with Claude, Cursor and other MCP clients, so you can search and triage feedback from your editor.

Move a card and the public roadmap updates. Linear has two-way sync, and voters get an email when the linked issue ships. Connect a GitHub repo and Feedjolt drafts a changelog entry from recent commits and merged PRs; you edit it and publish it.

The portal runs on your domain with your logo and colors, and customers sign in with a magic link or Google. Pricing is a flat price per workspace, with unlimited boards, posts and contributors. Teams moving from Canny can import their existing boards, posts and votes.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Feedjolt does

Feedjolt centralizes customer requests collected through a public portal, embeddable widget, workspace-specific email address, Slack, or the REST API. Customers can vote on posts, while product teams can evaluate demand using ARR, renewal risk, and blocked-deal signals. This gives teams more context than vote totals alone when deciding what to triage.

The platform is designed for SaaS product teams managing boards of customer feedback. Its portal can run on a team's domain with its own logo and colors. Customers can sign in with a magic link or Google, and teams moving from Canny can import existing boards, posts, and votes.

## How it works

The MCP connection lets agents work with a Feedjolt board from Claude, Cursor, or another MCP client. Agents can search feedback and help with triage, subject to the permissions a person grants. Feedjolt's AI identifies likely duplicate requests, but a person reviews those matches rather than having them merged automatically.

Product workflow changes can flow into customer-facing updates. Moving a card updates the public roadmap. Feedjolt also supports two-way synchronization with Linear; when a linked issue ships, voters receive an email. After connecting a GitHub repository, Feedjolt drafts a changelog entry from recent commits and merged pull requests. A team member edits the draft before publishing it.

## Tools and capabilities

- Search and triage customer feedback through MCP clients.
- Review AI-flagged duplicate requests.
- Rank requests using votes, ARR, renewal risk, and blocked deals.
- Keep a public roadmap aligned with card movement.
- Synchronize linked work with Linear in both directions.
- Draft changelog entries from GitHub commits and merged pull requests.
- Import boards, posts, and votes from Canny.
- Collect requests through a portal, widget, email, Slack, or REST API.

## Limitations and notes

Agent actions follow the permissions granted by a person, so access depends on the user's Feedjolt permissions. Duplicate detection is a review step, not an automatic decision. GitHub changelog drafts require editing and publishing by the team, and Linear's voter notification applies when the linked issue ships.

Feedjolt uses a flat price per workspace and includes unlimited boards, posts, and contributors. The customer portal supports custom branding and Google or magic-link sign-in.

_Full upstream README: https://allmcps.com/mcp/feedjolt/readme_