
How to add Quackback MCP Server to Windsurf
AI agents search, triage, comment, vote, and manage feedback & changelogs in Quackback. Paste the config into ~/.codeium/windsurf/mcp_config.json and restart Windsurf.
Last updated June 14, 2026 · 134★ · http · apikey · official
Windsurf config for Quackback MCP Server
{
"mcpServers": {
"quackback-mcp-server": {
"serverUrl": "https://{host}/api/mcp",
"headers": {
"Authorization": "Bearer ${QUACKBACK_API_KEY}"
}
}
}
}Remote server — no local install needed. Restart the client after saving the config.
Setup steps
- 1Open Windsurf → Cascade → the hammer/MCP icon → Configure (or edit ~/.codeium/windsurf/mcp_config.json).
- 2Paste the Quackback MCP Server config below.
- 3Fill in placeholder secrets, then save.
- 4Click Refresh in the MCP panel.
- 5Quackback MCP Server's tools become available to Cascade.
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 Windsurf
searchSearch feedback posts or changelog entries with filtering and pagination
get_detailsGet full details for any entity by TypeID (post, changelog)
triage_postUpdate a post: set status, tags, and/or owner
vote_postToggle vote on a feedback post
proxy_voteVote on a feedback post on behalf of another user/customer
add_commentPost a comment on a feedback post, with threaded reply support
update_commentEdit a comment's content
delete_commentHard-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 + Windsurf FAQ
Where is the Windsurf config file?
Windsurf reads MCP servers from ~/.codeium/windsurf/mcp_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 Windsurf?
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.
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).