Feedback review for Andrew Harrison (StableKernel)

Andrew, thank you for the thoughtful and detailed feedback over the past few weeks. You've sent us some of the most specific, well-formed reports any customer has — the kind that we can fix without back-and-forth — and several of them have directly shaped what's shipping. Quick rundown of where things stand.

What you've told us

Four substantive themes, plus a few NPS responses (mostly 7/10):

1. MCP installer missed Claude Code. When you installed, it configured Claude Desktop's claude_desktop_config.json but didn't write to Claude Code's .mcp.json. You worked around it by creating the file manually.
2. "Feedback" is overloaded. Two different things share the word: customer feedback (about your product) and product feedback (about Simple Product). Both surface in the same dashboard, which makes the boundary fuzzy.
3. MCP card tools lack details. list_cards and search_cards return only titles + stages — no descriptions. You also noted there was no get_card tool to fetch full details.
4. Card ordering inconsistency. Order returned by MCP doesn't match the order on the board UI. You use the UI ordering as a priority signal and want Claude to respect it.

What's already addressed

Issue 3 (MCP card details) — get_card shipped. A get_card tool now exists in MCP and returns full card content including the description. So "fetch the full text of one card" is now possible end-to-end. list_cards / search_cards still return summaries — we kept that deliberately so listings stay light — but if you'd rather they included description by default, that's a small adjustment. Happy to flip it.

Issue 1 (MCP installer for Claude Code) — should now work. The installer was rebuilt to detect Claude Code, Claude Desktop, Cursor, Windsurf, and VS Code, writing config to each of them in one auth step. Re-running npx @simple-product/mcp@latest --install should configure all of them at once. If it's still missing Claude Code's .mcp.json, that's a real bug we'd want to see — happy to dig in.

There's also a bigger architectural shift you may not have noticed: the MCP runtime is now a thin bridge to a hosted endpoint. New tools and tool description fixes ship server-side — when we improve the MCP surface, your bridge picks up the new tools the next time it connects, with no reinstall. So issues you've raised about MCP tools tend to fix themselves the next time you connect.

What's coming soon

Honest answer: nothing in flight today specifically targets your remaining themes (2 and 4). The recent MCP work has been broadening the surface (new tools, hosted runtime) rather than refining the existing tools.

That said, both of your remaining themes are actively in our heads and will surface in the next round of MCP polish.

What we're not building yet

Issue 2 (feedback terminology). This is a genuine gap and we don't have a fix in flight. The two meanings of "feedback" are real and confusing — something a customer left for you, vs. something you left for us. The likely future direction is either renaming "product feedback" to something less collision-y (issues? signals? requests?) or splitting the dashboard surface so the two streams sit in different places. We'd love your input on which framing would feel most natural to you.

Issue 4 (card ordering in MCP). Also not in flight. The wrinkle is that the UI ordering is a per-stage drag position, and MCP currently returns cards by creation order. Honoring drag position would mean exposing position as a sortable field on the MCP responses — doable, just hasn't been done. If this would meaningfully improve how you and Claude work together day-to-day, that's strong signal to prioritize it.

NPS

You've left us a few 7/10 (passive) NPS responses and one 6/10. We hear you. The hope is that as we close the gaps above — particularly the MCP polish — those scores creep upward. We're paying attention.

Wrapping up

If either of the unaddressed items (terminology or ordering) is blocking real workflow for you and Stable Kernel, we'd love to learn more about how you're using SP-via-Claude day-to-day. That context would help us decide what to prioritize next. Reply with a few times that work and we'll find a slot.

Genuinely grateful for the bug reports and the consistency of your feedback — early-stage product work is more fun when customers care enough to write things this thorough.

— Andy