update_file_content — vibedeploy MCP Tool Mutating
update_file_content
(update file content) is one of 39 tools on the
vibedeploy
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call update_file_content from your client
- Claude Code vibedeploy update_file_content run in your project directory
- Claude Desktop vibedeploy update_file_content ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor vibedeploy update_file_content ~/.cursor/mcp.json
- VS Code vibedeploy update_file_content .vscode/mcp.json
- Zed vibedeploy update_file_content ~/.config/zed/settings.json
- Windsurf vibedeploy update_file_content ~/.codeium/windsurf/mcp_config.json
- Cline vibedeploy update_file_content ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI vibedeploy update_file_content ~/.gemini/settings.json
- Grok vibedeploy update_file_content .mcp.json (in your project root)
- ChatGPT vibedeploy update_file_content Settings → Connectors → Advanced → Developer mode
- Claude.ai vibedeploy update_file_content Settings → Connectors → Add custom connector
- LangChain vibedeploy update_file_content pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vibedeploy https://mcp.vibedeploy.be/mcp
Other tools on this server
- get_account
- deploy_site
- update_site
- list_sites
- get_site
- delete_site
- get_site_analytics
- read_file
- read_files
- list_file_hashes
- list_source_files
- read_source_file
- read_source_files
- write_source_files
- delete_source_file
- build_and_deploy
- search_files
- deploy_from_url
- rehost_images
- apply_edits
- get_forms_config
- set_forms_config
- verify_forms_sender_domain
- add_custom_domain
- verify_custom_domain
- remove_custom_domain
- list_custom_domains
- list_dns_records
- check_domain_availability
- begin_deploy
- add_files
- add_file_chunk
- commit_deploy
- abort_deploy
- list_deploys
- list_history
- list_snapshots
- create_snapshot
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.