Cursor feedback integration: read user requests from your editor, over MCP
With FDBK's MCP server in Cursor, you can look up what users asked for while you build it: search posts, read a bug report with its comments, and mark the post in progress or done when you ship. Add the server to mcp.json with an API key from Developers. It's on Pro and Business.
Why bring feedback into the editor?
The context for a feature is in the request: what users tried, what they expected, the comments under it. Reading it next to the code, and closing the loop from the same place, saves the round trip to another tool.
How do I add it to Cursor?
Create an API key under Developers, then add an "fdbk" server to mcp.json with the /api/mcp URL and the key in an Authorization header. The docs have the snippet to copy.
What can it change?
It can create posts, reply as the team and change statuses. When a post moves to done it shows up in the public changelog, and people who posted or commented are emailed if the board has that turned on.
Getting started
- 01Create an API key under Developers.
- 02Add the server to Cursor's mcp.json.
- 03Ask for the top requests on a board.
- 04Mark the post done when it ships.
Free forever for one board. No card.
Questions
- Does it work with other editors?
- Yes, any MCP client that supports HTTP servers, like Claude Code, uses the same URL and key.
- Can I limit what the key can do?
- Keys act as the team on your workspace. Keep one per person or tool, and revoke it to cut access.