FeedBear
FeedBear helps product teams collect, organize, and act on customer feedback, feature requests, comments, and changelog updates.
Verdict
Common use cases
- Triage new feature requests during standup
- Summarize top feedback themes for roadmap planning
- Link support tickets to existing feature threads
- Draft changelog entries from shipped items
- Pull customer quotes from feedback comments
Integration
- Vendor
- FeedBear
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
feedbear
Tools
- Add Item Comment
Publish a public comment on a FeedBear item as the API key creator. This action may notify post participants.
- Create Board Item
Create a feedback item on a FeedBear board without notifying users.
- Delete Board Itemdestructive
Permanently delete a FeedBear board item, with explicit force confirmation available for items with merged posts.
- Get Board Item
Get the full details of one feedback item from a FeedBear board.
- List Board Items
List or search feedback items on a FeedBear board, with optional status and sort filters. Returns one page and a cursor for controlled continuation.
- List Boards
List boards in the connected FeedBear project, optionally including private team-only boards.
- List Changelog Entries
List published FeedBear changelog entries newest first. Draft and scheduled entries are excluded.
- List Item Comments
List non-spam comments on a FeedBear item, newest first, including reply relationships. Returns one page and a cursor for controlled continuation.
- List Statuses
List the statuses configured for the connected FeedBear project.
- Update Board Item
Update selected fields of an existing FeedBear board item without notifying voters.
Setup
Setup guide
- 11. In FeedBear, navigate to Settings → Integrations → API and generate a new API key with the scopes you need (read-only for searching, write for creating items and comments). 2. Copy the key to your clipboard. 3. In Switchy, open your workspace settings and click Integrations, then find FeedBear in the MCP directory. 4. Paste your API key into the auth field and click Connect. 5. Switchy will verify the key and show you which FeedBear project it's tied to. 6. Open any Project in Switchy and type '@FeedBear list the top 5 feature requests from the mobile board' to confirm the connection works. 7. If you see a list of items with titles and vote counts, you're ready to go.
What teammates see: by default, memories from FeedBear are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Top Requests This Week
@FeedBear list the top 10 feature requests from the last week sorted by votes, then summarize the common themes in two sentences.
Changelog Draft
@FeedBear find all items marked 'Completed' in the last two weeks and draft a short changelog entry highlighting what shipped.
Customer Pain Points
@FeedBear list comments on the top 5 open bug reports and identify the most common user pain points mentioned.
Sprint Context Pull
@FeedBear get the full details and all comments for item #47 so I can understand what users actually need before we scope the work.
Post Triage Comment
@FeedBear add a comment to item #52 saying 'Thanks for the suggestion — we're reviewing this for Q2 and will follow up with questions next week.'
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@FeedBear review all comments on our top 3 feature requests and draft a summary of common themes for our planning doc
I reviewed 47 comments across the top 3 requests (dark mode, iOS app, Slack integration). Common themes: 1) Accessibility concerns—8 users mentioned eye strain and contrast needs for dark mode. 2) Workflow integration—users want the iOS app to sync with desktop and the Slack integration to support two-way updates. 3) Timeline anxiety—multiple commenters asked for ETAs or interim solutions. Recommended action: address timeline expectations in your next changelog update to reduce repeat questions.
This example chains List Board Items, Get Board Item, and List Item Comments to synthesize feedback patterns. The AI reasons over raw comment text to identify themes your team might miss. Useful for quarterly planning but requires manual verification—sentiment analysis is interpretive, not definitive.
Use-case deep-dives
When FeedBear beats spreadsheets for feature requests
A 6-person SaaS team gets 40-60 feature requests a week across email, Slack, and their public roadmap. They spend Monday mornings sorting duplicates and tagging themes. The FeedBear MCP wins here because it lets the team query items by status, add comments in bulk, and merge duplicates without leaving the AI workspace. The List Board Items tool with filters handles the sort; Add Item Comment closes the loop with customers. The threshold: if you're fielding fewer than 20 requests a month, a shared Google Sheet is faster to set up. Above that volume, the MCP pays for itself by keeping context in one place and letting the AI spot patterns across boards.
Why this MCP is overkill for weekly release notes
A 3-person product team ships every Thursday and writes a changelog entry summarizing the week's fixes and features. They want the AI to draft the entry by pulling closed items from FeedBear. The MCP can list changelog entries and read board items, but it can't create or edit changelog content—those actions aren't exposed. You'd still write the draft in FeedBear's UI, then reference it in Switchy. If your changelog workflow is already manual, this MCP adds a read-only lookup step but doesn't automate the writing. Better fit: teams who want to cross-reference shipped features against open requests during planning, not teams trying to auto-generate release notes.
When FeedBear MCP helps support find known issues fast
A 10-person support team at a B2B tool gets repeat questions about missing features. Before escalating to engineering, they want to check if the request is already on the public roadmap and link the customer to the existing thread. The FeedBear MCP's List Board Items and Get Board Item tools let the AI search feedback by keyword and return the URL and status in seconds. The team uses it during live chats to say "this is planned for Q2" with proof. The trade-off: if your FeedBear board has fewer than 50 items, a browser bookmark is faster. Above 100 items across multiple boards, the MCP saves 2-3 minutes per lookup and keeps the support rep in the same workspace.
Frequently asked
What does the FeedBear MCP let me do in Switchy?
It connects your FeedBear feedback boards to Switchy so AI can read, create, and comment on feature requests without switching tabs. You can ask AI to summarize top-voted items, draft responses to customer feedback, or create new board items from Slack threads. It also pulls changelog entries so AI knows what you've shipped recently.
Do I need admin access to connect FeedBear?
You need a FeedBear API key, which any account owner or admin can generate from the FeedBear settings. The MCP inherits the permissions of whoever created that key. If the key creator can't access private boards or delete items, neither can the AI. Standard team members typically can't generate API keys.
Can the FeedBear MCP vote on items or change their status?
No. It can read items, create new ones, add comments, and delete items with force confirmation, but it can't upvote, change status labels, or merge duplicate posts. For status changes or voting, you still need to open FeedBear directly or use their API separately.
Why use this instead of just checking FeedBear manually?
AI can triage dozens of feedback items in seconds and draft personalized responses based on your product roadmap or recent changelog. If you're answering the same feature request across five different posts, the MCP lets AI spot the pattern and write one consolidated reply. Manual checking works fine for small boards; this scales better.
Who on the team should connect the FeedBear MCP?
Whoever owns customer feedback or product management. The API key creator's name appears on all AI-generated comments, so connect it under a shared account or the PM who normally responds to FeedBear. Don't connect it under an engineer's personal key unless you want customers seeing their name on every AI reply.