Set up with your agent
If you work with an AI agent — Claude Code, Claude Desktop, or any MCP client — it can add Tapback to your site for you. Connect it to Tapback once, paste a prompt, and it creates the Tapbar, gives you the embed snippet, tells you which templates to edit, and checks the counts once you deploy.
Connect
Point your agent at the Tapback MCP server — one URL, nothing to install:
claude mcp add --transport http tapback https://api.tapback.party/mcp
Then run /mcp and authorize. On Claude Desktop or claude.ai, it's Settings → Connectors → Add custom connector, paste https://api.tapback.party/mcp, and Connect. The full picture — accounts, and what the agent can and can't reach — is in Manage from your agent.
Copy a prompt for your stack
Pick your setup and copy the prompt, then paste it to your connected agent. Each one carries the placement details for that stack, so the agent has what it needs to take it from there.
Tick Also set up the in-page picker and the prompt gains a step for the authoring editor: the agent mints an authoring key and wires editor.js plus a <tapback-editor> element into your draft or preview template, gated on that stack's own draft flag. It's a Plus feature, and the picker lets you choose a post's reactions while you're looking at it.
What the agent does
Working from that prompt, it will:
- ask for your domain and create a Tapbar with it as the allowed site
- pick a starter reaction set — you can change it any time
- give you the exact
<script>+<tapback-bar>snippet and where each piece goes - post a test reaction and read the count back once you've deployed
- with the picker ticked: mint the authoring key and place the editor script and
<tapback-editor>element in your draft template only
From there, "change the heart to a fire" or "show a ghost and a skull on my Halloween post" are one message each. For the hands-on version of any of this, see Reactions on your blog.