MCP Reference

Quackback's MCP server exposes 39 tools and 6 resources. Tools perform actions (search, create, update, delete). Resources provide lookup data (boards, statuses, tags) that tools reference by ID.

Tools

search

Search feedback posts or changelog entries. Returns paginated results with a cursor for the next page.

Scope: read:feedback for posts and changelogs. read:article + team role for articles (also requires help center to be enabled).

search({ query: "dark mode", sort: "votes", limit: 10 })
search({ entity: "changelogs", status: "published" })
search({ entity: "articles", query: "getting started", status: "published" })
search({ boardId: "board_01abc...", status: "open" })
search({ dateFrom: "2026-01-01", dateTo: "2026-02-01" })
search({ showDeleted: true })

get_details

Get full details for any entity by TypeID. The entity type is auto-detected from the ID prefix. No need to specify whether it's a post or changelog.

Scope: read:feedback for posts and changelogs. read:article + team role for kb_article_*/kb_category_* (also requires help center to be enabled).

Returns all fields including comments (for posts), linked posts (for changelogs), tags, official response, and timestamps. Also supports kb_article_* and kb_category_* IDs.

get_details({ id: "post_01abc..." })
get_details({ id: "changelog_01xyz..." })
get_details({ id: "kb_article_01abc..." })
get_details({ id: "kb_category_01abc..." })

triage_post

Update a post's status, tags, or owner. All fields except postId are optional. Only provided fields are updated.

Scope: write:feedback + team role (admin or member)

triage_post({ postId: "post_01abc...", statusId: "status_01xyz..." })
triage_post({ postId: "post_01abc...", ownerPrincipalId: "principal_01xyz..." })
triage_post({ postId: "post_01abc...", tagIds: ["tag_01a...", "tag_01b..."] })

vote_post

Toggle a vote on a feedback post. Call once to vote, call again to unvote.

Scope: write:feedback

Returns the current vote state and total vote count.

vote_post({ postId: "post_01abc..." })

proxy_vote

Add or remove a vote on behalf of another user. Use this to record votes from external channels (support tickets, Slack messages, sales calls) with source attribution for traceability.

Scope: write:feedback + team role (admin or member)

Adding a vote is idempotent: calling it twice for the same user has no effect. Removing a vote works for any vote type (proxy, integration, or direct).

proxy_vote({ postId: "post_01abc...", voterPrincipalId: "principal_01xyz..." })
proxy_vote({
  postId: "post_01abc...",
  voterPrincipalId: "principal_01xyz...",
  sourceType: "zendesk",
  sourceExternalUrl: "https://support.example.com/tickets/1234"
})
proxy_vote({ action: "remove", postId: "post_01abc...", voterPrincipalId: "principal_01xyz..." })

add_comment

Post a comment on a feedback post. Supports threaded replies via parentId.

Scope: write:feedback

add_comment({ postId: "post_01abc...", content: "Thanks for the feedback!" })
add_comment({
  postId: "post_01abc...",
  content: "Good point.",
  parentId: "comment_01xyz..."
})

update_comment

Edit a comment's content. Team members can edit any comment. Authors can edit their own.

Scope: write:feedback

update_comment({ commentId: "comment_01abc...", content: "Updated response." })

delete_comment

Hard-delete a comment and all its replies. This cannot be undone. Authors can delete their own comments. Team members can delete any comment.

Scope: write:feedback

Warning:
Deleting a comment also deletes all replies. This action is permanent.

delete_comment({ commentId: "comment_01abc..." })

react_to_comment

Add or remove an emoji reaction on a comment.

Scope: write:feedback

react_to_comment({ action: "add", commentId: "comment_01abc...", emoji: "👍" })
react_to_comment({ action: "remove", commentId: "comment_01abc...", emoji: "👍" })

create_post

Submit new feedback on a board. Requires a board ID and title. Content, status, and tags are optional.

Scope: write:feedback

Tip:
Use the quackback://boards resource to look up board IDs before calling create_post.

create_post({ boardId: "board_01abc...", title: "Add dark mode" })
create_post({
  boardId: "board_01abc...",
  title: "Add dark mode",
  content: "Would love a dark theme option.",
  statusId: "status_01xyz...",
  tagIds: ["tag_01a..."]
})

delete_post

Soft-delete a feedback post. The post is hidden from public views but can be restored within 30 days.

Scope: write:feedback + team role (admin or member)

delete_post({ postId: "post_01abc..." })

restore_post

Restore a soft-deleted post. Posts can only be restored within 30 days of deletion.

Scope: write:feedback + team role (admin or member)

restore_post({ postId: "post_01abc..." })

merge_post

Merge a duplicate post into a canonical post. Votes are combined. Reversible via unmerge_post.

Scope: write:feedback + team role (admin or member)

Tip:
Use search to find potential duplicates first, then merge them to consolidate votes.

merge_post({
  duplicatePostId: "post_01abc...",
  canonicalPostId: "post_01xyz..."
})

unmerge_post

Restore a merged post to independent state. Recalculates vote counts for both posts.

Scope: write:feedback + team role (admin or member)

unmerge_post({ postId: "post_01abc..." })

create_changelog

Create a changelog entry. Saves as a draft by default. Set publish: true to publish immediately.

Scope: write:changelog + team role (admin or member)

create_changelog({ title: "v2.1 Release", content: "## New features\n- Dark mode..." })
create_changelog({ title: "v2.1 Release", content: "...", publish: true })

update_changelog

Update an existing changelog entry's title, content, publish state, or linked posts.

Scope: write:changelog + team role (admin or member)

update_changelog({ changelogId: "changelog_01abc...", title: "v2.1.1 Patch" })
update_changelog({
  changelogId: "changelog_01abc...",
  publish: true,
  linkedPostIds: ["post_01a...", "post_01b..."]
})

delete_changelog

Soft-delete a changelog entry.

Scope: write:changelog + team role (admin or member)

delete_changelog({ changelogId: "changelog_01abc..." })

list_suggestions

List AI-generated feedback suggestions. Suggestions are created when feedback is ingested from external sources (Slack, email, API) and processed by the AI pipeline.

Three suggestion types:

• create_post - AI extracted new feedback and suggests creating a post
• vote_on_post - AI matched feedback to an existing post and suggests adding a vote
• duplicate_post - AI detected two existing posts that may be duplicates

Scope: read:feedback + team role (admin or member)

Each suggestion includes the original raw feedback item, matched post (if applicable), AI signal data (summary, evidence, confidence), and source metadata.

list_suggestions()
list_suggestions({ suggestionType: "create_post" })
list_suggestions({ status: "dismissed", sort: "relevance" })

accept_suggestion

Accept an AI-generated suggestion. The result depends on the suggestion type:

• create_post: Creates a new post from the extracted feedback. Optional edits override the suggested title, body, or board.
• vote_on_post: Adds a proxy vote to the matched existing post.
• duplicate_post: Merges the source post into the target post. Use swapDirection to reverse which post is kept.

Scope: write:feedback + team role (admin or member)

accept_suggestion({ id: "feedback_suggestion_01abc..." })
accept_suggestion({
  id: "feedback_suggestion_01abc...",
  edits: { title: "Better title" }
})
accept_suggestion({ id: "merge_sug_01abc...", swapDirection: true })

dismiss_suggestion

Dismiss an AI-generated suggestion. The suggestion can be restored later via restore_suggestion.

Scope: write:feedback + team role (admin or member)

dismiss_suggestion({ id: "feedback_suggestion_01abc..." })
dismiss_suggestion({ id: "merge_sug_01abc..." })

restore_suggestion

Restore a dismissed suggestion back to pending status.

Scope: write:feedback + team role (admin or member)

restore_suggestion({ id: "feedback_suggestion_01abc..." })

get_post_activity

Get the activity log for a post. Shows status changes, merges, tag changes, owner assignments, proxy votes, comment pins, and other events in reverse chronological order (limited to the 200 most recent).

Scope: read:feedback + team role (admin or member)

Each activity entry includes the event type, actor name, metadata (e.g., old/new status), and timestamp.

get_post_activity({ postId: "post_01abc..." })

Help Center Tools

Note:
Help center tools are only available when the help center feature flag is enabled. See Help Center for setup.

create_article

Create a new help center article as a draft.

Scope: write:article + team role

Articles are created as drafts. Use update_article with publish: true to publish.

update_article

Update an existing help center article. Publish or unpublish by setting the publish parameter.

Scope: write:article + team role

All fields except articleId are optional. Only provided fields are updated.

delete_article

Soft-delete a help center article.

Scope: write:article + team role

manage_category

Create, update, or delete a help center category.

Scope: write:article + team role

Conversation Tools

Work the support inbox programmatically: list and read conversations, reply to visitors, and change conversation status. All conversation tools require a team role (admin or member) and the support inbox to be enabled.

list_conversations

List support-inbox conversations, newest activity first. Returns a compact, paginated list.

Scope: read:chat + team role (admin or member)

list_conversations({ status: "open" })
list_conversations({ assignedAgentPrincipalId: "principal_01xyz...", priority: "high" })

get_conversation

Get a conversation and its most recent messages.

Scope: read:chat + team role (admin or member)

Internal notes are excluded unless includeInternal is true. Anonymous visitors' synthetic emails are never returned.

get_conversation({ conversationId: "conversation_01abc..." })
get_conversation({ conversationId: "conversation_01abc...", includeInternal: true })

reply_to_conversation

Send an agent reply in a conversation (visible to the visitor). Auto-assigns the conversation to the calling agent if it's unassigned.

Scope: write:chat + team role (admin or member)

reply_to_conversation({ conversationId: "conversation_01abc...", content: "Thanks for reaching out, we're on it." })

set_conversation_status

Change a conversation's status (open, snoozed, or closed). Snoozing defers it until the customer next replies; closing stamps the resolution time; a later reply reopens it.

Scope: write:chat + team role (admin or member)

set_conversation_status({ conversationId: "conversation_01abc...", status: "closed" })

suggest_post

Suggest to the support team (not the visitor) that a resolved conversation be tracked as a feedback post. Appears only in the agent inbox as an internal note; a team member confirms with one click. Rejected unless the conversation is resolved.

Scope: write:chat + team role (admin or member)

suggest_post({ conversationId: "conversation_01...", boardId: "board_01...", title: "Add dark mode", content: "Customer asked for a night theme." })

share_post

Embed an existing feedback post as a card in the conversation so the visitor can view and upvote it. Use search to find candidates first, to surface related ideas and avoid duplicates.

Scope: write:chat + team role (admin or member)

share_post({ conversationId: "conversation_01...", postId: "post_01..." })

Ticket Tools

Work the support-ticket surface programmatically: list and read tickets, open new ones, reply, add internal notes, and link tickets to trackers. Tickets share the conversation scopes (read:chat / write:chat). All ticket tools require a team role (admin or member).

Note:
A service (API key) caller sees every ticket; a human caller sees only the tickets their role can view.

list_tickets

List support tickets, most recently updated first. Filter by type, internal status category, customer-facing stage, requester, or company.

Scope: read:chat + team role (admin or member)

list_tickets({ type: "customer", statusCategory: "open" })
list_tickets({ companyId: "company_01abc..." })

get_ticket

Get a ticket and its most recent thread messages, oldest-first.

Scope: read:chat + team role (admin or member)

get_ticket({ ticketId: "ticket_01abc...", includeInternal: true })

create_ticket

Open a support ticket. A description opens the thread. Returns the created ticket.

Scope: write:chat + team role (admin or member)

create_ticket({ type: "customer", title: "Refund not received", description: "Customer reports a missing refund from last week." })

reply_to_ticket

Post a reply on a ticket thread, visible to the requester. Stamps the first-response time on the first reply.

Scope: write:chat + team role (admin or member)

reply_to_ticket({ ticketId: "ticket_01abc...", content: "We've issued your refund; it should arrive in 3-5 days." })

add_ticket_note

Add an internal note to a ticket thread. The requester never sees it; only the support team does.

Scope: write:chat + team role (admin or member)

add_ticket_note({ ticketId: "ticket_01abc...", content: "Confirmed the refund with billing; awaiting bank processing." })

link_ticket

Link a customer ticket to a tracker so the tracker's stage changes cascade onto it. The tracker must be type tracker and the ticket type customer; a customer ticket belongs to at most one tracker.

Scope: write:chat + team role (admin or member)

Returns the tracker's linked tickets.

link_ticket({ trackerTicketId: "ticket_01tracker...", ticketId: "ticket_01customer..." })

unlink_ticket

Remove a customer ticket from a tracker.

Scope: write:chat + team role (admin or member)

Returns the tracker's remaining linked tickets.

unlink_ticket({ trackerTicketId: "ticket_01tracker...", ticketId: "ticket_01customer..." })

Resources

Resources provide lookup data for boards, statuses, tags, roadmaps, team members, and help center categories. Use them to find IDs before calling tools like triage_post or create_post.

Tip:
A typical workflow: read quackback://statuses to find the "planned" status ID, then call triage_post with that status ID.