Manage from your agent
Tapback runs an MCP server, so you can do everything the console does from your coding agent instead. Ask Claude to add reactions to your site and it can sign you up, create the Tapbar, pick the reactions, hand you the embed snippet, and check the counts once it's live — in the same conversation where you're editing the page.
It's one connector URL, hosted alongside the API. Nothing to install.
https://api.tapback.party/mcpIn a hurry? Copy a ready-made setup prompt for your stack — Hugo, Jekyll, Astro, Next.js, WordPress and more.
Connect
Claude Code:
claude mcp add --transport http tapback https://api.tapback.party/mcpThen run /mcp and authorize — it opens a browser tab to sign you in.
Claude Desktop or claude.ai: Settings → Connectors → Add custom connector, paste the URL, and click Connect.
Either way a Tapback page opens in your browser. Sign in with your email and password, or create an account right there (the page carries the same anti-bot check and email verification as signup on the site). A new account has to verify its email — and wait for approval if the platform requires it — before it can sign in, so after you verify, reopen the connection to finish. Signing in authorizes that one agent; no cookie is set, and the agent never sees your password.
Once connected, the agent acts as your account with the same reach you have in the console, with one exception: your Tapbar's secret key is never handed to the agent. It stays a console-only credential, so it can't end up in a chat transcript.
What the agent can do
You talk to the agent in plain language — "make the reactions a heart and a rocket", "what are my top pages this week" — and it calls the matching tool. The surface:
| Area | You can ask it to… |
|---|---|
| Tapbars | list your Tapbars, create one, read a Tapbar's full config, pause / archive / resume it, reset it to defaults |
| Configure | change the reaction set (icons, colors, labels), the palette of extra reactions and which ones a given page shows (the Plus per-post feature), the look (layout, corner, theme, fall animation, spacing), the allowed sites, and the counting mode |
| Keys | list a Tapbar's keys, mint a new publishable / secret / authoring key (shown once — an authoring key comes with the ready-to-paste editor.js snippet and its <tapback-editor> element), and revoke one |
| Embed | generate the exact <script> + <tapback-bar> snippet for a page — the same one the console's Embed panel produces — or the authoring markup for a draft template, editor.js plus a <tapback-editor> element, with a placeholder where your authoring key goes |
| Analytics | read recent reaction volume, lifetime totals and top pages, and export a Tapbar's data as JSON or CSV |
| Try it live | post a test reaction to a page and read the counts back, to confirm the bar works end to end |
| Icons | search the built-in set or the full Iconify library, preview an icon, and set it on a reaction |
The config the agent writes goes through the same validation as the console — reaction limits, allowed-origin format, the plan's feature gates — so a request that wouldn't be valid in the console fails the same way, with a reason you can act on.
Example: add reactions to a blog
Ask your agent something like "Add a Tapback reactions bar to my blog at blog.example.com." It can, in one go:
- Create a Tapbar and set
https://blog.example.comas the allowed site. - Choose a reaction set — say a heart, a star, and a laugh.
- Give you the embed snippet to drop into your template.
- After you deploy, post a test reaction and read the count back so you know it's wired up.
From there, "change the heart to a fire" or "switch the bar to the bottom-left corner" are one message each, and every embed updates without a code change — the same as editing in the console.
Testing counts
The "try it live" tools post real reactions: they increment that Tapbar's own totals for whatever entity you point them at. Use a throwaway entity id like mcp-test so a test tap doesn't land on a real page's count. Your Tapbar's per-reader rate limits still apply.
Managing connections
Every agent you authorize shows up under Account → Connected apps in the console. Each row is one agent, with the date it connected. Click Disconnect to cut its access: it happens right away — the agent can't act on your account again until you reconnect it — and it only affects that one connection, so your other agents keep working. Removing the connector inside the agent itself works too.
Privacy and access
The agent holds a short-lived token scoped to your account — it can read and change your Tapbars and read your analytics, and it re-checks that your account is still active on every call. Reaction data itself carries no reader identity; see Privacy & limits for what Tapback stores.