Proposal: extend with Cloud API tools (Servers, Account) — would you accept a PR?

[artgas1]

Hi team! 👋

I'm using timeweb-mcp-server via Claude Code MCP to manage our infrastructure. The current tools cover Apps Platform well (~5 tools), but I keep falling back to raw curl for Cloud API operations — checking VPS state, account balance, reboots, snapshots. This defeats the purpose of having an MCP integration.

I'd like to contribute support for Cloud API tools and would prefer to land it upstream rather than maintain a fork. Before I start — would you accept a PR along these lines?

Proposed scope (first PR, MVP)

Servers (VPS):

• list_servers, get_server
• reboot_server, start_server, shutdown_server
• resize_server (change preset)
• list_server_snapshots, create_server_snapshot, delete_server_snapshot
• get_server_logs

Account:

• get_account_finances
• get_account_status

Technical approach

• Generate tool scaffolds from the official OpenAPI spec at https://timeweb.cloud/api-docs-data/bundle.json
• Hand-polish descriptions for the top tools (machine-generated descriptions are usually a bad MCP UX)
• Smoke tests against read-only endpoints (list, get) using a real TIMEWEB_CLOUD_TOKEN
• Keep existing Apps Platform tools and code structure unchanged
• Auth: reuse existing TIMEWEB_CLOUD_TOKEN env var

I saw you recently added DBaaS, VPC, and Floating IP tools — happy to align with whatever code patterns you established there.

Follow-up PRs (out of scope for first PR)

Databases, S3, DNS, Firewalls, SSH keys, Kubernetes, Load Balancers — would split into separate PRs so review stays manageable.

One request 🙏

Could you add a LICENSE file (MIT / Apache-2.0 / whatever you prefer)? The repo currently has no explicit license, which makes it hard for others to contribute confidently or build on the code.

Happy to adjust the scope or approach based on your preferences. Let me know if this direction works for you!