Zero to loop in five minutes.

Quickstart

The whole loop is five steps. Sign up, add one script tag, publish your roadmap, point your agent at MCP, and let the changelog write itself.

1. Create a project

Sign up and create a project from the dashboard. Give it a name and a slug — the slug identifies the project across the widget, public pages and API.

2. Embed the feedback widget

Add one tag before </body>. That's the install — grab your project ID from Settings → Embed in the dashboard.

<!-- Add before </body> -->
<script
  src="https://api.usedamper.com/widget.js"
  data-project-id="YOUR_PROJECT_ID"
></script>

Everything is configurable via attributes — theme, position, colors, trigger style and the copy users see:

<script
  src="https://api.usedamper.com/widget.js"
  data-project-id="YOUR_PROJECT_ID"
  data-theme="auto"
  data-position="right"
  data-primary-color="#2563eb"
  data-trigger-label="Feedback"
  data-trigger-style="subtle"
  data-greeting="How can we improve?"
  data-placeholder="Describe your idea..."
  data-keyboard-shortcut="ctrl+shift+f"
  data-feedback-types="bug,feature,improvement"
  data-enable-sentiment="true"
></script>

Identify signed-in users

Pass the signed-in user to the widget with an HMAC signature and their plan — votes arrive pre-weighted, and the widget can be limited to identified users only.

// after your user logs in
Damper.identify({
  userId: "user_123",      // required
  email: "[email protected]", // optional, for notifications
  plan: "pro",              // optional, drives vote weight
  tier: 50,                 // optional, priority 1-99
  userHash: "hmac-signature"  // optional, verified identity
});

JavaScript API

Everything is also controllable from code: Damper.open(), Damper.close(), Damper.isOpen(), Damper.isIdentified() and Damper.identify() — for opening the widget after an upsell prompt or submitting feedback from your own UI.

3. Publish your roadmap

Create roadmap items from feedback in your inbox — or from scratch. Add them to a board, mark them public, and share the link. Voters pick items, leave their email, and their votes hit your demand score.

Your project also gets a public feedback board and changelog alongside the roadmap — each with its own toggle, styling and subscribers.

4. Connect your AI agent

Damper ships a hosted MCP server — any MCP client can work your roadmap. Add it to Claude Code's .mcp.json:

{
  "mcpServers": {
    "damper": {
      "type": "http",
      "url": "https://api.usedamper.com/mcp",
      "headers": {
        "Authorization": "Bearer dmp_..."
      }
    }
  }
}

Create the key under Settings → API Keys. The recommended agent loop: get_project_context → list_tasks → start_task → work → complete_task.

Read the full MCP reference →

5. Automate the changelog

When a public task is marked done, Damper adds it to a draft changelog entry. Publish it and voters get notified by email automatically. Connect X under integrations and releases post themselves.

Integrations

• Slack — install the Damper app to your workspace and use the message shortcut to turn any thread into feedback.
• X / Twitter — connect your account once; published changelog entries can auto-post.
• Stripe — your plan tiers drive vote weighting on the roadmap.
• Email — voters and submitters get notified when what they asked for ships.

Reference

Deep dives for builders:

• MCP reference — all 100+ tools, auth and the workflow. — all 100+ tools, auth and the workflow.
• AI execution — how agents work your roadmap. — how agents work your roadmap.
• Weighted voting — how demand scores are calculated. — how demand scores are calculated.
• Pages — notes, meetings and database pages with live relations. — notes, meetings and database pages with live relations.
• Status pages — monitors, incidents and subscriber emails. — monitors, incidents and subscriber emails.
• Error logs — ingest production errors by API. — ingest production errors by API.
• Widget — identity, attachments and the JS API. — identity, attachments and the JS API.
• Context graph — typed context for coding agents. — typed context for coding agents.
• Status pages — monitors, incidents and subscriber emails.
• Error logs — ingest production errors by API.
• Widget — identity, attachments and the JS API.
• Context graph — typed context for coding agents.