Claude Connectors Directory listing
Feedback DevTools for Claude
Visual feedback → source-mapped file:line
Feedback DevTools turns stakeholder clicks on any UI into agent-ready context. Each item pins the React component, exact source file:line, console errors, and failed network calls. Install the MCP in Cursor or Claude to list open feedback, pull get_feedback_context (component + file + console + network + Claude Code prompt), and mark items resolved — without leaving the IDE. Hosted MCP at https://server-production-14a9.up.railway.app/mcp. Auth: dashboard Bearer session + project X-SDK-Token (not open). Pricing: Free $0 / Pro $9 per project per month.
What the MCP returns
Shipped in PR #30: every open item includes source-mapped component, file (path:line:col), console, and network. No extra tools in this listing.
| Tool | Returns |
|---|---|
| list_open_feedback | JSON array of open items with component, file (path:line:col), console, and network summaries. |
| get_feedback_context | One item with source-mapped fields plus a ready-to-run Claude Code prompt. |
| mark_feedback_resolved | Mark an item resolved; optionally record the PR URL. |
Sample source-mapped payload
Same shape list_open_feedback and get_feedback_context return after #30.
{
"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"
}
}Install in Claude
Claude Desktop (stdio)
Add to claude_desktop_config.json. Claude Code can use the same env vars via its MCP settings.
{
"mcpServers": {
"feedback-devtools": {
"command": "npx",
"args": [
"-y",
"@feedback/mcp-server"
],
"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"
}
}
}
}Remote connector URL
For Claude.ai custom connectors / directory submission, the MCP endpoint is:
https://server-production-14a9.up.railway.app/mcpAuth headers: Authorization: Bearer <fdt_session> and X-SDK-Token: <project sdk key>. 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.
- list_open_feedback
“List open Feedback DevTools items and show each component + file:line.”
- get_feedback_context
“Pull get_feedback_context for the highest-priority open item and open the mapped file:line.”
- mark_feedback_resolved
“After you open the PR, call mark_feedback_resolved with that feedback id and the PR URL.”
Directory submission kit
- Name
- Feedback DevTools
- Tagline
- Visual feedback → source-mapped file:line
- Documentation URL
- https://feedback-devtools.com/for/claude
- MCP URL
- https://server-production-14a9.up.railway.app/mcp
- Pricing
- Free $0 / Pro $9 per project per month
- Privacy
- /docs
Also see Cursor listing · file:line demo · docs