F

Feedjolt

Search and triage customer feedback in Feedjolt from Claude, Cursor, and other MCP clients.

Install Feedjolt

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://api.feedjolt.com/mcp/

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 1d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 1d ago · Nov 12, 2026, 19:02 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://api.feedjolt.com/mcp/

Overview

Feedjolt MCP server connects AI clients to a customer feedback board for SaaS product teams. It lets agents search and triage requests while applying the permissions granted by a person, with prioritization based on ARR, renewal risk, and blocked deals alongside customer votes. Feedjolt can flag likely duplicate requests for review, and moving a card can update the public roadmap. Reach for it when product teams need to manage feedback from an editor without relying only on the loudest request.

Use cases

  • Search customer feedback from an editor
  • Triage requests using votes and account signals
  • Review likely duplicate feedback posts
  • Sync product work with a public roadmap
  • Draft changelog entries from GitHub activity

Key features

  • MCP-based feedback search and triage
  • Prioritization by votes, ARR, renewal risk, and blocked deals
  • AI-assisted duplicate detection with human review
  • Two-way Linear synchronization
  • GitHub-based changelog drafts
  • Canny data import

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

4/4 checks healthy over the last 13d

How Feedjolt works

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Feedjolt

Feedjolt is an MCP server that connects AI clients to a Feedjolt customer feedback workspace. It provides tools for searching and triaging customer requests, while respecting permissions granted by a person. Teams can use it from Claude, Cursor, and other MCP clients to work with feedback boards.

Yes, Feedjolt works with Cursor through MCP. Developers can search and triage customer feedback from their editor, with agent actions limited by the permissions a person grants.

Feedjolt combines customer votes with ARR, renewal risk, and blocked-deal signals. This helps teams weigh business impact instead of automatically treating the most-voted request as the highest priority.

Yes, Feedjolt supports two-way Linear synchronization and can draft changelog entries from recent GitHub commits and merged pull requests. Teams edit and publish the generated changelog entry, and voters receive an email when a linked Linear issue ships.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFeedjolt AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/feedjolt?style=directory)](https://allmcps.com/mcp/feedjolt)
HTML Embed
<a href="https://allmcps.com/mcp/feedjolt"><img src="https://allmcps.com/api/badge/feedjolt?style=directory" alt="Feedjolt on AllMCPs" /></a>