How to add Quackback MCP Server to Claude Desktop

AI agents search, triage, comment, vote, and manage feedback & changelogs in Quackback. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 14, 2026 · 134★ · http · apikey · official

Claude Desktop config for Quackback MCP Server

{
  "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.

Setup steps

1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
2Paste the Quackback MCP Server config below under the top-level "mcpServers" key.
3Fill in any placeholder secrets (API keys, paths) in the snippet.
4Save the file, then fully quit and reopen Claude Desktop.
5Open a chat and confirm Quackback MCP Server's tools appear under the 🔌 tools menu.

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)

What Quackback MCP Server can do in Claude Desktop

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

Security

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 + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Quackback MCP Server config there under the "mcpServers" key and restart the client.

Is Quackback MCP Server safe to use with Claude Desktop?

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).

View repo Full Quackback MCP Server page