NestDaddy

Damper

com.usedamper/mcp · v0.6.0

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

Connect Remote server

Terminal
claude mcp add --transport http mcp https://api.usedamper.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.usedamper.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.usedamper.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://api.usedamper.com/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 80 found in our last check

  • list_projects

    List 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

    Get the canonical Damper workflow instructions. Use this to set up or update CLAUDE.md in a project.

  • list_tasks

    Get 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 matching task already exists. Returns up to 50 tasks by defa…

  • get_task

    Get 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 payload (agentNotes, all sessions/commits inline), or request spe…

  • list_self_assessments

    List recent structured agent self-assessments for a project. Use this miss log to find recurring missingContext/toolIssues/processGaps and improve project context.

  • update_task

    Update 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 you learn more about the work. Set startDate and dueDate wh…

  • create_task

    Create 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 followers are notified, the same as linking later with `link_…

  • add_note

    Add 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; those are already stored structurally and shown in `get_tas…

  • add_commit

    Log 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 commits to complete_task instead **Example:** After `git commit…

  • link_pr

    Link 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 update the same PR record. **When to use:** - Right after open…

  • create_subtask

    Add 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_subtask

    Update 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_subtask

    Remove a subtask from a task. Use get_task to see subtask IDs.

  • delete_task

    Permanently delete a task. Only works on tasks in backlog or planned status with no commits.

  • add_task_dependency

    Add 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_dependency

    Remove a task dependency by dependency ID.

  • add_api_example

    Attach 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 and validation error — give each its own `key`). **Upserts b…

  • add_screenshot

    Attach 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/theme/viewport the project asks for (see start_task). Give e…

  • add_diagram

    Attach 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 screenshots cannot: a decision tree or branching rule, a multi-step f…

  • list_review_artifacts

    List 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 reviewer asked you to redo.

  • remove_review_artifact

    Remove an API example, screenshot or diagram from a task, by id or by kind + key (e.g. a page that no longer changes).

  • start_task

    Lock 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 task. If the reviewer decided your latest review request, t…

  • review_task

    Optional 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 caused friction. This drives project improvements. If you have…

  • complete_task

    Mark 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 by a previous complete_task call), calling this again will mo…

  • request_review

    Lightweight 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 session). Do not leave reviewable work in in_progress. No checkl…

  • abandon_task

    Release 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

    List available project context sections with brief previews.

  • resolve_context

    Resolve 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

    Get 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/architecture", "api/endpoints/auth"). Use glob patterns to fetch multip…

  • update_context_section

    Upload/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 projects, use paths like `api/architecture`, `api/testing` to or…

  • delete_context_section

    Delete a project context section. Use when documentation is outdated or no longer relevant.

  • sync_project_context

    Bulk upload all project context sections at once. Use after analyzing a codebase. ⚠️ SECURITY WARNING: Do NOT include sensitive information.

  • get_project_context

    Get 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, conventions, and patterns you MUST follow. Skipping this leads…

  • get_section_blocks

    Get 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

    Get 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

    Build 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, instruction drift, and guarded delegation guidance. `verificationCom…

  • audit_context_health

    Find invalid route taxonomy, weak or uncovered fixtures, missing baselines, route overlap, stale knowledge, and fallback usage.

  • get_context_graph

    Inspect the typed graph projection derived from context routes, sections, bundles, modules, and optional project-authored relationships.

  • resolve_context_graph

    Run bounded shadow-mode graph traversal for repository paths. Returns ranked context candidates and full provenance without changing authoritative route resolution.

  • list_context_relations

    List project-authored typed relationships layered over the derived context graph.

  • upsert_context_relation

    Create or update an explicit typed relationship. Existing routes, bundles, modules, and section metadata remain authoritative; use relationships for missing cross-surface or semantic links.

  • delete_context_relation

    Delete a project-authored context relationship. Derived graph edges are not mutable through this tool.

  • list_context_routes

    List structured path-to-context routes in priority order.

  • upsert_context_route

    Create or update a validated structured context route.

  • delete_context_route

    Delete a structured context route by name.

  • preview_context_route_migration

    Parse Markdown routing into structured route candidates without writing them.

  • validate_context_routing

    Run project route fixtures against the production context resolver.

  • compare_context_resolution

    Compare structured routing output with legacy Markdown routing for repository paths.

  • list_context_bundles

    List versioned context bundles and recent versions.

  • upsert_context_bundle

    Create or update a coherent context bundle. Semantic changes record immutable versions; identical retries are no-ops.

  • get_context_bundle

    Get a context bundle with immutable version snapshots, optionally selecting one version.

  • delete_context_bundle

    Delete a context bundle and its version history.

  • list_context_fixtures

    List executable context routing expectations.

  • upsert_context_fixture

    Create or update intended executable expectations for an important repository path. Derive assertions from project truth and verified code behavior, never by copying the current resolver output; only write project context when authorized, then run validate_context_routing.

  • report_context_feedback

    Report missing, irrelevant, or incorrectly routed knowledge without storing prompts or source code.

  • delete_context_fixture

    Delete an executable routing fixture by name.

  • prepare_completion

    Resolve final touched paths, compare them with the prepare_work snapshot, detect version drift and scope expansion, and generate context disposition evidence. Also returns `reviewEvidence` for the final scope: which screenshots, API examples and diagrams the project expects, how…

  • preview_context_update

    Preview a section replacement or stable-block patch, including semantic changes and sensitive-data warnings, without writing.

  • patch_context_section

    Apply stable-block operations with optimistic concurrency and immutable version snapshots.

  • upsert_context_block

    Replace or append a stable context block while preserving unrelated blocks. The Markdown content must begin with a level-2 or level-3 heading whose generated slug exactly matches blockId.

  • verify_context_section

    Record repository verification without mutating section content.

  • render_context_routes_markdown

    Render the canonical structured route mapping as deterministic generated Markdown.

  • list_context_maintenance_candidates

    List the current deduplicated context-maintenance queue without refreshing or mutating it.

  • refresh_context_maintenance_candidates

    Aggregate privacy-safe feedback, self-assessment gaps, and fallback telemetry; may auto-create private tasks when project policy enables it.

  • convert_context_maintenance_candidate

    Convert a candidate into a deduplicated private context-maintenance roadmap task.

  • list_feedback

    Get user feedback. Useful for understanding user needs. Feedback summaries include available dates such as `createdAt`, `updatedAt`, `firstOccurredAt`, and `lastOccurredAt`, and `attachmentCount` (screenshots or files the submitter attached; download them with `get_feedback_atta…

  • get_feedback

    Get feedback details with votes, comments and a list of attachments. Download an attachment with `get_feedback_attachment`.

  • get_feedback_attachment

    Download a screenshot or file attached to a feedback item. `index` is the 0-based position shown by `get_feedback` (`attachmentCount` in `list_feedback` / `get_feedback` tells you how many exist). Images come back as image content you can view; other files come back as an embedd…

  • update_feedback

    Update feedback status or visibility.

  • reply_to_feedback

    Reply to a feedback item as a team member. The reply will be visible to the customer. Send follow-up info to the feedback author by setting `notifyCustomer` (emails them) and optionally adding up to 3 `attachments` (PNG/JPEG/WebP/GIF screenshots, 3 MB each) that appear in the em…

  • report_issue

    Report an error, bug, or feature request with MCP tools or suggest improvements. Reports that contain personal data, secrets, or chat transcripts are kept private automatically.

  • link_feedback_to_task

    Link feedback items to an existing roadmap task. Linked feedback status follows the task and followers are notified once the task is past backlog, the same as linking from the dashboard. To link while creating a task, pass `feedbackIds` to `create_task`. Already-linked and unkno…

  • list_pages

    List content pages and database pages for a project. Database row pages are included with their parentId.

  • search_pages

    Search pages and linked project knowledge by title/content.

  • get_page

    Read a page, including live content, linked people, propertyValues keyed by property ID, and update timestamp for conflict-safe edits. Full data is included in text and structured output.

  • create_page

    Create a normal page, database page, or database row page. For rows, pass parentId as the database page ID and propertyValues by property ID.

  • update_page

    Update page title, icon, content, content width, kind, agent visibility, or linked people. If ifUpdatedAt is omitted, the tool reads the latest page timestamp first.

  • move_page

    Move a page under another page/database or reorder it. Use parentId null for a top-level page.

  • duplicate_page

    Duplicate a page, including database row property values and linked people.

  • archive_page

    Archive a page and its child pages. This is a soft delete.

Headers

NameDescription
Authorization
Required, secret
Damper API key (dmp_…), created in the Damper dashboard under Settings → API keys, scoped to one project or the whole account.

Details

Endpointhttps://api.usedamper.com/mcp (Streamable HTTP)
First published30 Oct 2026
Last updated30 Oct 2026
Registry namecom.usedamper/mcp

More productivity servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.