Great Question MCP honesty matrix — create_*_study / candidates R/W vs FDT create_github_issue / file:line
Great Question's MCP support docs (greatquestion.co/support/integrations/mcp) give AI assistants read and write access to studies, transcripts, highlights, and participants. The "What's available" page (greatquestion.co/support/integrations/mcp-available-tools) publishes the tool surface: candidates (create_candidate, update_candidate, delete_candidate, get/list/search), interview studies (create_interview_study, update/delete/get/list/search), survey studies (create_survey_study, …), and unmoderated studies (create_unmoderated_study, …) plus screeners, blocks, scheduling, recruitment, sessions/transcripts, responses, and synthesis (highlights, insights, reels).
That is a real research write surface inside Great Question — study CRUD and candidate R/W — and it is not a ship-to-code surface. Nothing on those support pages publishes create_github_issue, create_pr, open_pr, a codebase/git write, or React component file:line. Feedback DevTools foils with first-party create_github_issue / create_tracker_issue / mark_feedback_resolved plus capture-time source maps (component + file:line) in the ticket body, handed to your local agent. We do not claim server-side auto-opened or auto-merged PRs. Zero Great Question product integration ships in FDT today. Distinct from Condens#84 (read-only published Artifacts) and UserTesting#82 (create/launch studies) — do not reopen Condens#84 / Optimal#83 / UserTesting#82 / Lyssna#81 / FullStory#77.
Feedback DevTools is our product. Great Question MCP from https://greatquestion.co/support/integrations/mcp and tool catalog from https://greatquestion.co/support/integrations/mcp-available-tools (create_interview_study / create_survey_study / create_unmoderated_study + candidates R/W; no create_github_issue / create_pr / file:line) — lastChecked September 30, 2026 ~14:20pm Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs Great Question MCP
| Feedback DevTools | Great Question MCP | |
|---|---|---|
| Positioning | Capture + create_github_issue / create_tracker_issue / mark_feedback_resolved + local-agent file:line | Research MCP — create/update/delete interview, survey, and unmoderated studies; candidates R/W; screeners/blocks/scheduling/recruitment |
| Published MCP write surface | create_github_issue · create_tracker_issue · mark_feedback_resolved + local-agent file:line | create_interview_study · create_survey_study · create_unmoderated_study · create_candidate / update_candidate / delete_candidate (+ screeners, blocks, moderators, study messages) — research writes inside Great Question, not GitHub |
| Study create tools (named) | N/A — FDT does not market interview/survey/unmoderated study creation | mcp-available-tools: create_interview_study, create_survey_study, create_unmoderated_study (plus update/delete/get/list/search per type) |
| 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 create_github_issue / create_tracker_issue / create_pr / open_pr / codebase / git write on the Great Question MCP surface |
| Server-side auto-open / auto-merge PRs | No — we do not claim server-side auto PRs | No — published tools create and manage Great Question studies/candidates; they do not open or merge GitHub PRs |
| Source maps / file:line | Yes — capture-time React component + file:line in ticket body | Studies, candidates, sessions, transcripts, highlights, insights — research evidence, not React component file:line |
| Great Question in FDT today | Zero — no Great Question product integration ships in Feedback DevTools today | First-party Great Question MCP (OAuth 2.1 PKCE / agent API token) into studies + candidates |
| Plan gate | Free plan forever + Pro $9/mo per project — MCP ticket tools without a research-suite Enterprise SKU | Great Question research suite MCP — not a published $9 MCP SKU (sources: support integrations/mcp pages) |
Great Question MCP study CRUD + candidates R/W verified on greatquestion.co/support/integrations/mcp and greatquestion.co/support/integrations/mcp-available-tools — lastChecked September 30, 2026 ~14:20pm Asia/Jerusalem
Where Great Question MCP is genuinely strong
Credit where due — Great Question MCP is a real research unlock if:
- You already run Great Question and want Claude, ChatGPT, Cursor, or Copilot to create interview / survey / unmoderated studies (create_interview_study, create_survey_study, create_unmoderated_study) and manage candidates without leaving the AI client.
- Candidate R/W (create_candidate / update_candidate / delete_candidate), screeners, unmoderated blocks, scheduling, and recruitment shortlists matter more than React component file:line.
- Sessions, transcripts, highlights, insights, and reels as the analysis/synthesis surface inside the assistant is the job — not opening GitHub/Linear tickets from the MCP itself.
Where Feedback DevTools is more honest about create_* / ship
- create_*_study is real — and it is not ship-to-code. Support docs (greatquestion.co/support/integrations/mcp + mcp-available-tools) publish create_interview_study / create_survey_study / create_unmoderated_study and candidates R/W (lastChecked September 30, 2026 ~14:20pm Asia/Jerusalem). Neither page publishes create_github_issue, create_pr, or file:line.
- Tickets with file:line. create_github_issue and create_tracker_issue open GitHub/Linear tickets whose bodies carry component + file:line from capture. Great Question's published MCP surface writes studies and candidates — a GitHub issue or PR, if any, is a separate coding agent, not a Great Question MCP tool.
- Local-agent path. The same source map is handed to your coding agent; a PR, if any, is that agent's git workflow. 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 a study ID or transcript quote alone.
- Not the Condens / UserTesting foils. Condens#84 is read-only published Artifacts (cannot create/edit/delete). UserTesting#82 create/launch studies on the UserTesting surface. Great Question's honesty gap is study CRUD + candidates R/W without create_github_issue / create_pr / file:line — do not reopen Condens#84 / Optimal#83 / UserTesting#82 / Lyssna#81 / FullStory#77.
- Zero Great Question in FDT today. This foil is honesty about surfaces — Feedback DevTools does not ship a Great Question connector; it ships create_github_issue / create_tracker_issue + local-agent file:line.
Pricing shape (not the foil) (as of September 30, 2026)
- Great Question: research suite MCP (create_*_study + candidates R/W); not a published $9 MCP SKU (sources: greatquestion.co/support/integrations/mcp; greatquestion.co/support/integrations/mcp-available-tools)
- 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 Great Question as a research suite whose MCP creates studies and manages candidates but does not publish create_github_issue / create_pr / file:line.
Who should pick which?
- Choose Great Question MCP if your job is creating interview / survey / unmoderated studies and managing candidates from Claude, ChatGPT, Cursor, or Copilot, then reading sessions/transcripts/insights back in that client.
- 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 create_*_study as a GitHub write or a source map.
Frequently asked questions
What create_*_study tools does Great Question MCP publish?
Per https://greatquestion.co/support/integrations/mcp-available-tools (lastChecked September 30, 2026 ~14:20pm Asia/Jerusalem): create_interview_study, create_survey_study, and create_unmoderated_study (plus update/delete/get/list/search per type). Candidates: create_candidate, update_candidate, delete_candidate, get/list/search. Overview: https://greatquestion.co/support/integrations/mcp. No invent beyond those named tools.
Can Great Question MCP create GitHub issues or pull requests?
No create_github_issue / create_tracker_issue / create_pr / open_pr / codebase / git write / file:line on the Great Question MCP surface (greatquestion.co/support/integrations/mcp + mcp-available-tools; lastChecked September 30, 2026 ~14:20pm Asia/Jerusalem). Writes are Great Question studies and candidates. Feedback DevTools foils with create_github_issue / create_tracker_issue + source-mapped body and does not claim server-side auto-open or auto-merge. Distinct from Condens#84 / Optimal#83 / UserTesting#82 / Lyssna#81 / FullStory#77.
Is this the same foil as Condens MCP (#84) or UserTesting MCP (#82)?
No. Condens#84 is read-only published Artifacts (cannot create/edit/delete). UserTesting#82 foils UserTesting draft+launch. This strip foils Great Question create_interview_study / create_survey_study / create_unmoderated_study + candidates R/W — still no create_github_issue / create_pr / file:line. Do not reopen Condens#84 / Optimal#83 / UserTesting#82 / Lyssna#81 / FullStory#77.
Try Feedback DevTools free — create_github_issue / create_tracker_issue with file:line, not a research-suite create_*_study launcher.