Skip to content

MCP server

Connect AI agents to your feedback and support

Quackback's MCP server lets Claude, Cursor and any MCP client search and triage feedback, reply to customers, work tickets and update your help center, with only the access you grant.

Connect your first agent

  • MCP server on Pro and above
  • Sign in with OAuth or an API key
  • Open source. Self-host on your own domain
Example session in Claude Code
> Merge this week's duplicate requests about CSV export.

  quackback · search
  { "query": "CSV export", "dateFrom": "this_week" }
  → 3 posts: Export to CSV (194 votes), CSV download (12), Export as CSV (4)

  quackback · merge_post  ×2
  → Merged into "Export to CSV". Votes from both now count there.

Done. "Export to CSV" now holds every vote, so it's the one to track.

What agents can do in Quackback

Agents work the same workspace your team does, through tools for feedback, support, the help center, the changelog and your settings.

See every tool

Feedback

Search and filter posts, set status, owner and tags, merge duplicates, comment, and add votes for customers who asked.

Conversations and tickets

Read conversations and reply to customers, open, snooze or close them, and open, answer and add notes to tickets.

Help center

Search articles, then write, update and publish articles and categories.

Changelog

Find what shipped, then draft, publish or schedule the entry that tells everyone.

Support meets feedback

Share an existing post into a conversation so the customer can vote, suggest that a resolved conversation becomes a post, vote for a customer, and accept suggested merges. Link customer tickets to a tracker ticket so its progress carries over.

Workspace settings

Change branding, the portal, Messenger, modules, office hours and the changelog. Preview a change first, and every change returns a receipt with the values before and after that you can undo. For anything else, the agent links you to the right page.

Safe by design

Agents act with the access you grant, and what customers write reaches them as data.

Sign in your way

OAuth with dynamic client registration, so clients set themselves up from the URL, and a device code flow for tools without a browser. Or use an API key.

Customer text is marked

Results flag every field written by a customer or visitor, so an agent treats it as data to read, never as instructions.

Some things stay with people

Members, roles, API keys, billing and SSO can't be changed from chat. The agent opens the page for a person to review. An agent with write access can delete posts, comments, changelog entries and help articles. A deleted post can be restored for 30 days. A deleted comment can't be undone.

Connect your client in a minute

The server is on by default on plans that include it. Your endpoint is your workspace address followed by /api/mcp. Turn the server off, or stop new OAuth apps registering, in Settings under Developers.

Add the endpoint

Clients that support MCP OAuth, like Claude Code and Cursor, need only the URL. They open the browser so you can sign in and approve access.

Terminal
claude mcp add --transport http quackback \
  https://feedback.acme.com/api/mcp

Or use an API key

Create a key in Settings and send it as a Bearer token. Each key acts as its own identity, so the activity log shows which agent made each change.

.cursor/mcp.json
{
  "mcpServers": {
    "quackback": {
      "url": "https://feedback.acme.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:QUACKBACK_API_KEY}"
      }
    }
  }
}

Choose what it can do

When you connect over OAuth, the consent screen offers Full access or Read only, or access for each area. Full access is preselected, so pick Read only for an agent that should only look. Keys get read, or read and write, for each area, and never more than their creator's role allows. Changelog access is write only.

Read the MCP guide
Scopes
read:feedback     search posts and changelog entries
write:feedback    create posts, vote, comment, triage
write:changelog   create, update and publish entries
read:article      search and read help articles
write:article     write and publish help articles
read:chat         read conversations and tickets
write:chat        reply, change status, add notes
read:settings     read workspace settings
write:settings    change branding, portal, Messenger and more

Made for real work

See which help desks and feedback tools have an MCP server, and who maintains each one, in the help desk MCP server tracker.

Building your own integration? Explore the API
Works with your toolsClaude Code, Cursor, VS Code, Windsurf, Claude Desktop, Claude.ai and ChatGPT, and any client that supports remote MCP over HTTP.
Every change attributedThe activity log shows which person or key did what.
One key, two usesAPI keys use the same access levels for MCP and the REST API.
Set up the MCP serverConnect a client with OAuth or an API key, and choose its access. On Pro and up.
On your own domainQuackback is open source. Self-host it and the endpoint runs on your servers.

Common questions

What is an MCP server?

MCP, the Model Context Protocol, is an open standard that lets AI tools call other software. Quackback's MCP server gives agents like Claude and Cursor tools to search, read and update your workspace, with the access you grant.

Which AI tools work with Quackback's MCP server?

Any client that supports remote MCP servers over HTTP. The setup guides cover Claude Code, Cursor, VS Code, Windsurf and Claude Desktop, and Claude.ai and ChatGPT connectors sign in through the same OAuth flow.

How do agents sign in?

Clients that support MCP OAuth, such as Claude Code and Cursor, need only the server URL: they register themselves and sign you in through the browser. Tools without a browser, such as a CLI on a remote machine, can use the device code flow and show a code you approve on another device. Any client can use an API key from Settings instead, sent as a Bearer token.

Can I limit what an agent can do?

Yes. When you connect over OAuth, the consent screen offers Full access or Read only, or you can set access for each area. Full access is preselected, so choose Read only if the agent should not write. API keys get read, or read and write, for feedback, the help center, conversations and settings. Changelog access is write only. A key never gets more than the role of the teammate who created it.

What stops a customer's message from steering an agent?

Every tool result that holds text written by someone outside your team, such as a customer message, a portal comment or an inbound email, says which fields that text is in and marks it as data to read, never instructions to follow. The text itself is left unchanged.

Is the MCP server the same as Quackback AI?

No. Quackback AI is built in: an agent that answers your customers and a copilot for your team. The MCP server is for AI tools you already use, like Claude or Cursor, to work in your workspace.

Which plans include the MCP server?

On Quackback Cloud, the MCP server is included on Pro, Business and Enterprise, each with a 14-day free trial. The open-source, self-hosted edition includes it at no cost, on your own domain.

Have another question? Talk to the team.

Put your agents to work