Skip to main content
Gcore MCP Server provides approximately 40 tools for managing S3-compatible object storage and SFTP storage through natural language. Configuration and client setup are covered in the Gcore MCP Server overview.

​
Configure for Storage

The GCORE_TOOLS environment variable controls which tools are exposed. Setting GCORE_TOOLS="storage.*" loads all Storage tools. 
GCORE_TOOLS="storage.*"
Storage tools follow the storage.<resource>.<operation> naming pattern. The object_storages tools manage S3-compatible storage buckets with list, create, get, and delete operations. The sftp_storages tools handle SFTP storage instances. The locations tools list available storage locations, ssh_keys tools manage SSH keys for SFTP access, and statistics tools retrieve storage usage metrics.

​
Storage operations

Natural language requests trigger the corresponding API operations. Listing locations requires no parameters—a request like “Show available storage locations” returns location names, regions, and S3 endpoints such as s3.lu.gcore.com for Luxembourg. Bucket listing shows all storage buckets. A request to “List all my storage buckets” returns bucket names, locations, sizes, object counts, and creation dates. Bucket creation requires a name and location. Requesting “Create a new storage bucket named ‘app-uploads’ in Luxembourg” provisions the bucket and returns the S3 endpoint with access credentials for client configuration. Storage statistics provide usage insights. “Show storage usage statistics for all buckets” returns per-bucket size, object count, and bandwidth consumption alongside totals. SFTP storage management includes instance creation and listing. Creating with “Create an SFTP storage instance in Luxembourg” provisions the instance and returns connection details including host, port, and username. SSH keys must be added separately to enable access—“Add an SSH key for SFTP access” configures authentication.
WarningDeleting a storage bucket removes all objects permanently. Requesting “Delete the storage bucket ‘old-backup’” executes immediately and cannot be undone.

​
Multi-step workflows

Complex storage configurations involve multiple tools executed in sequence. Setting up CDN with storage origin requires creating a bucket, retrieving credentials, and configuring the CDN. A combined request like “Create a storage bucket named ‘cdn-origin’ in Luxembourg and show me the S3 endpoint and credentials” provisions storage ready for CDN integration. Migration planning queries available locations. “What storage locations are available for migrating data from Luxembourg to a US region?” returns US-based locations with their endpoints. Cost analysis combines statistics with billing context. “Show storage usage and estimated costs for all buckets” returns usage metrics and cost projections.

​
S3 client integration

Gcore Object Storage is S3-compatible. After creating a bucket via MCP Server, any S3 client can access it using the returned endpoint and credentials. 
aws s3 ls s3://app-uploads --endpoint-url https://s3.lu.gcore.com
aws s3 cp file.txt s3://app-uploads/ --endpoint-url https://s3.lu.gcore.com
The AWS CLI, s3cmd, and S3-compatible SDKs work with Gcore storage endpoints.

​
Tool naming patterns

Storage tool names follow the storage.<resource>.<operation> pattern. The storage.object_storages.list tool lists all storage buckets without parameters and returns bucket names, locations, sizes, and object counts. The storage.object_storages.create tool requires name (the bucket name) and location (the storage location). The storage.locations.list tool returns available storage locations with regions and S3 endpoints.
InfoTool parameters and behavior reflect the Gcore Storage API. Bucket management via the control panel is documented in the S3 storage guide. Tool filtering options are available in the GCORE_TOOLS reference.