Storage Connections MCP Tools

When using the Vendia MCP server, you have access to the following MCP tools for interacting with your storage connections. Each tool serves a specific purpose in managing and working with your stored data.

Permission Requirements

Storage Connections use a two-layer permission system. For any operation to succeed, it must be allowed by both:

1. IAM Permissions (AWS level) - The outer security boundary
2. Access Policies (Vendia level) - Fine-grained control using glob patterns

See Access Policies for a comprehensive guide on how these layers work together.

Available Tools

list-storage-connections

Lists all configured storage connections and their status.

• IAM Permissions: None required
• Access Policy Actions: None required

list-storage-connection-contents

Browse folder structure and list files in your connected S3 buckets.

• IAM Permissions: s3:ListBucket
• Access Policy Actions: FILE_READ
• Note: Only files and folders matching access policy patterns with read permissions will be listed

read-storage-connection-file

Read content from supported file types in your connected S3 buckets.

• IAM Permissions: s3:GetObject
• Access Policy Actions: FILE_READ
• Note: The file path must match an access policy pattern that allows read operations

write-storage-connection-file

Create new files or overwrite existing files in your connected S3 buckets.

• IAM Permissions: s3:PutObject
• Access Policy Actions:
  • For new files: FILE_CREATE
  • For existing files: FILE_WRITE

FILE_CREATE vs FILE_WRITE

• FILE_CREATE - Allows creating new files but prevents overwriting existing files
• FILE_WRITE - Allows overwriting existing files but not creating new ones
• Grant both actions when you need both capabilities

See Access Policies - Actions for details.

delete-storage-connection-file

Delete files from your connected S3 buckets.

• IAM Permissions: s3:DeleteObject
• Access Policy Actions: FILE_DELETE
• Note: The file path must match an access policy pattern that allows delete operations

S3 Directory Behavior

In S3, directories don’t exist independently — they’re simulated through key prefixes. Creating a file creates its parent “directories,” and deleting the last file in a “directory” removes that directory path as well.

Related Documentation

• Access Policies - Complete guide on the two-layer permission system, actions, glob patterns, and configuration examples
• Creating Storage Connections - Initial setup and IAM configuration
• Best Practices - Security and organizational recommendations
• Troubleshooting - Common issues and solutions