This Yandex Cloud MCP server acts as a friendly bridge between the Claude AI desktop app and Yandex Cloud’s storage system. In simple terms, it gives the AI the ability to "look" inside cloud storage folders and manage files directly through a chat interface. Instead of a user having to manually download data and upload it to the AI, they can simply ask the assistant to browse their cloud buckets or fetch specific documents, making cloud management feel like a natural conversation. On a more technical level, the tool provides three essential capabilities: listing all buckets in an account, viewing the contents of a specific bucket, and downloading files to a local directory. It uses the Model Context Protocol to expose these functions as tools that a Large Language Model can call upon autonomously. This allows the AI to perform complex operations, such as scanning large datasets for specific information or preparing local environments with cloud-hosted assets, all based on simple natural language prompts. The server is built using Node.js and TypeScript, leveraging the AWS SDK’s compatibility with Yandex Cloud’s S3-compliant endpoints. Security is a priority, as the system manages authentication through environment variables and service account keys to ensure sensitive credentials remain protected. For developers building AI-driven workflows, this MCP server is an invaluable asset because it turns static cloud storage into an active, queryable resource that an AI agent can navigate and utilize to provide deeper, data-driven insights.
Category: Cloud & Infrastructure
Tags: cloud-storage, object-storage, s3, yandex-cloud
bash mkdir yandex-cloud-mcp cd yandex-cloud-mcp npm init -y Step 2: Install dependencies bash # Main dependencies npm install @modelcontextprotocol/sdk @aws-sdk/client-s3 dotenv # Development dependencies npm install -D typescript @types/node ts-node nodemon Step 3: Configure TypeScript Create a tsconfig.json file in the root directory: json { "compilerOptions": { "target": "ES2020", "module": "commonjs", "outDir": "./dist", "rootDir": "./src", "strict": true, "esModuleInterop": true, "skipLibCheck": true, "forceConsistentCasingInFileNames": true, "resolveJsonModule": true }, "include": ["src/**/*"], "exclude": ["node_modules", "dist"] } Step 4: Update package.json scripts Add the following to your package.json: json "scripts": { "build": "tsc", "start": "node dist/index.js", "dev": "ts-node src/index.ts", "watch": "nodemon --exec ts-node src/index.ts" } Step 5: Create source and build 1. Create a src folder. 2. Create src/index.ts and paste the server code (starting with #!/usr/bin/env node). 3. Build the project: bash npm run build ---storage.editor (read/write) or storage.viewer (read-only). 3. Create a Static Access Key and save the Access Key ID and Secret Access Key.claude_desktop_config.json file: - Windows: %APPDATA%\Claude\claude_desktop_config.json - macOS: ~/Library/Application Support/Claude/claude_desktop_config.json JSON Configuration: json { "mcpServers": { "yandex-cloud": { "command": "node", "args": ["/FULL/PATH/TO/YOUR/PROJECT/yandex-cloud-mcp/dist/index.js"], "env": { "YANDEX_ACCESS_KEY_ID": "YOUR_ACCESS_KEY_ID", "YANDEX_SECRET_ACCESS_KEY": "YOUR_SECRET_ACCESS_KEY" } } } } Note: Replace /FULL/PATH/TO/YOUR/PROJECT/ with the actual absolute path to your project folder. ---production-logs bucket. Find the log file from the last hour, download it, and tell me if there are any '500 Internal Server Error' entries."marketing-assets bucket. Group them by file type and tell me which files are older than six months so I can decide what to archive."project-research bucket and find the PDF about 'Q3 Market Trends'. Download it and give me a 5-bullet point summary of the main findings."CD Build Artifacts Problem: After a CI/CD pipeline runs, a developer needs to verify that the build artifacts (like a .zip or .apk file) were correctly generated and…
Part of MCP Servers