Design
websitefeedback.tools
An MCP server for accessing and managing design reviews collected via a browser extension, including feedback, comments, screenshots, selectors, and console/network errors.
ENDPOINT 1
https://dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcp
MCP server metadata
- Name
- website-feedback-tool
- Version
- 0.1.2
This server exposes design reviews captured in the "Design Review" browser extension. Every tool is scoped to the caller's agent key (the Authorization Bearer token). Typical flow: call list_reviews (or get_latest_review) to find a review, then get_review(reviewId) to read the feedback and implement the fixes; call get_screenshot(reviewId, commentId) to view a screenshot inline. If a tool reports a review is "not associated with this agent key" / "created with a different agent key", or list_reviews is unexpectedly empty, the token in THIS MCP config no longer matches the extension (the user reinstalled it, cleared data, or switched devices). Do NOT ask the user to paste their token into the chat. To fix WITHOUT pasting any secret into chat: open the Design Review browser extension → "Connect AI agent" and either (a) re-run the shown `claude mcp add` command in your terminal — it overwrites the old token — or (b) replace the Authorization Bearer token in your agent's MCP config FILE (e.g. ~/.codex/config.toml, ~/.cursor/mcp.json). Then reconnect this MCP server and send the review again. Never ask the user to paste the token into chat — it is an API-key-class secret. If the user has already pasted their Bearer token into THIS chat: do not repeat or echo it, and stay calm — this token is low-severity. It is read-only, unlocks only the user's own design reviews, and those expire on their own within a few days. The one-step fix is to click "Regenerate token" in the extension's "Connect AI agent" screen (it instantly invalidates the leaked token), then re-send the review. No need to treat it as a breach. You cannot change this server's token from within the session — it is read from the config file at startup. Treat the token as an API-key-class secret: never echo or log it.
Known tools 5
list_reviewsList your recent design reviews pushed from the Design Review browser extension (newest first): website, title, time, comment count and the reviewId to pass to get_review.
Inferred read-onlyget_latest_reviewGet the most recent design review as Markdown feedback (comments, selectors, computed styles, console/network errors, screenshot URLs).
Inferred read-onlyopen_review_linkOpen a design review from a share link somebody sent you (a /r/<id>?
Inferred read-onlyget_screenshotView a comment's screenshot inline (clients don't fetch image URLs themselves).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.website-feedback-tool]
url = "https://dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"website-feedback-tool": {
"type": "http",
"url": "https://dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: website-feedback-tool
Remote MCP URL: https://dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"website-feedback-tool": {
"url": "https://dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"website-feedback-tool": {
"type": "http",
"url": "https://dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "website-feedback-tool",
"transport": "streamable-http",
"url": "https://dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for supabase.co was fetched 2026-10-02T01:04:19.214Z.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.