# Usedamper MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.usedamper%2Fmcp
Registry id: `mcp-registry/com.usedamper/mcp`
Status: live (checked 2026-11-22T17:14:07.084Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 941
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "usedamper-mcp-server": {
      "type": "http",
      "url": "https://api.usedamper.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http usedamper-mcp-server https://api.usedamper.com/mcp
```

## Tools (141)

- `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:** Wh
- `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 p
- `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 h
- `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 w
- `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,
- `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 (defa
- `add_status_incident_update`: Post a timeline message and move the incident to investigating, identified, monitoring or resolved. resolvedAt is only valid with stage resolved. Private update
- `add_status_maintenance_update`: Post a timeline message and transition state (scheduled, in_progress, completed or cancelled). isPublic and notifySubscribers default to true. Private updates c
- `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 b
- `add_to_changelog`: Add completed tasks to a changelog. Private tasks can be linked; their titles/descriptions are not exposed in public changelog output and are surfaced as an "ot
- `archive_page`: Archive a page and its child pages. This is a soft delete.
- `audit_context_health`: Find invalid route taxonomy, weak or uncovered fixtures, missing baselines, route overlap, stale knowledge, and fallback usage.
- `compare_context_resolution`: Compare structured routing output with legacy Markdown routing for repository paths.
- `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 expl
- `convert_context_maintenance_candidate`: Convert a candidate into a deduplicated private context-maintenance roadmap task.
- `create_changelog`: Create a new changelog entry.
- `create_database_property`: Add a property column to a page database. Property type. Relation types: `page` (linked page IDs), `roadmap` (linked roadmap task IDs), `feedback` (linked feedb
- `create_database_template`: Create a database-level page template with content and default property values.
- `create_database_view`: Create a saved database view with table, list, board, or calendar layout.
- `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.
- `create_status_alert_recipient`: Add an alert recipient. type user_email and voice_call need userId (an account user; voice calls need a verified phone with urgent calls enabled), email needs e
- `create_status_check`: Create an http, ssl or heartbeat monitor in a group. http and ssl monitors require a public url; heartbeat monitors return a heartbeatUrl for your job to ping. 
- `create_status_group`: Create a status page group (component). slug is lowercase letters, digits and dashes, unique per project. isPublic defaults to true.
- `create_status_incident`: Open a manual incident, optionally tied to a groupId or checkId. Dates use ISO 8601 UTC. initialUpdateMessage (or summary) becomes the first timeline update. is
- `create_status_maintenance`: Create a scheduled status-page maintenance window. Dates use ISO 8601 UTC. Use list_status_maintenance_targets to choose groupId or checkIds (mutually exclusive
- `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 roadm
- `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 i
- `create_task_from_page`: Create a roadmap task from a page. Copies the page title and content excerpt into the task, links the page as a source backlink, and updates a `roadmap` databas
- `delete_changelog`: Permanently delete a changelog entry.
- `delete_context_bundle`: Delete a context bundle and its version history.
- `delete_context_fixture`: Delete an executable routing fixture by name.
- `delete_context_relation`: Delete a project-authored context relationship. Derived graph edges are not mutable through this tool.
- `delete_context_route`: Delete a structured context route by name.
- `delete_context_section`: Delete a project context section. Use when documentation is outdated or no longer relevant.
- `delete_database_view`: Delete a saved database view. A database must keep at least one view.
- `delete_module`: Delete a registered module by name.
- `delete_status_alert_recipient`: Permanently remove an alert recipient.
- `delete_status_check`: Permanently delete a monitor with its results and monitor-specific alert recipients. Set isEnabled false with update_status_check to pause instead.
- `delete_status_group`: Permanently delete a group together with its monitors and their results. Scheduled or in-progress maintenance for the group is cancelled.
- `delete_status_incident`: Permanently delete an incident and its timeline. For a monitor incident, results recorded during it are cleared so uptime is recalculated. To keep history, post
- `delete_status_maintenance`: Permanently delete a maintenance window and its timeline. To retain history, use add_status_maintenance_update with state cancelled instead.
- `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.
- `duplicate_page`: Duplicate a page, including database row property values and linked people.
- `edit_status_maintenance_update`: Correct a historical maintenance timeline message only. State and visibility remain immutable; this does not send subscriber notifications.
- `get_agent_instructions`: Get the canonical Damper workflow instructions. Use this to set up or update CLAUDE.md in a project.
- `get_completion_checklist`: Load detailed completion checklist branches for the project. Use after `start_task` or `review_task` because those only return a checklist index. Filters: `grou
- `get_context_bundle`: Get a context bundle with immutable version snapshots, optionally selecting one version.
- `get_context_graph`: Inspect the typed graph projection derived from context routes, sections, bundles, modules, and optional project-authored relationships.
- `get_context_section`: Get full content of a specific context section. Supports glob patterns for hierarchical sections. **Hierarchical paths**: For monorepos or large projects, secti
- `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_
- `get_module`: Get details of a specific module.
- `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 
- `get_page_backlinks`: List pages that link to a page.
- `get_page_database`: Read the complete database definition and every row, including property IDs, names, types, options and propertyValues keyed by property ID in text and structure
- `get_page_database_schema`: Read all property IDs, names, types, options, views, and templates without downloading rows. Full definitions are included in text and structured output.
- `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. **IMPORTAN
- `get_project_settings`: View current project settings, including the completion checklist index, standards refs, scope guidance, and the review evidence policy: per kind (apiExamples, 
- `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.
- `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_status_history`: Uptime history for a window (24h, 7d, 30d or 90d; default 90d) as bucketed points. Filter by groupId or checkId; without checkId only monitors included in uptim
- `get_status_summary`: Overall status page health: overall state, per-group state, monitor counts, active incidents and 24h/90d uptime (0-1, null without data). Maintenance windows sh
- `get_task`: Get task details. Defaults to a compact view (plan, current progress, subtasks, PRs, unresolved decisions, completion receipt, evidence counts) — no `agentNotes
- `get_template`: Get full content of a specific code template.
- `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 l
- `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: 
- `list_changelogs`: List changelogs for the project. Filter by status (draft, published).
- `list_context_bundles`: List versioned context bundles and recent versions.
- `list_context_fixtures`: List executable context routing expectations.
- `list_context_maintenance_candidates`: List the current deduplicated context-maintenance queue without refreshing or mutating it.
- `list_context_relations`: List project-authored typed relationships layered over the derived context graph.
- `list_context_routes`: List structured path-to-context routes in priority order.
- `list_context_sections`: List available project context sections with brief previews.
- `list_feedback`: Get user feedback. Useful for understanding user needs. Feedback summaries include available dates such as `createdAt`, `updatedAt`, `firstOccurredAt`, and `las
- `list_modules`: List registered modules in this monorepo.
- `list_pages`: List content pages and database pages for a project. Database row pages are included with their parentId.
- `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.
- `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 chec
- `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 conte
- `list_status_alert_recipients`: List who is alerted when monitors go down or recover: account users by email or voice call, external emails and Slack channels, for all monitors or one checkId.
- `list_status_checks`: List monitors (status checks) with type, target, schedule, current state and last run. Set includeDailyUptime for 30 days of daily uptime per monitor.
- `list_status_groups`: List status page groups (components) in display order with visibility and monitor/incident counts.
- `list_status_incidents`: List automated and manual incidents (open first, then newest) with affected component and timeline updates (newest first).
- `list_status_maintenance`: List maintenance windows, scope, schedules, visibility and timeline updates (newest first) for this project. Use the returned IDs to edit windows or timeline me
- `list_status_maintenance_targets`: List status-page groups and monitors for maintenance targeting. Returns identifiers, names and visibility without probe configuration.
- `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, 
- `list_templates`: List available code templates for this project.
- `move_page`: Move a page under another page/database or reorder it. Use parentId null for a top-level page.
- `open_public_page`: Get the public URL for a project page (roadmap, feedback, changelog, or a specific roadmap item). **IMPORTANT:** NEVER guess or construct public page URLs yours
- `patch_completion_checklist`: Apply a scoped patch to the project completion checklist, touching only the branches you name. Groups, items, subitems, and standards are matched by `id`; entri
- `patch_context_section`: Apply stable-block operations with optimistic concurrency and immutable version snapshots.
- `prepare_completion`: Resolve final touched paths, compare them with the prepare_work snapshot, detect version drift and scope expansion, and generate context disposition evidence. A
- `prepare_work`: Build a deterministic, compact work packet with governing context, a shadow graph comparison and provenance, path-owned surfaces, checklist scope, project verif
- `preview_completion_checklist_migration`: Preview how a legacy flat completion checklist could be regrouped into native V2. Flags broad items, command-dump style items, and title-derived ids before writ
- `preview_context_route_migration`: Parse Markdown routing into structured route candidates without writing them.
- `preview_context_update`: Preview a section replacement or stable-block patch, including semantic changes and sensitive-data warnings, without writing.
- `publish_changelog`: Publish a changelog with optional email and Twitter notifications.
- `query_page_database`: Read a bounded page of database rows using metadata or property filters, stable cursor pagination, a resumable polling cursor, and optional property/content pro
- `refresh_context_maintenance_candidates`: Aggregate privacy-safe feedback, self-assessment gaps, and fallback telemetry; may auto-create private tasks when project policy enables it.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
