Condens MCP honesty matrix — read-only published Artifacts vs FDT create_github_issue / create_tracker_issue
Condens's product update "Connect Condens to Your AI Assistants with the MCP Server" (condens.io/product-updates/condens-mcp-server/, April 28, 2026) says the Condens MCP Server gives any compatible AI tool direct, read-only access to your published research. You can ask questions about findings in Claude or ChatGPT, have an agent pull from your repository mid-workflow, ground Figma Make designs in usability testing, or write code knowing what users said — all from published Artifacts.
The same page is explicit on privacy: "The Condens MCP Server is read-only. AI tools connected through it can retrieve published Artifacts; they cannot create, edit, or delete anything in your workspace." A Condens Admin enables MCP and controls who it is available to; each user connects their own account so access matches what they already see in Condens. Feedback DevTools is honest about a different surface: first-party create_github_issue / create_tracker_issue / mark_feedback_resolved plus source-mapped local-agent context with file:line. We do not claim server-side auto-opened or auto-merged PRs. Zero Condens product integration ships in FDT today.
Feedback DevTools is our product. Condens MCP read-only published Artifacts claim from https://condens.io/product-updates/condens-mcp-server/ (April 28, 2026) — lastChecked September 30, 2026 ~12:25pm Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs Condens MCP
| Feedback DevTools | Condens MCP | |
|---|---|---|
| Positioning | Capture + create_github_issue / create_tracker_issue / mark_feedback_resolved + local-agent file:line | Research MCP — query published Condens Artifacts; product update explicit read-only (cannot create/edit/delete) |
| Published MCP write surface (read-only honesty) | create_github_issue · create_tracker_issue · mark_feedback_resolved + local-agent file:line | Read-only — "can retrieve published Artifacts; they cannot create, edit, or delete anything" (Apr 28, 2026); no create_github_issue / create_tracker_issue / create_pr / open_pr / codebase / git write |
| create_github_issue / create_tracker_issue / create_pr | Yes create_github_issue / create_tracker_issue + capture-time file:line; no server-side create_pr | No — Condens MCP itself is read-only published Artifacts query; no create_github_issue / create_pr on the Condens MCP surface |
| Server-side auto-open / auto-merge PRs | No — we do not claim server-side auto PRs | No — Condens product update frames read-only Artifact access; Condens MCP does not open or merge GitHub PRs |
| Source maps / file:line | Yes — capture-time React component + file:line | Published Artifacts, studies, interviews, insights — research evidence, not React component file:line |
| Condens in FDT today | Zero — no Condens product integration ships in Feedback DevTools today | First-party Condens MCP into published Artifacts (Settings > Account > API & MCP Server; Business+ for Claude/ChatGPT) |
| Plan gate | Free plan forever + Pro $9/mo per project — MCP tools without a research-suite Business/Enterprise SKU | Business plan for Claude/ChatGPT connections; Enterprise for other integrations (Apr 28, 2026) — not a separate $9 MCP SKU |
Condens MCP read-only published Artifacts verified on condens.io/product-updates/condens-mcp-server/ (April 28, 2026) — lastChecked September 30, 2026 ~12:25pm Asia/Jerusalem
Where Condens MCP is genuinely strong
Credit where due — Condens MCP is a real research unlock if:
- You already keep research in Condens (studies, interviews, Artifacts) and want Claude / ChatGPT / Cursor / Figma Make / n8n / Copilot Studio to query published findings without exporting.
- Workspace Admin enablement + per-user OAuth matter more than React component file:line — access follows what you can already see in Condens.
- Grounding designs and code in published usability insights is the primary surface — not opening GitHub/Linear tickets from the MCP itself.
Where Feedback DevTools is more honest about create_* / ship
- Read-only published Artifacts. Condens product update (April 28, 2026) is explicit: MCP retrieves published Artifacts only — cannot create, edit, or delete anything in the workspace (lastChecked September 30, 2026 ~12:25pm Asia/Jerusalem). We quote that so buyers are not surprised.
- Tickets with file:line. create_github_issue and create_tracker_issue open GitHub/Linear tickets whose bodies carry component + file:line from capture. Condens's published MCP surface queries research Artifacts — not a Condens MCP write tool that opens tracker tickets.
- Local-agent path. The same context is handed to your coding agent; a PR, if any, is that agent's git workflow — not a Condens MCP PR tool. FDT does not claim server-side auto-open or auto-merge.
- Capture-time source maps. Every item pins the React component and file path:line so the agent starts from a known path instead of rediscovering from an Artifact ID or quote alone.
- Not the Optimal / UserTesting / Lyssna / FullStory foils. Optimal#83 is Optimal research MCP read-only + Jira via AI integrations. UserTesting#82 can create drafts and launch tests. Lyssna#81 is FAQ read-only studies. FullStory#77 is FullStory session MCP. Condens's honesty gap is read-only published Artifacts (cannot create/edit/delete) — do not reopen Optimal#83 / UserTesting#82 / Lyssna#81 / FullStory#77.
- Zero Condens in FDT today. This foil is honesty about surfaces — Feedback DevTools does not ship a Condens connector; it ships create_github_issue / create_tracker_issue + local-agent file:line.
Pricing shape (not the foil) (as of September 30, 2026)
- Condens: MCP from Business plan for Claude/ChatGPT; Enterprise for other integrations (source: condens.io/product-updates/condens-mcp-server/, April 28, 2026)
- Feedback DevTools: Free (unlimited collection) · Pro $9/mo per project (source: feedback-devtools.com/pricing)
MCP honesty is about capability claims, not sticker shock — FDT Pro is $9/mo per project vs Condens as a research suite with a read-only published-Artifacts MCP connector.
Who should pick which?
- Choose Condens MCP if your evidence archive is Condens published Artifacts and you want AI assistants to query that research read-only — without expecting the Condens MCP itself to create GitHub/Linear tickets or edit the workspace.
- Choose Feedback DevTools if you want visual feedback with file:line on capture, first-party MCP tools that create GitHub/Linear tickets (create_github_issue / create_tracker_issue), and a local-agent fix path — without reading "connect Condens to your AI" as a published Condens MCP write / ticket tool.
Frequently asked questions
What does Condens MCP say about read-only / create / edit / delete?
Per https://condens.io/product-updates/condens-mcp-server/ (April 28, 2026; lastChecked September 30, 2026 ~12:25pm Asia/Jerusalem): "The Condens MCP Server is read-only. AI tools connected through it can retrieve published Artifacts; they cannot create, edit, or delete anything in your workspace."
Can Condens MCP create GitHub issues, Linear tickets, or pull requests?
No create_github_issue / create_tracker_issue / create_pr / open_pr / codebase / git write tool on the Condens MCP surface — April 28, 2026 product update is read-only published Artifacts (lastChecked September 30, 2026 ~12:25pm Asia/Jerusalem). Feedback DevTools foils with create_github_issue / create_tracker_issue + capture-time file:line and does not claim server-side auto-open or auto-merge. Distinct from Optimal#83 / UserTesting#82 / Lyssna#81 / FullStory#77.
Is this the same foil as Optimal Workshop MCP (#83), UserTesting MCP (#82), Lyssna MCP (#81), or FullStory (#77)?
No. Optimal#83 foils Optimal research MCP read-only + Jira via AI tool integrations. UserTesting#82 foils draft+launch study creation. Lyssna#81 foils FAQ read-only studies. FullStory#77 foils FullStory session MCP. This strip foils Condens MCP read-only published Artifacts (cannot create/edit/delete) — do not reopen those.
Try Feedback DevTools free — create_github_issue / create_tracker_issue with file:line, no server-side auto-PR or Condens-style read-only Artifact query as the ticket path.