get_feedback_attachment — Damper MCP Tool Read-only
get_feedback_attachment
(get feedback attachment) is one of 141 tools on the
Damper
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_feedback_attachment from your client
- Claude Code Damper get_feedback_attachment run in your project directory
- Claude Desktop Damper get_feedback_attachment ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Damper get_feedback_attachment ~/.cursor/mcp.json
- VS Code Damper get_feedback_attachment .vscode/mcp.json
- Zed Damper get_feedback_attachment ~/.config/zed/settings.json
- Windsurf Damper get_feedback_attachment ~/.codeium/windsurf/mcp_config.json
- Cline Damper get_feedback_attachment ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Damper get_feedback_attachment ~/.gemini/settings.json
- Grok Damper get_feedback_attachment .mcp.json (in your project root)
- ChatGPT Damper get_feedback_attachment Settings → Connectors → Advanced → Developer mode
- Claude.ai Damper get_feedback_attachment Settings → Connectors → Add custom connector
- LangChain Damper get_feedback_attachment pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://api.usedamper.com/mcpOther tools on this server
- 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
- delete_subtask
- delete_task
- add_task_dependency
- remove_task_dependency
- add_api_example
- add_screenshot
- add_diagram
- list_review_artifacts
- remove_review_artifact
- start_task
- review_task
- complete_task
- request_review
- abandon_task
- list_context_sections
- resolve_context
- get_context_section
- update_context_section
- delete_context_section
- sync_project_context
- get_project_context
- get_section_blocks
- get_section_block_content
- prepare_work
- audit_context_health
- get_context_graph
- resolve_context_graph
- list_context_relations
- upsert_context_relation
- delete_context_relation
- list_context_routes
- upsert_context_route
- delete_context_route
- preview_context_route_migration
- validate_context_routing
- compare_context_resolution
- list_context_bundles
- upsert_context_bundle
- get_context_bundle
- delete_context_bundle
- list_context_fixtures
- upsert_context_fixture
- report_context_feedback
- delete_context_fixture
- prepare_completion
- preview_context_update
- patch_context_section
- upsert_context_block
- verify_context_section
- render_context_routes_markdown
- list_context_maintenance_candidates
- refresh_context_maintenance_candidates
- convert_context_maintenance_candidate
- list_feedback
- get_feedback
- update_feedback
- reply_to_feedback
- report_issue
- link_feedback_to_task
- list_pages
- search_pages
- get_page
- create_page
- update_page
- move_page
- duplicate_page
- archive_page
- get_page_database
- get_page_database_schema
- query_page_database
- upsert_database_row
- create_task_from_page
- create_database_property
- update_database_property
- update_database_row_values
- update_database_view
- create_database_view
- delete_database_view
- create_database_template
- get_page_backlinks
- list_templates
- get_template
- update_template
- sync_templates
- list_modules
- get_module
- update_module
- sync_modules
- delete_module
- list_changelogs
- create_changelog
- update_changelog
- add_to_changelog
- publish_changelog
- delete_changelog
- get_completion_checklist
- patch_completion_checklist
- preview_completion_checklist_migration
- get_project_settings
- update_project_settings
- open_public_page
- list_status_maintenance_targets
- list_status_maintenance
- create_status_maintenance
- update_status_maintenance
- delete_status_maintenance
- add_status_maintenance_update
- edit_status_maintenance_update
- get_status_summary
- get_status_history
- list_status_groups
- create_status_group
- update_status_group
- delete_status_group
- list_status_checks
- create_status_check
- update_status_check
- delete_status_check
- run_status_check
- list_status_incidents
- create_status_incident
- update_status_incident
- delete_status_incident
- add_status_incident_update
- list_status_alert_recipients
- create_status_alert_recipient
- update_status_alert_recipient
- delete_status_alert_recipient
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.