list_scheduled_syncs — CloudBridge MCP Tool Read-only
list_scheduled_syncs
(list scheduled syncs) is one of 26 tools on the
CloudBridge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_scheduled_syncs from your client
- Claude Code CloudBridge list_scheduled_syncs run in your project directory
- Claude Desktop CloudBridge list_scheduled_syncs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CloudBridge list_scheduled_syncs ~/.cursor/mcp.json
- VS Code CloudBridge list_scheduled_syncs .vscode/mcp.json
- Zed CloudBridge list_scheduled_syncs ~/.config/zed/settings.json
- Windsurf CloudBridge list_scheduled_syncs ~/.codeium/windsurf/mcp_config.json
- Cline CloudBridge list_scheduled_syncs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CloudBridge list_scheduled_syncs ~/.gemini/settings.json
- Grok CloudBridge list_scheduled_syncs .mcp.json (in your project root)
- ChatGPT CloudBridge list_scheduled_syncs Settings → Connectors → Advanced → Developer mode
- Claude.ai CloudBridge list_scheduled_syncs Settings → Connectors → Add custom connector
- LangChain CloudBridge list_scheduled_syncs pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cloudbridge https://cloud-bridge.ru/api/mcpOther tools on this server
- list_clouds
- list_files
- list_transfers
- get_transfer
- get_usage
- list_share_links
- get_download_url
- read_text_file
- list_dedup_scans
- get_dedup_scan
- create_transfer
- cancel_transfer
- remote_upload
- create_share_link
- revoke_share_link
- start_dedup_scan
- execute_dedup
- cancel_dedup_scan
- create_scheduled_sync
- update_scheduled_sync
- delete_scheduled_sync
- run_scheduled_sync
- move_file
- create_folder
- delete_file
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.