run_code_in_vm — floot MCP Tool Mutating
run_code_in_vm
(run code in vm) is one of 45 tools on the
floot
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call run_code_in_vm from your client
- Claude Code floot run_code_in_vm run in your project directory
- Claude Desktop floot run_code_in_vm ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor floot run_code_in_vm ~/.cursor/mcp.json
- VS Code floot run_code_in_vm .vscode/mcp.json
- Zed floot run_code_in_vm ~/.config/zed/settings.json
- Windsurf floot run_code_in_vm ~/.codeium/windsurf/mcp_config.json
- Cline floot run_code_in_vm ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI floot run_code_in_vm ~/.gemini/settings.json
- Grok floot run_code_in_vm .mcp.json (in your project root)
- ChatGPT floot run_code_in_vm Settings → Connectors → Advanced → Developer mode
- Claude.ai floot run_code_in_vm Settings → Connectors → Add custom connector
- LangChain floot run_code_in_vm pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http floot https://mcp.floot.com/mcp
Other tools on this server
- search
- fetch
- list_projects
- list_resources
- list_files
- read_file
- read_files
- search_code
- get_guides
- get_guide
- write_file
- edit_file
- delete_file
- remove_dependency
- create_project
- apply_patch
- get_logs
- typecheck
- run_tests
- add_dependency
- run_code_in_browser
- navigate_preview
- screenshot_preview
- get_current_context
- view_annotation
- get_job_status
- rename_file
- copy_file
- query_database
- execute_sql
- pull_database_schema
- create_checkpoint
- update_project_metadata
- generate_image
- upload_asset
- request_user_upload
- card_upload_asset
- provision_resource
- request_external_resource
- get_publish_status
- publish_app
- unpublish_app
- cancel_request
- get_preview_url
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.