@damper/mcp

MCP server for Damper - enables AI agents to manage roadmap tasks.

Install

npm install -g @damper/mcp

Setup

1. Get API Key

Damper → Settings → API Keys → Generate

2. Configure Your AI Agent

Claude Code (~/.claude.json or ~/.config/claude/claude.json):

{
  "mcpServers": {
    "damper": {
      "command": "npx",
      "args": ["@damper/mcp"],
      "env": { "DAMPER_API_KEY": "dmp_..." }
    }
  }
}

Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "damper": {
      "command": "npx",
      "args": ["@damper/mcp"],
      "env": { "DAMPER_API_KEY": "dmp_..." }
    }
  }
}

Multiple Projects

Each API key is tied to one project. For multiple projects, configure separate server entries:

Claude Code (~/.claude.json or ~/.config/claude/claude.json):

{
  "mcpServers": {
    "damper-frontend": {
      "command": "npx",
      "args": ["@damper/mcp"],
      "env": { "DAMPER_API_KEY": "dmp_frontend_xxx" }
    },
    "damper-backend": {
      "command": "npx",
      "args": ["@damper/mcp"],
      "env": { "DAMPER_API_KEY": "dmp_backend_xxx" }
    }
  }
}

The AI will see tools from both servers and can distinguish between them:

• "list tasks from damper-frontend"
• "start the auth bug in damper-backend"

Tools

| Tool | Description | |------|-------------| | list_tasks | Get roadmap tasks (filter by status, type, quarter) | | get_task | Task details + subtasks + linked feedback | | create_task | Create task with type (bug, feature, improvement, task) | | update_task | Update description, plan, priority, effort, quarter, labels | | start_task | Lock and start task (use force to take over) | | add_note | Add progress note | | create_subtask | Add subtask to a task | | update_subtask | Mark subtask done/undone | | complete_task | Mark done, release lock | | abandon_task | Release lock, return to planned | | list_feedback | Browse user feedback | | get_feedback | Feedback details + votes |

Task Types

Filter tasks by type to prioritize work:

> List all bugs
> Work on the first feature
> Show me improvement tasks

Types: bug 🐛, feature ✨, improvement 💡, task 📌

Task Metadata

Tasks include project management fields visible in list_tasks and get_task:

• Priority: high 🔴, medium 🟡, low ⚪
• Effort: xs, s, m, l, xl
• Quarter: Target quarter (Q1 2025, Q2 2025, etc.)
• Labels: Custom tags
• Due date: Target completion date

Updating Tasks

Refine task details as you work:

> Set priority to high for this task
> Update the implementation plan with what I've learned
> Add labels: backend, api, auth
> Set effort to medium
> Schedule this for Q2 2025

Subtasks

Tasks can have subtasks for tracking incremental progress. Use get_task to see subtasks with their IDs:

## Subtasks (2/5)
- [x] Setup database schema (id: abc123)
- [ ] Implement API endpoints (id: def456)

Create and update subtasks as you work:

> Add a subtask "Write unit tests" to this task
> Create subtask for database migrations
> Mark the database schema subtask as done
> Update subtask def456 to done

Task Locking

When you start a task, it's locked to prevent other agents from working on it simultaneously:

• Same agent starting again → success (idempotent)
• Different agent starting → fails with 409 (use force: true to take over)
• Complete or abandon → releases lock

Usage Examples

> What tasks are available?
> List bugs I can fix
> Show tasks for Q2 2025
> What's unscheduled? (quarter: none)
> Import my TODO.md into Damper
> Work on the dark mode feature
> Show me the subtasks for this task
> Mark the first subtask as done
> I'm done with the auth task - tests pass
> Abandon the current task, I'm blocked

Environment

| Variable | Required | Default | |----------|----------|---------| | DAMPER_API_KEY | Yes | - | | DAMPER_API_URL | No | https://api.usedamper.com |

License

MIT