S3 / MCP
Open source / Object storage

MCP servers & CLIs
for Russian S3 storage.

An MCP server, command-line client and agent skill in one Go binary. Seven cloud profiles share file transfer code and access controls.

7 providers Go · MIT Claude Code · Cursor · Codex

Project directory

Start with your cloud repository. Each has Russian and English guides, command examples, API research and a compatibility table.

01 / SELECTEL

Selectel

Pool selection and backup recovery

Six profile pools; tagging and lifecycle tools are disabled.

02 / YANDEX

Yandex Cloud

Object inventory and backup version inspection

ru-central1; profile restrictions apply to no-overwrite writes.

03 / VKCLOUD

VK Cloud

Hotbox/Icebox inspection and regional access

ru-msk and kz-ast pools; bucket tagging is disabled.

04 / CLOUDRU

Cloud.ru

Evolution Object Storage access diagnostics

Evolution, s3.cloud.ru, ru-central-1; not an Advanced profile.

05 / TIMEWEB

Timeweb Cloud

Archive recovery and bounded prefix usage

Bucket plans are chosen in the console; PUT Object Lock config is disabled.

06 / MWS

MWS

HMAC access checks and short-lived archive URLs

Cloud Platform, storage.mwsapis.ru; ACL is disabled.

07 / BEGET

Beget

Browse and restore files from an existing bucket

Buckets and share links use the console; presign and bucket API are disabled.

Get started

01

Build the binary

Clone your provider repository. Until binary releases are published, use the Docker build command in its README.

02

Configure access

Create a key in your cloud and save it with auth set. Choose the bucket and confine access to a prefix.

03

Connect MCP

Install the Claude Code, Cursor or Codex configuration. Start with object listing and read access.

Example: Yandex Cloud + Codex

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.

Project status. Code and emulator checks are published. Live cloud verification requires owner-provided credentials; binary releases, OCI images and MCP Registry publication remain pending. See each repository for profile limits. TASKS.md →

Before you connect

Which S3 providers are included?

Selectel, Yandex Cloud, VK Cloud, Cloud.ru Evolution, Timeweb Cloud, MWS Cloud Platform and Beget. Each has its own binary, profile and documentation.

How do I connect S3 to Claude Code, Cursor or Codex?

Build your provider binary, save credentials with auth set and run mcp install for the client. Each README lists commands and configuration locations.

Can an AI agent delete my files?

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.

Does this replace aws-cli or rclone?

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.

Does every cloud expose the same API?

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.

Where can I find prices and presigned URL limits?

Read provider research with official sources. Prices and unverified values are marked in the repositories; this directory is not a price offer.