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