MCP Documentation
Complete reference for the Damper MCP server. Connect your AI assistant, authenticate with your API key, and use the current hosted toolset for task management, project context, feedback, and more.
Add the Damper MCP server to your AI assistant. The server uses streamable HTTP transport — no local installation required.
Recommended WorkflowAI agents should follow this structured workflow for best results. The workflow ensures agents have full context before coding and properly track their progress.
Project ContextShranite in pridobite projektno dokumentacijo, ki agentom UI pomaga razumeti kodno zbirko. Kontekst je organiziran v poimenovane razdelke (npr. pregled, konvencije, testiranje) in ga je mogoče razrešiti iz datotek, ki jih bo sprememba verjetno zajela.
Task ManagementCore tools for working with tasks. Agents pick tasks, lock them to prevent conflicts, track progress, and mark work complete.
Setup
Add the Damper MCP server to your AI assistant. The server uses streamable HTTP transport — no local installation required.
{
"mcpServers": {
"damper": {
"type": "http",
"url": "https://api.usedamper.com/mcp",
"headers": {
"Authorization": "Bearer dmp_..."
}
}
}
}Authentication
All MCP requests are authenticated via your API key in the Authorization header.
Authorization: Bearer dmp_your_api_key
Recommended Workflow
AI agents should follow this structured workflow for best results. The workflow ensures agents have full context before coding and properly track their progress.
- Call
list_projectsif you do not already know the Damper project ID for this repo or task. - Pokličite
get_project_contextza indeks projekta in kritična pravila, pomembna za nalogo. Za razvoj funkcionalnosti pokličite samo-za-branjeprepare_workz verjetnimi datotekami in preglejte fixtureCoverage za vsako pot; za manjše delo uporabiteresolve_context. Rezervne predloge preverite glede na natančen kontekst in kodo. - Call
list_tasksto see available tasks sorted by priority. - Call
start_taskto lock a task and receive its full spec and project context. - Work on the task. Use
add_noteandadd_committo track progress. - When finished, load the relevant checklist branches, then call
complete_taskwith itemId-based confirmations and evidence fordoneitems, orabandon_taskwith a handoff summary.
Task Management
Core tools for working with tasks. Agents pick tasks, lock them to prevent conflicts, track progress, and mark work complete.
| Tool | Description |
|---|---|
list_tasks | Prikažite naloge z neobveznim filtriranjem po stanju, vrsti ali oznaki. Pred oštevilčenim pregledovanjem uporabite query za iskanje po naslovih, opisih, izvedbenih načrtih, uporabniških zgodbah ali natančnih oznakah. Rezultati so razvrščeni po prednosti (uteženem rezultatu povpraševanja) in vsebujejo razpoložljive datume nastanka, posodobitve in roka. |
get_task | Get full task details including description, implementation plan, subtasks, notes, and linked feedback. |
create_task | Create a new task with title, description, type, and optional implementation plan. |
update_task | Update task fields like title, description, status, type, labels, or effort estimate. |
delete_task | Delete a planned task that has no commits. Use with care; this is permanent. |
start_task | Lock a task for the current agent. Returns the task spec, project context, and critical rules. Prevents other agents from working on it. |
add_note | Add a progress note to a task. Use for decisions, observations, or status updates. Notes are visible to future agents. |
add_commit | Record a git commit against a task. Pass the commit hash and message. Helps track what code was written. |
complete_task | Mark a task as complete and release the lock. Requires itemId-based checklist confirmations with structured proof for done items and explicit checklistScope dimensions when appliesTo, when, or riskDomains rules are used. |
abandon_task | Release a task lock without completing it. Requires a handoff summary describing what was done and what remains. |
Subtasks
Break large tasks into smaller pieces. Agents check off subtasks as they complete each part, giving visibility into progress.
| Tool | Description |
|---|---|
create_subtask | Dodajte podnalogo kontrolnega seznama k nalogi. Navedite naslov. |
update_subtask | Označite podnalogo kot dokončano ali nedokončano. |
delete_subtask | Remove a subtask from a task. |
Task Review
Request a review of completed work before finalizing.
| Tool | Description |
|---|---|
review_task | Submit a task for review with a summary of changes. Returns review feedback or approval. |
Project Context
Shranite in pridobite projektno dokumentacijo, ki agentom UI pomaga razumeti kodno zbirko. Kontekst je organiziran v poimenovane razdelke (npr. pregled, konvencije, testiranje) in ga je mogoče razrešiti iz datotek, ki jih bo sprememba verjetno zajela.
| Tool | Description |
|---|---|
get_project_context | Naložite indeks projektnega konteksta. Podajte taskId, kadar je znan. Možnost criticalRuleMode je privzeto relevant; uporabite all za nameren celovit pregled ali none za odgovor samo z indeksom. To pokličite najprej v vsaki seji. |
resolve_context | Razrešite verjetno spremenjene poti v kontekst in obseg kontrolnega seznama. Privzeti vrednosti sta fallbackMode=minimal in detailMode=compact; široki rezervni način in polne podrobnosti ostajajo na voljo zaradi združljivosti ali namernega raziskovanja. Kadar je mogoče, podajte znane changeKinds. Rezervni metapodatki in opozorila usmerjajo raziskovanje ter niso merodajna resnica, dokler jih ne preverite glede na natančen kontekst in kodo. |
prepare_work | Sestavite determinističen paket samo za branje s strnjenim fixtureCoverage za vsako pot. Stanje represented ima scope route_representation, validationStatus not_checked in scenarioCoverage not_inferred: representedBy in unrepresentedStructuredRoutes prikazujeta samo zastopanost poti, ne preverjenih trditev ali vseh scenarijev široke poti. Vsaka vrzel zahteva odločitev; kritične in pomembne vrzeli imajo requiredBeforeCompletion, svetovalne pa lahko dokumentirano utemeljitev. |
audit_context_health | Preverite veljavnost taksonomije, pokritost poti s primeri, šibke ali neuspešne primere, manjkajoče osnove, zastarel kontekst, prekrivanja in rezervne razrešitve. |
list_context_routes / upsert_context_route / compare_context_resolution | Upravljajte preverjene strukturirane poti. Strukturirana ujemanja imajo prednost, Markdown pa ostane migracijska rezerva. |
list_context_fixtures / upsert_context_fixture / validate_context_routing | Shranite pregledana pričakovanja, izpeljana iz nameravane projektne resnice in kode, nikoli s kopiranjem izhoda razreševalnika. Pred dodajanjem primera popravite nepreverjeno rezervno usmerjanje in pred zanašanjem na zastopanost zaženite validate_context_routing. Za bistveno drugačna tveganja, pogodbe, preverjanje ali medpovršinsko vedenje dodajte natančno pot in primer; primer široke poti ni dokaz scenarija. |
list_context_bundles / upsert_context_bundle | Upravljajte povezane razdelke, primere in profile preverjanja. Vsaka posodobitev ustvari nespremenljiv posnetek različice. |
report_context_feedback | Prijavite manjkajoč, nerelevanten ali napačno usmerjen kontekst brez shranjevanja pozivov ali izvorne kode. |
list_context_sections | List all context sections with their titles, tags, and appliesTo targets. |
get_context_section | Get the full content of a specific context section by name. Supports hierarchical paths (e.g., api/architecture) and wildcards (api/*). |
get_section_blocks | Get the heading structure of a large context section. Returns block titles for selective loading. |
get_section_block_content | Load a specific block from a context section by heading. Useful for token-efficient reading of large docs. |
update_context_section | Create or update a context section. Provide content, optional tags, appliesTo targets, and critical rules. |
delete_context_section | Remove a context section by name. |
sync_project_context | Sync project context from a local CLAUDE.md or similar file to Damper. Useful for initial setup. |
Feedback
Access user feedback and weighted votes to inform task priorities. Link feedback items to tasks to track what customer requests led to shipped features.
| Tool | Description |
|---|---|
list_feedback | List feedback items with optional filtering by type, status, or search query. Returns items with vote counts, demand scores, and available created, updated, first-seen, and last-seen dates. |
get_feedback | Get full feedback details including description, votes, voter tiers, and linked tasks. |
update_feedback | Update a feedback item's status, type, or internal notes. |
link_feedback_to_task | Link a feedback item to a task. When the task ships, feedback submitters can be notified. |
Code Templates
Maintain code consistency with reusable templates for services, components, tests, and other patterns. Templates teach AI agents your project's conventions.
| Tool | Description |
|---|---|
list_templates | List all code templates with their names, tags, and descriptions. |
get_template | Get the full content of a code template by name. |
update_template | Create or update a code template with content, tags, and description. |
sync_templates | Sync code templates from local files to Damper. Reads template files and uploads them. |
Module Registry
Track monorepo structure with package paths, ports, dependencies, and descriptions. Helps AI agents understand which package to modify.
| Tool | Description |
|---|---|
list_modules | List all registered modules with their paths, ports, and descriptions. |
get_module | Get full details of a module including dependencies and configuration. |
update_module | Create or update a module entry with path, port, description, and dependencies. |
sync_modules | Sync module registry from package.json files in the monorepo. |
Changelogs
Create and manage changelog entries. When AI agents complete public tasks, draft changelog entries are created automatically.
| Tool | Description |
|---|---|
list_changelogs | List changelog entries with optional filtering by status (draft, published). |
create_changelog | Create a new changelog entry with title, content, version, and linked tasks. |
update_changelog | Update an existing changelog entry's title, content, version, or status. |
add_to_changelog | Add completed tasks to an existing changelog entry; private tasks are shown publicly only as other updates. |
publish_changelog | Publish a draft changelog entry. Sends notifications to subscribers of linked roadmap items. |
delete_changelog | Delete a changelog entry. |
Settings & Utilities
Configure project settings, get agent-specific instructions, and access utility tools.
| Tool | Description |
|---|---|
get_project_settings | Get current project settings including the completion checklist index, standards refs, scope guidance, default labels, and notification preferences. |
update_project_settings | Update project settings like the structured completion checklist, standards refs, default task labels, or notification rules. |
get_agent_instructions | Get agent-specific instructions that should be followed during task execution. Includes critical rules and workflow guidance. |
report_issue | Report a bug or issue with the Damper platform. Useful for agents encountering unexpected behavior. |
open_public_page | Get the URL for a project's public page (roadmap, changelog, or feedback board). |