Maze MCP honesty matrix — Enterprise read-only research vs FDT create_* + resolve
Maze MCP (maze.co/platform/mcp) connects Maze research to Claude, Cursor, Copilot, ChatGPT, and other MCP clients so teams can search studies, review transcripts, and surface pain points without leaving the agent. Per Help Center Data & Privacy (help.maze.co/articles/5736723999-maze-mcp-data-privacy), Maze MCP is available on Enterprise plans only, and access is read-only: your AI app can query research, but can't create or modify anything in Maze.
The Overview (help.maze.co/articles/3603930517-maze-mcp) frames the surface as study details, transcripts, cross-study patterns, pain-point quotes, research search, and study recommendations — not tracker write or git write. Feedback DevTools is honest about a different surface: 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.
Feedback DevTools is our product. Maze MCP Enterprise + read-only claims sourced from help.maze.co/articles/5736723999-maze-mcp-data-privacy, help.maze.co/articles/3603930517-maze-mcp, and maze.co/platform/mcp — lastChecked September 23, 2026 ~2:35pm Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs Maze MCP
| Feedback DevTools | Maze MCP | |
|---|---|---|
| Positioning: Maze research MCP connector | No — FDT is capture + create_github_issue / create_tracker_issue / mark_feedback_resolved + local-agent file:line, not a Maze research-query MCP | Yes — remote Maze MCP for Claude / Cursor / Copilot / ChatGPT (maze.co/platform/mcp; help.maze.co Maze MCP Overview) |
| Published MCP surface (Enterprise read-only honesty) | get_feedback_context, list_open_feedback, list_clusters, create_github_issue, create_tracker_issue, mark_feedback_resolved… | Enterprise + read-only research query: study details, transcripts, cross-study patterns, pain points/quotes, research search, study recommendations — "can't create or modify anything in Maze"; no create_github_issue / create_tracker_issue / resolve / create_pr / open_pr / codebase / git write |
| MCP tools that open GitHub / Linear tickets | Yes — create_github_issue (#57) + create_tracker_issue Linear (#59) with component + file:line in the body | No create_github_issue / create_tracker_issue — read-only research access; AI app cannot create or modify anything in Maze |
| Resolve / mark done from MCP | Yes — mark_feedback_resolved | No — read-only; cannot create, edit, or delete anything in Maze (Data & Privacy) |
| Open GitHub PR from MCP tool | No — create_github_issue + local-agent fix path (Cursor/Claude opens a PR if you ask; not a Maze MCP PR tool) | No dedicated create_pr / open_pr / codebase / git write tool — PR would be the coding agent using Maze research context |
| Auto-open / auto-merge PRs server-side | No — we do not claim server-side auto-opened or auto-merged PRs | No — Help Center frames read-only research query; Maze MCP does not open or merge GitHub PRs |
| Plan / Enterprise gate | Free plan forever + Pro $9/mo per project — MCP tools available without an Enterprise SKU | Enterprise plans only (multi-plan teams: only Enterprise-plan team data via MCP; admin may need to enable connectors) |
| Source map on capture (component + file:line) | Yes — pinned at collect time for the local agent | Maze studies / transcripts / themes / quotes — research evidence, not React component file:line |
| Who applies the code fix | Your local Cursor / Claude agent (from MCP context or Claude Code prompt) | Your AI coding agent may use Maze research as context — Maze MCP itself does not write code, open tickets, or open PRs |
| Free plan | Yes — unlimited feedback, forever | Maze MCP requires Enterprise; no free-plan MCP connector |
| Paid entry price | $9/mo per project (Pro) | Maze Enterprise pricing (contact / public plans); MCP is an Enterprise research connector, not a separate $9 MCP SKU |
Maze MCP Enterprise + read-only verified on help.maze.co/articles/5736723999-maze-mcp-data-privacy; Overview capabilities on help.maze.co/articles/3603930517-maze-mcp; platform on maze.co/platform/mcp — lastChecked September 23, 2026 ~2:35pm Asia/Jerusalem
Where Maze MCP is genuinely strong
Credit where due — Maze MCP is a real research unlock if:
- You already run Maze studies and want Claude/Cursor/Copilot/ChatGPT to pull transcripts, quotes, and cross-study themes without exporting.
- Enterprise workspace permissions + OAuth 2.1 matter more than React component file:line source maps.
- Proactive research surfacing inside PRD drafts (maze.co/platform/mcp) is the workflow you want.
- You need a deliberately read-only research connector — no accidental create/edit/delete in Maze from the agent.
Where Feedback DevTools is different (honest foil)
- Enterprise read-only vs create_*. Data & Privacy states Maze MCP is Enterprise-only and "can't create or modify anything in Maze"; Overview capabilities are study/transcript/insight query — no create_github_issue / create_tracker_issue / resolve / create_pr / open_pr / codebase / git write (lastChecked September 23, 2026 ~2:35pm Asia/Jerusalem). We quote those pages so buyers are not surprised.
- Tickets + resolve with file:line. create_github_issue, create_tracker_issue, and mark_feedback_resolved open/resolve GitHub/Linear tickets whose bodies carry component + file:line from capture. Maze's published surface has no create_* / resolve equivalent — it queries research.
- Local-agent path, not server-side PRs. Your Cursor/Claude agent applies the fix from FDT context. We do not claim to auto-open or auto-merge PRs on a server-side clone. Distinct from Canny#72, Enterpret#71, LogRocket#70, Jam#69, Marker#68/#65, BugHerd#67.
- 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 Maze transcript alone.
- Pricing shape. Unlimited free collection; Pro is $9/mo per project. Maze MCP requires Enterprise.
Pricing, side by side (as of September 23, 2026)
- Feedback DevTools: Free plan ($0, unlimited feedback) · Pro $9/mo per project
- Maze: Enterprise required for MCP (sources: help.maze.co/articles/5736723999-maze-mcp-data-privacy; help.maze.co/articles/3603930517-maze-mcp; maze.co/platform/mcp)
MCP honesty is about capability claims, not sticker shock — FDT Pro is $9/mo per project vs Maze as a full research suite with MCP as an Enterprise read-only connector.
Who should choose what
- Choose Maze MCP if your evidence archive is Maze studies/transcripts and you want agents to query research read-only inside Claude/Cursor/Copilot/ChatGPT on an Enterprise plan.
- Choose Feedback DevTools if you want visual feedback with file:line on capture, MCP tools that create and resolve GitHub/Linear tickets, and a local-agent fix path — without reading a Maze research MCP as a create_* / resolve / create_pr tool.
- Neither MCP is a silent auto-merge bot; both expect a human review step. The honest foil is what the published docs actually allow. Distinct from Canny Ideas/Feedback CRUD, Enterpret query-only, LogRocket auto-PR marketing, Jam bug-to-fix, Marker open-PR / create-tickets, and BugHerd codebase/CMS/design.
Frequently asked questions
What does Maze MCP positioning claim?
Per maze.co/platform/mcp and help.maze.co/articles/3603930517-maze-mcp (lastChecked September 23, 2026 ~2:35pm Asia/Jerusalem): Maze MCP brings research findings into AI tools — deep-dive studies, fast summaries, proactive research surfacing, transcripts, cross-study patterns, pain points/quotes, and study recommendations — inside Claude, Cursor, Copilot, ChatGPT, and other MCP clients.
Is Maze MCP read-only? Which plan is required?
Yes — Help Center Data & Privacy (help.maze.co/articles/5736723999-maze-mcp-data-privacy) states Maze MCP is available on Enterprise plans and access is read-only: your AI app can query research, but can't create or modify anything in Maze. It also cannot access studies outside your workspace permissions or read billing/credentials. Admins may need to enable third-party connectors; auth uses OAuth 2.1.
Does Maze MCP create GitHub/Linear tickets, resolve feedback, or open pull requests?
No. Published docs describe Enterprise read-only research query — no create_github_issue / create_tracker_issue / resolve / create_pr / open_pr / codebase / git write (lastChecked September 23, 2026 ~2:35pm Asia/Jerusalem). A ticket or PR, if any, is the coding agent's workflow using Maze research context — not a Maze MCP write tool.
Does Feedback DevTools auto-open or auto-merge GitHub PRs server-side?
No. Feedback DevTools MCP creates tracker tickets (create_github_issue, create_tracker_issue for Linear), can mark_feedback_resolved, and supplies source-mapped context / Claude Code prompts so your local agent can write the fix. We do not claim to auto-open or auto-merge pull requests server-side.
How does Feedback DevTools MCP foil Maze MCP?
FDT is honest about a different surface: capture-time component + file:line, create_github_issue / create_tracker_issue / mark_feedback_resolved, and a local-agent path. Maze MCP is strong at Enterprise read-only research query (studies, transcripts, quotes). Buyers should read Data & Privacy + Overview rather than assuming create_* / resolve / create_pr. Distinct from Canny#72 / Enterpret#71 / LogRocket#70 / Jam#69 / Marker#68/#65 / BugHerd#67.
Collect source-mapped feedback and open GitHub/Linear tickets from MCP — free.