Optimal Workshop MCP honesty matrix — read-only research vs marketing that creates a Jira ticket via AI tool integrations
Optimal's Intercom release "MCP + Optimal: Ask your research data anything with Claude, ChatGPT, and more" (intercom.news/optimal-workshop/150696-…, Shared by Optimal • July 23, 2026) says you can connect ChatGPT, Claude, and Cursor to Optimal research — ask questions, explore findings across studies, analyze interviews, and generate stakeholder-ready outputs. The same page is explicit: "The Optimal MCP server currently provides read-only access to your research. AI tools can explore and analyze your studies, but they can't edit, delete, or modify your data." Access uses OAuth 2.0 and follows existing Workspace permissions.
That July 23 release also markets action via other tools: "Build AI-powered workflows using your AI tool's existing integrations, from creating Jira tickets to sharing updates in Slack." The Optimal MCP blog (optimalworkshop.com/blog/optimal-mcp, July 22, 2026) echoes it: "Use MCP along with your AI tool's existing integrations to create alerts and automate next steps e.g. … create a JIRA ticket and follow-up tasks." 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 Optimal Workshop product integration ships in FDT today.
Feedback DevTools is our product. Optimal MCP read-only claim from https://intercom.news/optimal-workshop/150696-mcp-optimal-ask-your-research-data-anything-with-claude-chatgpt-and-more (July 23, 2026); Jira/Slack workflow marketing from that release + https://www.optimalworkshop.com/blog/optimal-mcp (July 22, 2026) — lastChecked September 30, 2026 ~10:17am Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs Optimal Workshop MCP
| Feedback DevTools | Optimal Workshop MCP | |
|---|---|---|
| Positioning | Capture + create_github_issue / create_tracker_issue / mark_feedback_resolved + local-agent file:line | Research MCP — query Optimal studies/interviews/transcripts; Intercom release read-only; markets Jira/Slack via AI tool integrations |
| Published MCP write surface (read-only honesty) | create_github_issue · create_tracker_issue · mark_feedback_resolved + local-agent file:line | Read-only — "can't edit, delete, or modify your data" (Intercom July 23, 2026); no create_github_issue / create_tracker_issue / create_pr / open_pr / codebase / git write |
| Marketing claim (Jira / Slack) | N/A — FDT ships first-party create_github_issue / create_tracker_issue; does not market "AI tool integrations create a Jira ticket" as its ticket path | Intercom July 23 + blog July 22: create a Jira/JIRA ticket and Slack updates via your AI tool's existing integrations — not a first-party Optimal MCP write tool |
| 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 — Optimal MCP itself is read-only research query; a Jira ticket would be a separate AI-tool integration / agent, not an Optimal MCP tool |
| Server-side auto-open / auto-merge PRs | No — we do not claim server-side auto PRs | No — Intercom + blog frame read-only research access; Optimal MCP does not open or merge GitHub PRs |
| Source maps / file:line | Yes — capture-time React component + file:line | Studies, task results, interviews, transcripts, cross-study themes — research evidence, not React component file:line |
| Optimal in FDT today | Zero — no Optimal Workshop product integration ships in Feedback DevTools today | First-party Optimal MCP into research (Integrations on Home; included with Optimal plan) |
| Plan gate | Free plan forever + Pro $9/mo per project — MCP tools without a research-suite Enterprise SKU | Included with Optimal plan (Intercom July 23, 2026) — not a separate $9 MCP SKU |
Optimal MCP read-only verified on intercom.news/optimal-workshop/150696-mcp-optimal-ask-your-research-data-anything-with-claude-chatgpt-and-more (July 23, 2026); Jira/Slack workflow marketing verified on that release + optimalworkshop.com/blog/optimal-mcp (July 22, 2026) — lastChecked September 30, 2026 ~10:17am Asia/Jerusalem
Where Optimal Workshop MCP is genuinely strong
Credit where due — Optimal MCP is a real research unlock if:
- You already run Optimal studies (tree testing, card sorts, usability testing, surveys, interviews) and want Claude / ChatGPT / Cursor to query studies, transcripts, quotes, and cross-study themes without exporting.
- Workspace OAuth permissions matter more than React component file:line — access follows what you can already see in Optimal.
- Executive summaries, dashboards, and stakeholder-ready deliverables grounded in Optimal research are the primary surface.
Where Feedback DevTools is more honest about create_* / ship
- Marketing vs read-only. Intercom release (July 23, 2026) markets creating Jira tickets / Slack updates via AI tool integrations; the same page is explicit that Optimal MCP is read-only and cannot edit, delete, or modify research data (lastChecked September 30, 2026 ~10:17am Asia/Jerusalem). Blog (July 22, 2026) markets "create a JIRA ticket and follow-up tasks" the same way. We quote both 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. Optimal's published MCP surface queries research evidence — a Jira ticket, if any, is a separate AI-tool integration / agent using Optimal context, not an Optimal MCP write tool.
- Local-agent path. The same context is handed to your coding agent; a PR, if any, is that agent's git workflow — not an Optimal 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 a study ID or quote alone.
- Not the Lyssna / UserTesting foils. Lyssna#81 is also read-only studies (cannot create/edit). UserTesting#82 can create drafts and launch tests. Optimal's honesty gap is the same family as Lyssna (read-only + ticket-via-other-integrations marketing) with Jira/Slack wording instead of Linear — do not reopen UserTesting#82 / Lyssna#81 / Dovetail#78 / FullStory#77 / Intercom#76 / Sprig#75 / Maze#73.
- Zero Optimal in FDT today. This foil is honesty about surfaces — Feedback DevTools does not ship an Optimal Workshop connector; it ships create_github_issue / create_tracker_issue + local-agent file:line.
Pricing shape (not the foil) (as of September 30, 2026)
- Optimal Workshop: MCP included with Optimal plan (sources: intercom.news/optimal-workshop/150696-mcp-optimal-ask-your-research-data-anything-with-claude-chatgpt-and-more; optimalworkshop.com/blog/optimal-mcp)
- 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 Optimal as a research suite with a read-only MCP connector (Jira/Slack via AI tool integrations, not first-party create_github_issue).
Who should pick which?
- Choose Optimal Workshop MCP if your evidence archive is Optimal studies/interviews/transcripts and you want AI assistants to query that research read-only — then optionally use your AI tool's other integrations (Jira, Slack) yourself for tickets.
- 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 a Jira ticket" AI-integration marketing as a published Optimal MCP write tool.
Frequently asked questions
What does Optimal MCP say about read-only / edit / delete?
Per https://intercom.news/optimal-workshop/150696-mcp-optimal-ask-your-research-data-anything-with-claude-chatgpt-and-more (Shared by Optimal • July 23, 2026; lastChecked September 30, 2026 ~10:17am Asia/Jerusalem): "The Optimal MCP server currently provides read-only access to your research. AI tools can explore and analyze your studies, but they can't edit, delete, or modify your data."
What does Optimal market about Jira / Slack tickets?
Intercom July 23, 2026: "Build AI-powered workflows using your AI tool's existing integrations, from creating Jira tickets to sharing updates in Slack." Blog https://www.optimalworkshop.com/blog/optimal-mcp (July 22, 2026): "Use MCP along with your AI tool's existing integrations to create alerts and automate next steps e.g. … create a JIRA ticket and follow-up tasks." That is AI-tool integration chaining — not a first-party Optimal MCP create_github_issue / create_pr tool.
Can Optimal MCP create GitHub issues, Jira tickets, or pull requests?
No create_github_issue / create_tracker_issue / create_pr / open_pr / codebase / git write tool on the Optimal MCP surface — Intercom July 23, 2026 is read-only (lastChecked September 30, 2026 ~10:17am Asia/Jerusalem). A Jira ticket or GitHub PR, if any, is a separate AI-tool integration / coding agent using Optimal context — not Optimal MCP itself. 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 UserTesting#82 / Lyssna#81 / Dovetail#78 / FullStory#77 / Intercom#76 / Sprig#75 / Maze#73.
Try Feedback DevTools free — create_github_issue / create_tracker_issue with file:line, no server-side auto-PR or "AI tool integrations create a Jira ticket" as the ticket path.