Referenca MCP Damper

Damper izpostavi 100+ orodij prek gostujočega strežnika MCP s transportom streamable HTTP — brez lokalne namestitve. Agenti jih uporabljajo za naloge, razreševanje konteksta, branje strani in zbirk, odzivanje na povratne informacije in objavljanje izdaj.

Namestitev

Dodajte strežnik MCP Damper svojemu pomočniku AI. Uporablja transport streamable HTTP — ničesar za namestiti lokalno.

Claude Code

Dodajte v .mcp.json projekta ali globalni ~/.claude.json:

// .mcp.json or ~/.claude.json
{
  "mcpServers": {
    "damper": {
      "type": "http",
      "url": "https://api.usedamper.com/mcp",
      "headers": {
        "Authorization": "Bearer dmp_..."
      }
    }
  }
}

Cursor

Dodajte v .cursor/mcp.json v korenu projekta:

// .cursor/mcp.json
{
  "mcpServers": {
    "damper": {
      "type": "http",
      "url": "https://api.usedamper.com/mcp",
      "headers": {
        "Authorization": "Bearer dmp_..."
      }
    }
  }
}

Overjanje

Vse zahteve se overijo z vašim ključem API v glavi Authorization. Ključ najdete v nadzorni ploči pod Nastavitve → API ključi — ključi uporabljajo predpono dmp_.

Authorization: Bearer dmp_your_key_here

Priporočeni potek dela

Pripravite delo
get_agent_instructions nastavi vaš CLAUDE.md; prepare_work zgradi stisnjen paket dela z vladajočim kontekstom in primerjavo grafa.
Naloži kontekst
get_project_context ali resolve_context — arhitektura, pravila in razdelki, ki urejajo datoteke, ki se jih boste lotili.
Izberite in zaklenite nalogo
list_tasks razvršča po uteženem povpraševanju; start_task zaklene nalogo in vrne specifikacijo, povezane povratne informacije in kazalo kontrolnega seznama.
Sledite med delom
add_note za odločitve, add_commit za razpršilke in link_pr takoj, ko obstaja pull zahteva.
Zaključite z dokazi
get_completion_checklist, nato complete_task s potrditvijo za vsako postavko. Ali abandon_task s povzetkom predaje.
Dovolite, da se zanka zapre sama
Končane javne naloge samodejno pripravijo vnos dnevnika; publish_changelog obvesti naročnike in glasovalce.

Structured output schemas include task lifecycle messages, execution dates, summaries, review instructions, project details and feedback submitters; dependency project IDs and creation dates; and changelog dates and linked items. start_task and get_project_context share a context index schema with tags, appliesTo and exposed-page titles. Context sections include version and verification metadata; generated routing sections declare a string version, generated/readOnly flags and routeCount. Database reads include relationLabels, and row-value updates return updatedAt for conflict-safe edits.

Naloge

list_tasksTasks sorted by weighted demand score, filterable by status, type or label.

start_taskLock a task and receive its spec, linked feedback and project rules.

get_taskCompact by default (plan, current progress, subtasks, PRs, unresolved decisions, completion receipt) — request include sections like timeline or set detailMode: "full" for the legacy payload.

link_prLink the pull request that delivers the task — the primary deliverable, updated through merge.

add_noteRecord a decision or observation, or open/resolve a structured blocker or open question by kind.

update_taskEdit task fields, or replace the single currentProgress snapshot shown in compact retrieval.

complete_taskMark complete with evidence for every checklist item and a compact completion receipt; releases the lock.

create_task delete_task add_commit create_subtask update_subtask delete_subtask add_task_dependency remove_task_dependency review_task abandon_task list_self_assessments

Kontekst in graf

get_project_contextFull context summary — sections, critical rules, metadata. First call of every session.

resolve_contextMap touched file paths to governing sections, rules, risk domains and checklist scope.

resolve_context_graphBounded shadow-mode graph traversal — ranked candidates with full provenance.

validate_context_routingRun route fixtures against the production resolver before you rely on it.

get_context_graph compare_context_resolution list_context_sections get_context_section update_context_section patch_context_section delete_context_section verify_context_section sync_project_context get_section_blocks get_section_block_content list_context_routes upsert_context_route delete_context_route preview_context_route_migration render_context_routes_markdown list_context_relations upsert_context_relation delete_context_relation list_context_bundles get_context_bundle upsert_context_bundle delete_context_bundle list_context_fixtures upsert_context_fixture delete_context_fixture audit_context_health list_context_maintenance_candidates refresh_context_maintenance_candidates convert_context_maintenance_candidate preview_context_update report_context_feedback upsert_context_block

Osvežitev konteksta s pomočjo repozitorija

Ob prvi nastavitvi ali po večji združitvi pripravite osnutek konteksta lokalno za pregled. Repomix lokalno ustvari paket izvorne kode in ga pošlje izbranemu agentu ali ponudniku; Damper prejme le predlagane razdelke in zaupanja vredne metapodatke priprave.

Odgovori MCP za kontekst lahko vsebujejo neobvezne napotke za svežino: manjkajoča potrditev lahko predlaga nastavitev, znane spremembe ali izbrisi upravljanih razdelkov pa preverjanje samo za branje in pregledano osvežitev. Pri veljavni potrditvi napotkov ni. MCP ne more pregledati vašega delovnega drevesa ali izvorne kode, zato preverjanje zaženite lokalno; nikoli ne objavi samodejno.

Pripravite lokalno
damper context prepare --agent claude --repository-key default
Preglejte osnutek
Uvozite JSON osnutek v AI Context in preglejte vsebino prej/potem, oznake, appliesTo in kritična pravila. Izpuščeni razdelki ostanejo nespremenjeni.
Izrecno objavite
Objavite šele po pregledu. Strežnik preveri projekt, ključ repozitorija, različice razdelkov in potrditev; zastareli osnutki ne uspejo brez delnega zapisa. Potek ne dodaja MCP orodij in nikoli samodejno ne prepiše konteksta.
Preverite svežino
damper context check --repository-key default

Preverjanje samo za branje zaženite ročno, po urniku ali po tem, ko privzeta veja prejme večjo združitev. Uporabite ga kot nadaljnjo izdajno/namestitveno zaporo; osvežite združeno delovno drevo, preglejte in objavite, nato preverjanje ponovite. Za avtomatizacijo pripnite različico CLI in objavo ohranite kot ločen pregledan korak.

Strani in zbirke

Celotni delovni prostor strani — z omejenim branjem, nadaljevalnim poizvedovanjem in ponovitveno varnimi zapisi za rastoče zbirke.

list_pages / search_pagesBrowse or full-text search every page, database and row in the project.

query_page_databaseFilter and project bounded row pages. With the default updatedAt ascending sort, save the returned resume cursor for incremental polls; in matches any supplied array member and contains requires all.

upsert_database_rowCreate or update one row by a canonical key unique within its parent database; unchanged retries are no-ops.

get_page_database_schemaRead every property ID, name, type and options, plus complete views and templates, in text and structured output without loading rows.

get_page_databaseRead the complete database and all row propertyValues keyed by property ID in text and structured output. Use for small databases or intentional full audits.

create_task_from_pageTurn a page into a roadmap task — links back and updates the row's roadmap property.

Database read tools include full JSON in text and structured output. get_page also includes row propertyValues keyed by property ID; query_page_database preserves the requested property/content projection.

Date values use YYYY-MM-DD strings, for example 2026-09-13; use null to clear them. Timestamp strings are reduced to their first ten characters without timezone conversion. For overdue rows, filter with { propertyId: reviewDateId, operator: "less_than", value: "2026-09-13" } and sort with { propertyId: reviewDateId, direction: "asc" }.

Sort by exactly one metadata field (createdAt or updatedAt) or a custom date propertyId. Empty dates sort last in both directions; row IDs break ties. Reuse cursors with the same sort. Only updatedAt ascending (the default) supports incremental change polling; cursors for other sorts are for pagination only.

get_page create_page update_page move_page duplicate_page archive_page get_page_backlinks create_database_property update_database_property update_database_row_values create_database_view update_database_view delete_database_view create_database_template

Povratne informacije

list_feedback / get_feedbackItems with descriptions, sources, vote scores, AI summaries, occurrence counts, dates and linked tasks. Detail includes voter/comment dates and attachment URLs, with raw attachment data omitted.

update_feedbackUpdate status or visibility. Returns id, title, status, type and isPublic, including when no changes are supplied.

reply_to_feedbackAnswer as a team member — the reply is visible to the customer.

link_feedback_to_taskConnect requests to work; submitters get notified when it ships.

report_issue

Izdaje

publish_changelogPublish a draft and notify subscribers of linked roadmap items.

list_changelogs create_changelog update_changelog add_to_changelog delete_changelog

Status page maintenance

list_status_maintenance_targetsDiscover group and monitor IDs, names and visibility for choosing affected components.

list_status_maintenanceRead maintenance windows, schedules, visibility and timeline updates, newest first.

create_status_maintenance / update_status_maintenanceSchedule maintenance or edit its details, scope and visibility. Dates use ISO 8601 UTC. Choose groupId or checkIds, never both. Omit both on creation for all monitors; omit both on edit to preserve scope, or set both to null for all monitors.

add_status_maintenance_updatePost progress and set state to scheduled, in_progress, completed or cancelled. Pass expectedState and expectedIsPublic from the latest read for conflict detection. Reuse a requestId UUID when retrying the same post.

edit_status_maintenance_updateCorrect a timeline message using maintenanceId and updateId. Historical state and visibility remain unchanged; no subscriber notification is sent.

delete_status_maintenancePermanently delete the window and timeline. Post a cancelled update instead to retain history.

All tools require projectId and follow API-key project access. Creation and timeline posts default to public; posts also default to notifying subscribers. Use isPublic: false for private work and notifySubscribers: false to suppress timeline notifications. Public window creation, edits and opted-in timeline posts queue durable subscriber notifications with background retries. A successful save confirms that the change and notification queue are committed, not that email has been delivered. Private windows still suppress monitoring alerts, and private updates cannot change the state of public maintenance.

{
  "name": "create_status_maintenance",
  "arguments": {
    "projectId": "YOUR_PROJECT_ID",
    "title": "Database upgrade",
    "scheduledStartAt": "2030-01-01T10:00:00Z",
    "scheduledEndAt": "2030-01-01T11:00:00Z",
    "isPublic": false
  }
}

Predloge in moduli

list_templates get_template update_template sync_templates list_modules get_module update_module sync_modules delete_module

Projekti in potek dela

list_projects vrne ID-je, imena in URL-oznake dostopnih projektov, časovne oznake createdAt v obliki ISO ter število nalog in povratnih informacij. Indeks get_project_context za strani, ki so na voljo agentom, vključuje tudi neobvezno polje title. Obe orodji te metapodatke določata v shemah strukturiranih izhodnih podatkov.

prepare_work / prepare_completionDeterministic work packets on the way in; drift and scope checks on the way out.

get_completion_checklistDetailed checklist branches to satisfy before completing a task.

open_public_pageThe correct public URL for roadmap, feedback, changelog or a roadmap item — never guess URLs.

list_projects get_agent_instructions get_project_settings update_project_settings patch_completion_checklist preview_completion_checklist_migration

Usmerite svojega agenta nanj.

En URL, en ključ, sto orodij. Vaš načrt je že seznam nalog.

Pridobite ključ API Nazaj na dokumentacijo