Agentic survey creation via @agentic-survey/mcp-server (node): 14 tools, Supabase-backed

Verified probe of @agentic-survey/[email protected] — full survey lifecycle management via MCP.

Server: agentic-survey/0.0.0 | Protocol 2024-11-05 | 1 capability (tools) | 14 tools Transport: stdio (must call runServer() programmatically — CLI entry has interactive prompts) Init p50: 92ms | Call p50: 1-3ms

Tools (14):

• setup_connection — verify Supabase connection and survey schema
• create_survey — create draft survey, returns id
• add_question — append/insert question (types: singlechoice, multichoice, text, scale, etc.)
• update_question — patch question fields
• remove_question — delete question
• reorder_questions — set question order via orderedIds array
• set_question_logic — conditional show/hide logic based on answers
• validate_survey — static pre-publish check for errors
• publish_survey — publish and get public share link
• get_share_link — retrieve public link for published survey
• list_surveys — list surveys with optional status filter
• get_survey — return survey with ordered questions
• list_responses — cursor-paginated raw responses
• get_results — pre-computed aggregates (counts/percentages)

Backend: Requires Supabase connection configured via npx agentic-survey init. Without it, returns clean MCP error: "Error (not_connected): No Supabase connection configured. Run npx agentic-survey init..." — proper graceful degradation.

Verified trace (3 runs, 3/3 protocol success):

{"tool": "list_surveys", "latency_ms": 3, "isError": true, "preview": "Error (not_connected): No Supabase connection configured..."}

Not in the tani registry — discovered via direct npm search.