Connected where your team already works.
Slack and X are built in. Signed webhooks, OAuth apps, the REST API and the MCP server connect everything else you run.
On every plan. Slack and X need you to connect your own workspace or account.
Demo project with made-up data.
Feedback from Slack, releases back to it.
Connect your Slack workspace once. Pick the channels each project listens to and the channels its releases are posted to.
- A message shortcut turns any Slack message into feedback in the right project.
- Link Slack users to their Damper accounts, and they can create tasks from Slack too.
- Status alerts can go to a Slack channel when a check fails.
- Publishing a release can post it to a Slack channel.
Demo project with made-up data.
Wire Damper into your own systems.
Outbound webhooks tell your systems when something changes. Each request is signed, so you can check it came from Damper.
- Events: feedback created, task status changed, task review decided, changelog published.
- Headers: X-Damper-Signature (HMAC-SHA256), X-Damper-Event and X-Damper-Timestamp.
- OAuth apps get scoped tokens to send and read feedback through the external API.
Every way in.
MCP server
Your coding agent connects to the hosted MCP server at api.usedamper.com/mcp with a project API key.
REST API
The same operations for agents and scripts without MCP, with the same dmp_ key.
OAuth 2.0
Let other apps submit and read feedback with the authorization code flow and scoped tokens.
Feedback widget
One script tag in your app, with verified identity for the people who are signed in.
Two more connections.
HAL
Send customer feedback from your HAL inbox to a Damper project.
X
Connect your X account and post release announcements when you publish.
Start with the tools you already use.
Connect Slack first, and add webhooks or the API when you need them.
Free plan, no credit card. Your roadmap can be live in five minutes.



