startBackupExport — Pixly MCP Tool
startBackupExport
(start backup export) is one of 44 tools on the
Pixly
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call startBackupExport from your client
- Claude Code Pixly startBackupExport run in your project directory
- Claude Desktop Pixly startBackupExport ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Pixly startBackupExport ~/.cursor/mcp.json
- VS Code Pixly startBackupExport .vscode/mcp.json
- Zed Pixly startBackupExport ~/.config/zed/settings.json
- Windsurf Pixly startBackupExport ~/.codeium/windsurf/mcp_config.json
- Cline Pixly startBackupExport ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Pixly startBackupExport ~/.gemini/settings.json
- Grok Pixly startBackupExport .mcp.json (in your project root)
- ChatGPT Pixly startBackupExport Settings → Connectors → Advanced → Developer mode
- Claude.ai Pixly startBackupExport Settings → Connectors → Add custom connector
- LangChain Pixly startBackupExport pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://pixly.gg/api/mcp
Other tools on this server
- getBedrockRange
- listBills
- getMonthSpending
- getLoaderVersions
- getPricingCatalog
- listServers
- createServer
- deleteServer
- updateServer
- startAssetUpload
- abortAssetUploads
- completeAssetUploads
- inspectAssetUpload
- deleteAsset
- listBackups
- createBackup
- deleteBackup
- getBackupDownloadUrl
- deleteBackupExport
- cancelBackupRestore
- restoreBackup
- getConsoleLogs
- verifyCustomDomain
- dismissJoinAttempt
- keepServerAwake
- getServerMetrics
- deleteModpack
- startModpackUpload
- abortModpackUpload
- completeModpackUpload
- inspectModpackUpload
- resetServer
- setResourcePack
- restartServer
- restartToApplySettings
- startServer
- stopServer
- startWorldUpload
- abortWorldUpload
- completeWorldUpload
- refreshWorldUploadParts
- getServerUsage
- getBalance
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.