Agents Index

Damper

OnlineNew

Feedback, roadmap, agent task execution with review, changelog, status pages and error logs.

Visit publisherConnectJSON

What it can do: 80 tools

  • list_projects read-onlyList all projects accessible with this API key. Use this to find project IDs for other tools. **Start here** to discover which projects you can work with.
  • get_agent_instructions read-onlyGet the canonical Damper workflow instructions. Use this to set up or update CLAUDE.md in a project.
  • list_tasks read-onlyGet roadmap tasks. Returns backlog/planned/in-progress by default. Search by title, description, plan, user story, or exact label, and filter by type, quarter, etc. Use `query` before paginating when checking whether a m
  • get_task read-onlyGet task details. Defaults to a compact view (plan, current progress, subtasks, PRs, unresolved decisions, completion receipt, evidence counts) — no `agentNotes` dump. Pass `detailMode: "full"` for the legacy full payloa
  • list_self_assessments read-onlyList recent structured agent self-assessments for a project. Use this miss log to find recurring missingContext/toolIssues/processGaps and improve project context.
  • update_taskUpdate task fields like description, implementation plan, priority, effort, quarter, start/due dates, labels, or visibility. Pass status "closed" to discard a task that will not ship. Useful for refining task details as
  • create_taskCreate a new roadmap task. Use for importing from TODO files or creating work items. When the task comes from customer feedback, pass `feedbackIds` to link it in the same call: the feedback status follows the task and fo
  • add_noteAdd a note to a task, or resolve a previously reported blocker/open_question. Use ONLY for non-obvious approach decisions and blockers — do not restate commits, checklist confirmations, or self-assessment findings here;
  • add_commitLog a commit for a task (secondary detail — the linked pull request is the primary deliverable, see `link_pr`). **When to use:** - After a notable commit: log hash and message - When completing work: optionally pass com
  • link_prLink the pull request that delivers this task. The PR is the primary deliverable of a task — call this as soon as the PR exists, and call it again with `state: "merged"` after merge. Upserts by URL, so repeated calls upd
  • create_subtaskAdd a new subtask to a task. Useful for breaking down work into smaller steps. Optionally set startDate/dueDate (YYYY-MM-DD) so the subtask appears on the roadmap timeline.
  • update_subtaskUpdate a subtask: mark it done/not done and/or set its timeline dates. Use get_task to see subtask IDs. Dates are YYYY-MM-DD; null clears a date.
  • delete_subtaskRemove a subtask from a task. Use get_task to see subtask IDs.
  • delete_taskPermanently delete a task. Only works on tasks in backlog or planned status with no commits.
  • add_task_dependencyAdd a dependency between roadmap tasks. The blocker task must be done before the blocked task can be worked on. Provide either blockerId (this task is blocked by another) or blockedId (this task blocks another).
  • remove_task_dependencyRemove a task dependency by dependency ID.
  • add_api_exampleAttach a request/response example for an API endpoint you added or changed, so the reviewer can check the contract in Damper without running anything. Add one per changed endpoint (more for distinct cases, e.g. success a
  • add_screenshotAttach a screenshot of a page or screen you added or changed, so the reviewer sees the result in Damper. Capture every changed page in each relevant state (default, empty, loading, error, validation…), using the locale/t
  • add_diagramAttach a Mermaid diagram that explains the logic or structure behind a change, so the reviewer can follow it without reading the diff. OPTIONAL — add one only when it clarifies something a list of endpoints or screenshot
  • list_review_artifacts read-onlyList the API examples, screenshots and diagrams attached to a task, with the reviewer's verdict on each (approved / changes_requested + comment). Use it to check coverage before complete_task, and to find artifacts a rev
  • remove_review_artifactRemove an API example, screenshot or diagram from a task, by id or by kind + key (e.g. a page that no longer changes).
  • start_taskLock and start a task. Fails if locked by another agent unless force=true. Use force=true to take over a task from another agent (e.g., if they abandoned it). Returns project context index with relevant sections for the
  • review_taskOptional standalone self-review step. You can also pass `selfAssessment` directly to `complete_task` instead. Reflect on your session: what project knowledge was missing, what tools were confusing, what process gaps cau
  • complete_taskMark task as ready for review (in_review). A human will verify and move it to done. Pass `skipReview: true` to mark as done immediately (use when the human explicitly asks). If the task is already in_review (put there b
  • request_reviewLightweight hand-off into review: move an in_progress task to in_review as soon as a human could review it (a working slice, an opened PR, attached screenshots or API examples, or when you are about to stop for the sessi
  • abandon_taskRelease lock and return task to planned status. Works for in_progress and in_review tasks. **Before calling:** 1. Push any WIP commits **Summary parameter:** What was done, what remains, blockers. Helps the next agent.
  • list_context_sections read-onlyList available project context sections with brief previews.
  • resolve_context read-onlyResolve touched file paths to governing context sections, critical rules, risk domains, and suggested checklist scope. Uses routing/path-to-context when present and falls back to module paths plus section metadata.
  • get_context_section read-onlyGet full content of a specific context section. Supports glob patterns for hierarchical sections. **Hierarchical paths**: For monorepos or large projects, sections can be organized hierarchically (e.g., "api/architectur
  • update_context_sectionUpload/update a project context section. Use after analyzing local codebase. This action shares documentation with the Damper project for future AI agents. **When to use hierarchical names**: For monorepos or large proj
  • delete_context_sectionDelete a project context section. Use when documentation is outdated or no longer relevant.
  • sync_project_contextBulk upload all project context sections at once. Use after analyzing a codebase. ⚠️ SECURITY WARNING: Do NOT include sensitive information.
  • get_project_context read-onlyGet project context index (token-efficient). Returns section list with previews. Use get_context_section to fetch full content for sections you need. **IMPORTANT:** Call this at session start. Contains architecture, con
  • get_section_blocks read-onlyGet a block index for a context section. Returns headings with character counts. Use to selectively load only relevant parts with `get_section_block_content`.
  • get_section_block_content read-onlyGet the full content of specific blocks within a section. Use `get_section_blocks` first to see available block IDs, then fetch only the ones you need.
  • prepare_work read-onlyBuild a deterministic, compact work packet with governing context, a shadow graph comparison and provenance, path-owned surfaces, checklist scope, project verification, unvalidated route-fixture representation, instructi
  • audit_context_health read-onlyFind invalid route taxonomy, weak or uncovered fixtures, missing baselines, route overlap, stale knowledge, and fallback usage.
  • get_context_graph read-onlyInspect the typed graph projection derived from context routes, sections, bundles, modules, and optional project-authored relationships.
  • resolve_context_graph read-onlyRun bounded shadow-mode graph traversal for repository paths. Returns ranked context candidates and full provenance without changing authoritative route resolution.
  • list_context_relations read-onlyList project-authored typed relationships layered over the derived context graph.

…and 40 more.

Connect it

Claude Code
claude mcp add --transport http damper https://api.usedamper.com/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://api.usedamper.com/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "damper": {
      "url": "https://api.usedamper.com/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "damper": {
      "type": "http",
      "url": "https://api.usedamper.com/mcp"
    }
  }
}

Questions

What does Damper do?

Feedback, roadmap, agent task execution with review, changelog, status pages and error logs. It exposes 80 tools to AI assistants.

What tools does Damper provide?

80 tools, including list_projects, get_agent_instructions, list_tasks, get_task, list_self_assessments, update_task, create_task, add_note, add_commit, link_pr, create_subtask, update_subtask….

How do I connect Damper to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://api.usedamper.com/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Damper require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Damper online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Damper?

usedamper.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Productivity & Docs