MCP Directory

Quackback MCP Server

Official

AI agents search, triage, comment, vote, and manage feedback & changelogs in Quackback.

Unverified
HTTP (remote)
API key
TypeScript

Add to your client

Copy the config for your MCP client and paste it into its config file.

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "quackback-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://{host}/api/mcp",
        "--header",
        "Authorization: Bearer ${QUACKBACK_API_KEY}"
      ]
    }
  }
}

Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.

Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf

Before you start

  • A running Quackback instance (cloud at app.quackback.io, or self-hosted via Docker / Railway)
  • A Quackback API key (qb_...) generated under Admin > Settings > Developers, or OAuth browser login
  • For Claude Desktop: Node.js (uses the mcp-remote bridge)

About Quackback MCP Server

Quackback's MCP server is bundled with the Quackback feedback platform and exposes feedback and changelog operations to AI agents over streamable HTTP at https://{your-host}/api/mcp. Agents can search and read posts/changelogs, triage and moderate feedback, vote, comment, react, manage roadmaps, merge duplicates, and create/update/publish changelog entries, plus handle AI-generated feedback suggestions. It supports both API-key (Bearer) and OAuth authentication, with copy-paste configs for Claude Code, Cursor, VS Code, Windsurf, and Claude Desktop.

Tools & capabilities (23)

search

Search feedback posts or changelog entries with filtering and pagination

get_details

Get full details for any entity by TypeID (post, changelog)

triage_post

Update a post: set status, tags, and/or owner

vote_post

Toggle vote on a feedback post

proxy_vote

Vote on a feedback post on behalf of another user/customer

add_comment

Post a comment on a feedback post, with threaded reply support

update_comment

Edit a comment's content

delete_comment

Hard-delete a comment and its replies

react_to_comment

Add or remove an emoji reaction on a comment

create_post

Submit new feedback on a board

delete_post

Delete a feedback post

restore_post

Restore a previously deleted feedback post

merge_post

Merge a duplicate post into a canonical post

unmerge_post

Restore a merged post to independent state

manage_roadmap_post

Add or remove a post from a roadmap

create_changelog

Create a changelog entry (draft or published)

update_changelog

Update title, content, publish state, and linked posts on a changelog

delete_changelog

Soft-delete a changelog entry

list_suggestions

List AI-generated feedback suggestions

accept_suggestion

Accept an AI feedback suggestion

dismiss_suggestion

Dismiss an AI feedback suggestion

restore_suggestion

Restore a dismissed feedback suggestion

get_post_activity

Get the activity timeline for a feedback post

What this server can do

Quackback MCP Server provides tools for these capabilities — tap one to see every MCP server that does the same:

When to use it

  • Let an AI agent triage incoming feedback by setting status, tags, and owners
  • Search and summarize feature requests, then draft and publish a changelog entry
  • Detect and merge duplicate feedback posts automatically
  • Vote or proxy-vote on behalf of customers and review a post's activity timeline
  • Review, accept, or dismiss AI-generated feedback suggestions

Security notes

The MCP server is hosted by your own Quackback instance; the endpoint is https://{your-host}/api/mcp. Authenticate with an API key (Bearer qb_...) generated under Admin > Settings > Developers, or via OAuth (browser login; supported by Claude Code and Claude Desktop). Store the API key in an environment variable (e.g. QUACKBACK_API_KEY) rather than hardcoding it.

Quackback MCP Server FAQ

What is the MCP server endpoint?

It is served by your own Quackback instance at https://{your-host}/api/mcp using the streamable HTTP transport. For Quackback Cloud, the host is your workspace domain.

How do I authenticate?

Use an API key (Bearer qb_...) created under Admin > Settings > Developers, or OAuth (browser login). Claude Code and Claude Desktop support both; Cursor, VS Code, and Windsurf use the API key.

Which clients are supported?

The in-app setup guide provides copy-paste configs for Claude Code (.mcp.json), Cursor (.cursor/mcp.json), VS Code (.vscode/mcp.json), Windsurf (~/.codeium/windsurf/mcp_config.json), and Claude Desktop (claude_desktop_config.json via the mcp-remote bridge).

Is it free / open source?

Yes. Quackback is AGPL-3.0 and self-hostable for free with Docker or one-click on Railway. The MCP server is included in every deployment.

Alternatives to Quackback MCP Server

Compare all alternatives →

Self-hosted MCP server for Jira and Confluence Cloud and Server/Data Center.

Verified
stdio (local)
API key
Python
11 tools
Updated 2 months agoRepo

Create, read, and modify Excel workbooks with your AI agent — no Microsoft Excel required.

Unverified
stdio (local)
No auth
Python
25 tools
Updated 2 months agoRepo

Official Notion server to read, search, create, and update pages and databases in your workspace.

Verified
stdio (local)
API key
TypeScript
9 tools
Updated 4 months agoRepo