Sprig MCP honesty matrix — Linear tip vs published tools (no create_issue / create_pr)
Sprig MCP (docs.sprig.com/docs/native-ai/sprig-mcp) connects Sprig studies, responses, and themes to Claude, ChatGPT, Cursor, Gemini, Copilot, and Linear. The Linear setup tip says: "Close the loop between user feedback and product decisions. Create Linear issues directly from Sprig response themes."
Published tools are get_surveys, get_responses, get_response_themes, plus draft-study creation ("No study can be launched from the AI client" — launch only via Sprig UI). There is no create_issue / create_pr / create_github_issue / open_pr / codebase / git write tool. Feedback DevTools is honest about a different surface: create_github_issue / create_tracker_issue 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. Sprig MCP tools + Linear tip sourced from docs.sprig.com/docs/native-ai/sprig-mcp (+ create-surveys-with-mcp draft-only) — lastChecked September 28, 2026 ~4:40pm Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs Sprig MCP
| Feedback DevTools | Sprig MCP | |
|---|---|---|
| Positioning | Capture + create_github_issue / create_tracker_issue / mark_feedback_resolved + local-agent file:line | Sprig research MCP connector (studies / responses / themes) for Claude / ChatGPT / Cursor / Gemini / Copilot / Linear |
| Published MCP tools | create_github_issue · create_tracker_issue · mark_feedback_resolved + local-agent file:line | get_surveys · get_responses · get_response_themes + draft study only ("No study can be launched from the AI client"); no create_issue / create_pr / create_github_issue |
| Linear / tracker write from themes | Yes — create_github_issue / create_tracker_issue open GitHub/Linear tickets with component + file:line | Linear tip markets "Create Linear issues directly from Sprig response themes" — no create_issue tool on the published list; a ticket, if any, is the coding agent / Linear assistant using Sprig theme context |
| Create / launch studies from AI client | N/A — FDT is feedback capture, not a survey platform | Draft study only — "No study can be launched from the AI client"; launch via Sprig UI |
| create_pr / open_pr / codebase / git write | No — create_github_issue + local-agent fix path (Cursor/Claude opens a PR if you ask; not a Sprig MCP PR tool) | No dedicated create_pr / open_pr / codebase / git write tool |
| Server-side auto-open / auto-merge PRs | No — we do not claim server-side auto PRs | No — published tools do not open or merge GitHub PRs |
| Source maps / file:line | Yes — capture-time React component + file:line | Sprig themes / responses / quotes — research evidence, not React component file:line |
| Pricing shape | Unlimited free collection; Pro $9/mo per project | Sprig research suite pricing; MCP is a connector, not a separate $9 MCP SKU |
Sprig MCP published tools + Linear tip verified on docs.sprig.com/docs/native-ai/sprig-mcp; draft-only study create on docs.sprig.com/docs/native-ai/create-surveys-with-mcp — lastChecked September 28, 2026 ~4:40pm Asia/Jerusalem
Where Sprig MCP is genuinely strong
Credit where due — Sprig MCP is a real research unlock if:
- You already run Sprig studies and want Claude/ChatGPT/Cursor/Linear to pull surveys, responses, and AI themes with source quotes.
- Drafting a study inside the AI client (then launching from the Sprig UI) fits your research workflow.
- You want themes and quotes as live context inside the same agent chat where roadmap decisions happen.
Where Feedback DevTools is more honest about create_*
- Linear tip vs published tools. docs.sprig.com Linear tip says "Create Linear issues directly from Sprig response themes"; published tools are get_surveys · get_responses · get_response_themes + draft study only — no create_issue / create_pr / create_github_issue (lastChecked September 28, 2026 ~4:40pm Asia/Jerusalem). 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. Sprig's published surface has no create_issue / create_github_issue equivalent — it retrieves themes.
- Local-agent path. The same context is handed to your coding agent; a PR, if any, is that agent's git workflow — not a Sprig 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 Sprig theme alone.
- Pricing shape. Unlimited free collection; Pro is $9/mo per project.
Pricing shape (not the foil) (as of September 28, 2026)
- Sprig: research suite pricing; MCP connector on docs.sprig.com/docs/native-ai/sprig-mcp
- Feedback DevTools: Free (unlimited collection) · Pro $9/mo per project
MCP honesty is about capability claims, not sticker shock — FDT Pro is $9/mo per project vs Sprig as a full research suite with MCP as a connector.
Who should pick which?
- Choose Sprig MCP if your evidence archive is Sprig studies/responses/themes and you want agents to query research (and draft studies) inside Claude/ChatGPT/Cursor/Linear.
- Choose Feedback DevTools if you want visual feedback with file:line on capture, MCP tools that create GitHub/Linear tickets (create_github_issue / create_tracker_issue), and a local-agent fix path — without reading a Sprig Linear tip as a create_issue / create_pr tool.
Frequently asked questions
What does the Sprig MCP Linear tip claim?
Per docs.sprig.com/docs/native-ai/sprig-mcp (lastChecked September 28, 2026 ~4:40pm Asia/Jerusalem): after connecting Sprig in Linear → Settings → Integrations → MCP, the tip says "Close the loop between user feedback and product decisions. Create Linear issues directly from Sprig response themes."
Which tools does Sprig MCP publish?
get_surveys (study configurations, up to 1000), get_responses (up to 1000 responses), get_response_themes (themes with associated responses), plus draft-study creation. "No study can be launched from the AI client" — launching studies can only be done via the Sprig UI (docs.sprig.com/docs/native-ai/sprig-mcp; create-surveys-with-mcp).
Does Sprig MCP create Linear/GitHub issues or open pull requests?
No create_issue / create_pr / create_github_issue / open_pr / codebase / git write tool is on the published list (lastChecked September 28, 2026 ~4:40pm Asia/Jerusalem). A Linear issue or PR, if any, is the coding agent / Linear assistant using Sprig theme context — not a Sprig MCP write tool. Feedback DevTools foils with create_github_issue / create_tracker_issue + local-agent path and does not claim server-side auto-open or auto-merge.
Try Feedback DevTools free — create_github_issue / create_tracker_issue with file:line, no server-side auto-PR claims.