cloudhosting_get_usage — CloudHostAI MCP Tool
cloudhosting_get_usage
(cloudhosting get usage) is one of 15 tools on the
CloudHostAI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call cloudhosting_get_usage from your client
- Claude Code CloudHostAI cloudhosting_get_usage run in your project directory
- Claude Desktop CloudHostAI cloudhosting_get_usage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CloudHostAI cloudhosting_get_usage ~/.cursor/mcp.json
- VS Code CloudHostAI cloudhosting_get_usage .vscode/mcp.json
- Zed CloudHostAI cloudhosting_get_usage ~/.config/zed/settings.json
- Windsurf CloudHostAI cloudhosting_get_usage ~/.codeium/windsurf/mcp_config.json
- Cline CloudHostAI cloudhosting_get_usage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CloudHostAI cloudhosting_get_usage ~/.gemini/settings.json
- Grok CloudHostAI cloudhosting_get_usage .mcp.json (in your project root)
- ChatGPT CloudHostAI cloudhosting_get_usage Settings → Connectors → Advanced → Developer mode
- Claude.ai CloudHostAI cloudhosting_get_usage Settings → Connectors → Add custom connector
- LangChain CloudHostAI cloudhosting_get_usage pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cloudhostai https://cloudhostai.eliteaiempire.com/mcpOther tools on this server
- cloudhosting_list_projects
- cloudhosting_get_project
- cloudhosting_get_project_status
- cloudhosting_list_deploys
- cloudhosting_get_logs
- cloudhosting_get_hetzner_status
- cloudhosting_export
- cloudhosting_get_account
- cloudhosting_create_project
- cloudhosting_deploy_project
- cloudhosting_destroy_server
- cloudhosting_delete_project
- cloudhosting_preview_deploy
- cloudhosting_get_pricing
This list was read from the server itself, by connecting to it and calling tools/list on 9 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.