iter0_reply_to_feedback — iter0 MCP Tool
iter0_reply_to_feedback
(iter0 reply to feedback) is one of 23 tools on the
iter0
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call iter0_reply_to_feedback from your client
- Claude Code iter0 iter0_reply_to_feedback run in your project directory
- Claude Desktop iter0 iter0_reply_to_feedback ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor iter0 iter0_reply_to_feedback ~/.cursor/mcp.json
- VS Code iter0 iter0_reply_to_feedback .vscode/mcp.json
- Zed iter0 iter0_reply_to_feedback ~/.config/zed/settings.json
- Windsurf iter0 iter0_reply_to_feedback ~/.codeium/windsurf/mcp_config.json
- Cline iter0 iter0_reply_to_feedback ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI iter0 iter0_reply_to_feedback ~/.gemini/settings.json
- Grok iter0 iter0_reply_to_feedback .mcp.json (in your project root)
- ChatGPT iter0 iter0_reply_to_feedback Settings → Connectors → Advanced → Developer mode
- Claude.ai iter0 iter0_reply_to_feedback Settings → Connectors → Add custom connector
- LangChain iter0 iter0_reply_to_feedback pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http iter0-mcp https://iter0.com/api/mcp
Other tools on this server
- iter0_health
- iter0_create_site
- iter0_edit_site
- iter0_get_site_status
- iter0_get_developer_docs
- iter0_show_three
- iter0_get_design_set_status
- iter0_confirm_paid_action
- iter0_open_builder
- iter0_list_my_designs
- iter0_get_design
- iter0_design_layout
- iter0_restore_version
- iter0_undo_edit
- iter0_check_site
- iter0_publish_site
- iter0_unpublish_site
- iter0_publish_status
- iter0_push_site
- iter0_get_canvas_feedback
- iter0_read_canvas_page
- iter0_get_canvas_snapshot
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.