fydbek MCP server
fydbek collects feedback on websites from clients, designers, copywriters and testers, right on the page, with a screenshot, the exact element and the browser context. The MCP server lets AI agents read that feedback, triage it, ask the reporter questions, export it to your task tracker and report back when a fix is ready. Everything the agent does is shown in fydbek with the app it came through, for example "via Claude".
Server URL
https://mcp.fydbek.com/mcpStreamable HTTP transport. Sign-in uses OAuth 2.1 with dynamic client registration: you log in to fydbek, choose the organization and approve access. You can disconnect at any time.
Connect
Claude (claude.ai, desktop, mobile): fydbek is in the Claude connector directory. Open it, click Connect and approve access in fydbek.
You can also go to Settings, Connectors, Add custom connector and paste the server URL.
ChatGPT: the fydbek app for ChatGPT is coming soon.
Claude Code and other clients with API tokens: create a token in fydbek under Settings and people, Tokens, then run:
claude mcp add --transport http fydbek https://mcp.fydbek.com/mcp --header "Authorization: Bearer fyd_pat_..."You need a fydbek account. Agents get the same permissions as the account or token they act for, scoped to one organization.
Tools
| Tool | Access | What it does |
|---|---|---|
list_projects | read | Websites (projects) in the organization with counts of open feedback. |
list_feedback | read | Compact list of feedback in a project, filter by status, type, reporter role, page, date or link to another tool. |
get_feedback | read | Full feedback: text, suggested text edit, element with CSS selector, browser and viewport, console and network errors, thread, links and the screenshot. |
get_page_feedback | read | Open feedback for one page, for coding agents working on that page. |
get_changes | read | New feedback, comments and status changes since a cursor. |
update_feedback | write | Status, type, priority, title, assignee or duplicate. Asking the reporter (needs_info) or marking ready for review requires a comment. |
add_comment | write | Comment in the thread, optionally internal (visible only to the team). |
attach_image | write | Image in the thread, typically a screenshot after a fix. |
link_external | write | Stores a link to a task in another tool (Linear, GitHub, ClickUp, Freelo, Orbit). Repeated calls never create duplicates. |
No tool deletes data. Write tools only change feedback within your organization.
Prompts
triage: triage new feedback, mark duplicates and ask the reporter when something is unclear.work_on_page: for coding agents, fix feedback for a page and send it for review with a screenshot.export_tasks: export feedback to another tool and store the links.client_summary: summary of a project for a client meeting.
Example prompts
- "Triage the new feedback in fydbek and ask the reporter when something is unclear."
- "What is waiting for the client's answer on codebros.cz? Summarize it for tomorrow's meeting."
- "Export triaged feedback without a Linear link to Linear and save the links in fydbek."
- "Find open feedback for the /pricing page, fix it in this repo and mark it ready for review with a screenshot."
Data and privacy
fydbek stores data in the EU (Cloudflare, EU jurisdiction). The MCP server returns only data from the organization you connected, within the scopes you approved. Disconnecting the app or revoking the token stops access immediately. Details: Privacy policy, Terms of service.