Selectel
Pool selection and backup recovery
Six profile pools; tagging and lifecycle tools are disabled.
An MCP server, command-line client and agent skill in one Go binary. Seven cloud profiles share file transfer code and access controls.
Start with your cloud repository. Each has Russian and English guides, command examples, API research and a compatibility table.
Pool selection and backup recovery
Six profile pools; tagging and lifecycle tools are disabled.
Object inventory and backup version inspection
ru-central1; profile restrictions apply to no-overwrite writes.
Hotbox/Icebox inspection and regional access
ru-msk and kz-ast pools; bucket tagging is disabled.
Evolution Object Storage access diagnostics
Evolution, s3.cloud.ru, ru-central-1; not an Advanced profile.
Archive recovery and bounded prefix usage
Bucket plans are chosen in the console; PUT Object Lock config is disabled.
HMAC access checks and short-lived archive URLs
Cloud Platform, storage.mwsapis.ru; ACL is disabled.
Browse and restore files from an existing bucket
Buckets and share links use the console; presign and bucket API are disabled.
MCP, CLI, access scope, confirmations, confined local files, audit and reusable checks.
Clone your provider repository. Until binary releases are published, use the Docker build command in its README.
Create a key in your cloud and save it with auth set. Choose the bucket and confine access to a prefix.
Install the Claude Code, Cursor or Codex configuration. Start with object listing and read access.
bash scripts/go.sh go build -o yandex-s3 ./cmd/yandex-s3
./yandex-s3 auth set
./yandex-s3 mcp install --client codex
Run from a cloned yandex-s3-mcp-ai-cli repository. Cloud calls require your own S3 key; auth set hides secret input.
Selectel, Yandex Cloud, VK Cloud, Cloud.ru Evolution, Timeweb Cloud, MWS Cloud Platform and Beget. Each has its own binary, profile and documentation.
Build your provider binary, save credentials with auth set and run mcp install for the client. Each README lists commands and configuration locations.
MCP starts read-only. Write, delete and admin levels are enabled separately; destructive actions use the configured approval policy. Also restrict the S3 key permissions, bucket and prefix.
These projects add MCP tools, agent skills and access controls. The CLI handles object operations and streaming restores; aws-cli and rclone remain independent automation tools.
No. Tools are registered by profile capabilities. For example, Beget bucket APIs and external presigning are disabled, while Cloud.ru targets Evolution. Check compat and live-test status.
Read provider research with official sources. Prices and unverified values are marked in the repositories; this directory is not a price offer.