Website Feedback Tool

Read visual design reviews from live web pages: comments, CSS selectors, styles, console errors.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
72%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~491Tokens (tool definitions)
~531 BTypical response size
Minimal attention impact (0.38% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "website-feedback-tool": {
      "url": "https://dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcp"
    }
  }
}

Remote endpoints

https://dfozgzaflbudvthtlhvn.supabase.co/functions/v1/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢list_reviews

List 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. Use this to pick which review to apply.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_latest_review

Get the most recent design review as Markdown feedback (comments, selectors, computed styles, console/network errors, screenshot URLs).

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢get_review(reviewId)

Get one design review by id as Markdown feedback. Obtain the id from list_reviews.

Input Schema

{
  "type": "object",
  "properties": {
    "reviewId": {
      "type": "string",
      "description": "Review id, e.g. rvw_abc123…"
    }
  },
  "required": [
    "reviewId"
  ],
  "additionalProperties": false
}
🟢open_review_link(url)

Open a design review from a share link somebody sent you (a /r/<id>?t=… URL) and get its feedback as Markdown. Use this when the user pastes a review link rather than asking for their own reviews — the link carries its own access, so the review does not need to have been pushed from this machine. It stays out of list_reviews: to open it again later, use the link again.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The full share link, including the ?t=… part."
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}
🟢get_screenshot(reviewId, commentId, url)

View a comment's screenshot inline (clients don't fetch image URLs themselves). Pass the reviewId and the comment id shown next to the screenshot in get_review.

Input Schema

{
  "type": "object",
  "properties": {
    "reviewId": {
      "type": "string",
      "description": "Review id, e.g. rvw_abc123…"
    },
    "commentId": {
      "type": "string",
      "description": "The comment id shown beside the screenshot in get_review."
    },
    "url": {
      "type": "string",
      "description": "Only for a review you opened with open_review_link: the same share link, which is what authorises reading its screenshots."
    }
  },
  "required": [
    "reviewId",
    "commentId"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools