create_changelog_entry
ChatGPTCreate a changelog entry on the project's public board changelog. 'title' is required; 'body' is Markdown. Optional 'version' (e.g. v1.4.0), 'category' (one of: added, improved, fixed, changed, removed, security), and 'component' (a slug from the project's component registry naming the product asset the entry belongs to, e.g. 'cli' or 'react-sdk' — keep 'version' a pure version and use 'component' for the asset instead of encoding it into the version string; an unknown slug errors listing the valid ones). By default the entry lands as a draft for review; set 'publish' to true to publish it to the public board immediately (published entries are included in the changelog email digest to subscribers). Optional 'published_at' (RFC 3339 or YYYY-MM-DD) backdates the display date — use it when importing existing changelog history. Returns the created entry.
create_feedback
ChatGPTCreate a new feedback item. Requires message (non-empty). Optional: type (Bug/Feature/Praise/Question/Improvement/Other), path, version, submitted_by.
create_rating
ChatGPTCreate a new helpful rating (thumbs up/down). Requires value (true=helpful, false=not helpful). Optional: path, version, submitted_by. For star or NPS ratings, use create_typed_rating.
create_survey
ChatGPTCreate a new survey from a canonical template. The 'template' must be one of: blank (empty starter), nps (Net Promoter Score), csat (customer satisfaction, 1-5), ces (customer effort, 1-7). The survey is created in 'draft' status — use set_survey_status to make it 'live'. Edit questions and triggers in the dashboard. Projects are capped at 10 non-archived surveys.
create_typed_rating
ChatGPTCreate a typed rating. Supports three rating types: - helpful: value is 1 (helpful) or 0 (not helpful) - star: value is 1-5 (or 1-max_stars if specified) - nps: value is 0-10 (Net Promoter Score) Required: project_id, rating_type, value. Optional: max_stars (for star type), path, version, submitted_by.
delete_feedback
ChatGPTDelete a feedback item. This performs a soft-delete (archive) - the item is not permanently removed.
delete_rating
ChatGPTDelete a rating item. This performs a soft-delete (archive) - the item is not permanently removed.
get_feedback
ChatGPTGet a single feedback item by its ID. Returns full feedback details including message, status, type, source, and metadata.
get_idea
ChatGPTGet a single idea (feature request) by its ID with full detail: title, description, status, votes (total and verified), comments count, public admin_response, completed_in_version, merged_into_id (set when the idea is a Duplicate), tag IDs, and the linked GitHub issue if any.
get_rating
ChatGPTGet a single rating item by its ID. Returns full rating details including value, path, version, and metadata.
get_rating_stats
ChatGPTGet aggregated helpful rating statistics for a project. Returns total count, helpful count, not helpful count, and percentage. Optionally filter by path. For star or NPS stats, use get_typed_rating_stats.
get_survey
ChatGPTGet a single survey by its ID, including the full definition: questions, trigger, thank-you action, status, and display mode.
get_survey_stats
ChatGPTGet aggregated response statistics for a survey, broken down per question (counts, averages, distributions, NPS bands where applicable).
get_typed_rating_stats
ChatGPTGet aggregated statistics for any rating type. Response varies by type: - helpful: total, helpful, not_helpful, percentage - star: total, average, distribution (counts per star value) - nps: total, score (-100 to 100), promoters, passives, detractors, distribution Required: project_id. Optional: rating_type (defaults to helpful), path.
list_changelog
ChatGPTList all changelog entries for a project (every status: draft, published, hidden), newest first. Each entry has a source (manual, github_release, completed_idea), title, Markdown body, optional version, category, and component (a slug naming the product asset, e.g. 'cli'), and lifecycle status. Optional 'component' narrows to one component slug. Call this before creating an entry to avoid duplicates.
list_feedback
ChatGPTList feedback items for a project. Supports pagination (page, limit) and filtering by status (New/Active/Assigned/Hold/Closed/Resolved), type (Bug/Feature/Praise/Question/Improvement/Other), and search term.
list_ideas
ChatGPTList ideas (feature requests) for a project. Returns compact rows: id, title, status, votes_count, comments_count, completed_in_version, created_at, plus pagination. Optional 'status' filter (Pending, Open, Planned, Started, Completed, Declined, Duplicate, Rejected; omit for all), 'sort' ('votes' = most voted first, 'newest' = default), 'search' (title/description), 'page', 'limit' (1-100, default 20). The public roadmap is the Planned, Started and Completed ideas. Use get_idea for the description, admin response and linked GitHub issue.
list_projects
ChatGPTList all projects for your organization. Returns project details including name, description, allowed origins, and feedback count.
list_ratings
ChatGPTList ratings (thumbs up/down) for a project. Supports pagination (page, limit) and filtering by path and value (true=helpful, false=not helpful).
list_surveys
ChatGPTList all surveys for a project. Returns each survey's full definition (questions, trigger, status, display mode) plus its response count. Survey statuses: draft, live, paused, archived.
merge_ideas
ChatGPTMerge a duplicate idea ('source_id') into the canonical idea to keep ('target_id'), both in the same project. Votes move to the target (a voter who backed both counts once), comments move with them, and the source becomes status Duplicate with merged_into_id pointing at the target; it stays visible on the public board as a merged duplicate. Cannot be undone through the API. The source must not already be a Duplicate, and the target must not itself be merged away. To merge several duplicates, call once per duplicate. Returns votes_migrated, votes_deduplicated and comments_migrated.
report_problem
ChatGPTReport a bug, docs mismatch, friction or missing feature you hit while using this MCP server or the SeggWat API. The report goes to the SeggWat team, not to your projects. One report per distinct problem; keep working after filing. 'category' must be one of: bug, docs_mismatch, friction, feature_gap, quality_degradation, other. 'surface' is the MCP tool name or API path you were using.
set_changelog_status
ChatGPTChange a changelog entry's lifecycle status. 'status' must be one of: draft, published, hidden. 'published' puts the entry live on the public board changelog — this is the review gate for drafts from GitHub-release sync and completed ideas. 'draft' unpublishes; 'hidden' soft-hides without deleting. Publishing also makes the entry eligible for the subscriber email digest, and the first publish of an entry created from feedback emails the original submitter. Returns the updated entry.
set_survey_status
ChatGPTChange a survey's lifecycle status. The 'status' must be one of: draft, live, paused, archived. Setting a survey to 'live' is what makes it fire from the widget. Returns the updated survey.
update_changelog_entry
ChatGPTUpdate a changelog entry's content: title, Markdown body, version, category, component. Only the fields you pass change; omitted fields keep their current value (pass an empty string to clear 'version', 'category', or 'component'). Works on any entry regardless of status — use it to polish synced GitHub-release or completed-idea drafts before publishing. Returns the updated entry.
update_feedback
ChatGPTUpdate a feedback item. At least one field must be provided: message, type (Bug/Feature/Praise/Question/Improvement/Other), status (New/Active/Assigned/Hold/Closed/Resolved), or resolution_note. Setting status to Resolved emails the feedback submitter (when they left an email and the project has resolution emails enabled); a resolution_note is included in that email.
update_idea
ChatGPTUpdate an idea (feature request). Provide at least one of: 'status' (Pending, Open, Planned, Started, Completed, Declined, Rejected — use merge_ideas for duplicates), 'completed_in_version' (e.g. v1.3.0; "" clears), 'admin_response' (public team reply shown on the board), 'title', 'description'. Omitted fields keep their value. Status changes are visible on the public board immediately: Planned/Started/Completed ideas form the public roadmap, Pending and Rejected are hidden. No emails are sent. The first time an idea moves to Completed, SeggWat auto-creates a DRAFT changelog entry for it (source completed_idea, once per idea — re-completing never duplicates it): title = idea title, body = admin_response if set, else the description, version = completed_in_version, component taken from an idea tag whose slug matches a changelog component. The draft is built from the values at that moment, so pass completed_in_version and admin_response in the same call as status Completed. The draft is never published automatically: review it with list_changelog / update_changelog_entry and publish with set_changelog_status. Returns the updated idea.
verify_setup
ChatGPTHas this project received its first submission from a widget yet? waiting with a hint until it has, then receiving with the time of the first one.
create_changelog_entry
Claudecreate_feedback
Claudecreate_rating
Claudecreate_survey
Claudecreate_typed_rating
Claudedelete_feedback
Claudedelete_rating
Claudeget_feedback
Claudeget_idea
Claudeget_rating
Claudeget_rating_stats
Claudeget_survey
Claudeget_survey_stats
Claudeget_typed_rating_stats
Claudelist_changelog
Claudelist_feedback
Claudelist_ideas
Claudelist_projects
Claudelist_ratings
Claudelist_surveys
Claudemerge_ideas
Claudereport_problem
Claudeset_changelog_status
Claudeset_survey_status
Claudesetup_project
Claudeupdate_changelog_entry
Claudeupdate_feedback
Claudeupdate_idea
Claudeverify_setup
Claude