Feedback DevTools for VS Code

What the MCP returns

Shipped in PR #30: every open item includes source-mapped component, file (path:line:col), console, and network. PR #53 adds replaySummary / replayUrl and cited playwrightFlows on get_feedback_context. #60/#57/#59 add clusters + GitHub/Linear issue tools (Usero foil; Marker MCP create-tickets foil — their FR still open). Hosted MCP has the full catalog; local stdio via the public feedback-devtools-mcp npm package has the 16 read/triage tools until 0.2.0 publishes.

Sample source-mapped payload

Same shape list_open_feedback and get_feedback_context return after #30 / #53 (replay + Playwright cites on context).

{
  "id": "fb_demo_1",
  "status": "new",
  "changeType": "fix_bug",
  "priority": "high",
  "summary": "Make the primary button blue",
  "expectedBehavior": "Button uses the brand primary blue token",
  "component": "Button",
  "file": "src/Button.tsx:12:3",
  "console": {
    "errorCount": 1,
    "warnCount": 0,
    "errors": [
      {
        "level": "error",
        "message": "undefined is not a function",
        "stack": "TypeError: undefined is not a function\n    at Button (src/Button.tsx:12:3)"
      }
    ]
  },
  "network": {
    "failedCount": 1,
    "failed": [
      {
        "method": "GET",
        "url": "/api/theme",
        "status": 500,
        "statusText": "Internal Server Error"
      }
    ]
  },
  "pageContext": {
    "url": "https://app.example.com/home",
    "title": "Home"
  },
  "replayUrl": "https://blob.example.com/replays/demo/fb_demo_1.json",
  "replaySummary": {
    "durationMs": 45000,
    "clicks": 3,
    "routes": [
      "https://app.example.com/home"
    ],
    "inputInteractions": 1,
    "mutations": 7
  },
  "playwrightFlows": [
    {
      "id": "fl_home",
      "name": "Home smoke",
      "actionCount": 4,
      "pageUrl": "https://app.example.com/home",
      "match": "page_path",
      "specCite": "import { test } from '@playwright/test';\ntest('home', async ({ page }) => { await page.goto('/home'); });"
    }
  ]
}

Install in VS Code

Option A — hosted HTTP MCP (Copilot agent mode)

One-click opens VS Code via vscode.dev/redirect and installs the hosted MCP at https://server-production-14a9.up.railway.app/mcp. Add the Authorization and X-SDK-Token headers yourself in MCP settings — same caveat as Cursor one-click. Requires VS Code 1.101+ with GitHub Copilot Chat / agent mode.

Workspace .vscode/mcp.json (note servers, not mcpServers):

{
  "servers": {
    "feedback-devtools": {
      "type": "http",
      "url": "https://server-production-14a9.up.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_fdt_session_COOKIE",
        "X-SDK-Token": "fk_sdk_YOUR_PROJECT_TOKEN"
      }
    }
  }
}

Option B — local stdio (public npm)

Same public npm stdio path as Cursor — feedback-devtools-mcp via npx -y, no registry auth. Hosted HTTP above is still the easiest path.

The published feedback-devtools-mcp@0.1.0 local server has the 16 read/triage tools above but not clusters or issue creation yet — claim_feedback, create_github_issue, create_tracker_issue, get_cluster, list_clusters are hosted-MCP-only until feedback-devtools-mcp@0.2.0 publishes. For those, use the hosted option below (recommended).

{
  "servers": {
    "feedback-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "feedback-devtools-mcp"
      ],
      "env": {
        "FEEDBACK_API_URL": "https://server-production-14a9.up.railway.app/api/v1",
        "FEEDBACK_SDK_TOKEN": "fk_sdk_YOUR_PROJECT_TOKEN",
        "FEEDBACK_AUTH_TOKEN": "YOUR_fdt_session_COOKIE"
      }
    }
  }
}

Discovery: /.well-known/mcp.json.

Copy fdt_session from the dashboard cookie after login, and the project SDK token from project settings. The endpoint is not open.

Example prompts

Three prompts for directory submission — each exercises a different tool.

1. list_open_feedback

   “List open Feedback DevTools items and show each component + file:line.”

2. get_feedback_context

   “Pull get_feedback_context for the highest-priority open item and open the mapped file:line.”

3. mark_feedback_resolved

   “After you open the PR, call mark_feedback_resolved with that feedback id and the PR URL.”

4. list_clusters

   “List feedback clusters and show severity + one verbatim sample quote each.”

5. create_github_issue

   “Create a GitHub issue from the highest-priority open item with the source-mapped body.”