AIStor

AIStor MCP server

This is a Model Context Protocol (MCP) server for interacting with AIStor object stores.

More information about MCP can be found on its official site.

More information about AIStor MCP server can be found in our blog posts:

• Introducing MCP server for AIStor

• Administrative functions of MCP server for AIStor

• MCP server for AIStor: How it works

Updates

• 2025-05-28

• Added support for MCP version 2025-03-26

• Added support for StreamableHTTP protocol

• Added the text_to_object tool

Features

Read operations

• List buckets

• List objects in the bucket

• Get object's metadata and tags

• Create a presigned URL with expiration for an object

AI operations

• Describe the object's contents using the ask_object tool

Write operations

These operations should be enabled by using the --allow-write flag in the config.

• Create a bucket

• Upload an object to the bucket

• Add tags to the object

Delete operations

These operations should be enabled by using the --allow-delete flag in the config.

• Delete an object

• Delete a bucket

Admin operations

These operations should be enabled by using the --allow-admin flag in the config.

• Get cluster info (config, health status, available space) in human-readable form

Available tools

Usually the Large Language Model (LLM) will be able to figure out which tool to use for your request. Sometimes, you may want to tell the model explicitly which tool to use. For such cases and also to let you know what else is possible with this MCP server, here is the list of tools available in this version.

You can always get this list by clicking the hammer icon in your Claude for Desktop application.

ask_object : Ask questions about an object's content using AI, supporting various file formats and returning contextual answers

copy_object : Copy an object from one bucket to another while preserving metadata and optionally modifying properties. You can also specify a version ID to copy a specific version of the object.

create_bucket : Create a new bucket with specified configurations and optional versioning settings

delete_bucket : Delete a bucket and optionally force removal of all contained objects

delete_object : Delete a specific object or version from a bucket, with optional soft delete support. You can also specify a version ID to delete a specific version of the object.

download_object : Download an object from a specified bucket to the local filesystem, preserving metadata. You can also specify a version ID to download a specific version of the object.

get_admin_info : Get comprehensive technical information about the AIStor object store, including status, performance metrics, and configuration

get_bucket_lifecycle : Get the lifecycle also known as lifecycle rules also known as ILM configuration of a specified bucket

get_bucket_replication : Get the replication configuration of a specified bucket

get_bucket_tags : Get the tags of a specified bucket

get_bucket_versioning : Get the versioning status and configuration of a specified bucket

get_data_usage_info : Get data usage information for the AIStor object storeincluding total data stored, number of objects, and usage by each bucket

get_object_metadata : Get detailed metadata of an object including content type, size, custom headers, and system properties

get_object_presigned_url : Get a presigned URL for an object in a bucket, with an optional expiration time. Default is 7 days.

get_object_tags : Get all tags associated with a specific object in a bucket

get_object_versions : Get all versions of an object in a bucket

list_allowed_directories : List all directories that are permitted for operations with the server

list_bucket_contents : List all objects in a specified bucket, including their sizes and last modified dates. You can also specify a prefix to filter the objects and whether to list versions.

list_buckets : List all buckets in the AIStor object store with their basic information

list_local_files : List all files and directories in a specified local directory path with their attributes

move_object : Move an object between buckets by copying to destination and removing from source. You can also specify a version ID to move a specific version of the object.

set_bucket_tags : Set the tags for a specified bucket

set_bucket_versioning : Configure versioning settings for a bucket with administrative privileges

set_object_tags : Set or update tags for an existing object in a bucket, supporting multiple key-value pairs. You can also specify a version ID to set tags for a specific version of the object.

text_to_object : Convert text to an object in a bucket, with support for different content types.

upload_object : Upload a file from local filesystem to a specified bucket.

Configuration for Claude for Desktop

This MCP server works with other MCP-enabled clients, but let's start with Claude. It uses the STDIO transport to interact with the server. See the next section for the instructions on configuring the server with StreamableHTTP transport.

Prerequisites

Download and install Claude for Desktop application from Claude. This MCP server works with other MCP-enabled clients, but let's start with Claude.

Make sure you have Docker or Podman installed and ready to use on your desktop/laptop.

Get your AIStor (or MinIO) object store credentials (MINIO_ACCESS_KEY and MINIO_SECRET_KEY) and its endpoint location. If you don't have an AIStor or MinIO server available, feel free to use the values for MinIO Playground server.

Configuration file

Open the Claude for Desktop configuration file with your favorite text editor. To find the config file in your system follow the Quickstart instructions from the Model Context Protocol site. Its default location is:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the following lines to the config file, replacing the credentials, endpoint, and YOUR_USERNAME with their actual values. This example uses Podman, but if you use Docker replace podman in the command: field with docker. If you have other MCP servers configured just insert the AIStor config in the list.

Be careful when adding the --allow-* flags. By default without any flags the server will be running in read-only mode. Add --allow-write and --allow-delete flags to this configuration only when you need them. The --allow-admin flag enables admin functions that collect information about the cluster.

{
 "mcpServers": {
 "aistor": {
 "command": "podman",
 "args": [
 "run",
 "-i",
 "--rm",
 "-v",
 "/Users/YOUR_USERNAME/Downloads:/Downloads",
 "-e",
 "MINIO_ENDPOINT=REPLACE_WITH_ENDPOINT",
 "-e",
 "MINIO_ACCESS_KEY=REPLACE_WITH_ACCESS_KEY",
 "-e",
 "MINIO_SECRET_KEY=REPLACE_WITH_SECRET_KEY",
 "-e",
 "MINIO_USE_SSL=true",
 "quay.io/minio/aistor/mcp-server-aistor:latest",
 "--allowed-directories",
 "/Downloads",
 "--allow-write",
 "--allow-delete",
 "--allow-admin"
 ]
 }
 }
}

By default, the number of objects or buckets that the server lists and send to LLM is limited by 1000 objects. This is done to avoid hitting the limit of the model's context window in tokens. If your model allows wider context window you can increase this number by adding the --max-keys parameter to the configuration file. Keep in mind that each object record contains several dozen of tokens.

Configuration for StreamableHTTP

This MCP server works with other MCP-enabled clients, that support the StreamableHTTP transport.

Prerequisites

Download and install an LLM client that supports MCP and StreamableHTTP. For example, you can use Cherry Studio.

Make sure you have Docker or Podman installed and ready to use on your desktop/laptop.

Get your AIStor (or MinIO) object store credentials (MINIO_ACCESS_KEY and MINIO_SECRET_KEY) and its endpoint location. If you don't have an AIStor or MinIO server available, feel free to use the values for MinIO Playground server.

Run the server

Run the following command to start the server. Replace the values for MINIO_ENDPOINT, MINIO_ACCESS_KEY, and MINIO_SECRET_KEY with your actual values. Replace 8090 (in three places!)with the port number available on your system.

podman run -d --name aistor-mcp-server \
 -v /Users/YOUR_USERNAME/Downloads:/Downloads \
 -e MINIO_ENDPOINT=REPLACE_WITH_ENDPOINT \
 -e MINIO_ACCESS_KEY=REPLACE_WITH_ACCESS_KEY \
 -e MINIO_SECRET_KEY=REPLACE_WITH_SECRET_KEY \
 -e MINIO_USE_SSL=true \
 -p 8090:8090 \
 quay.io/minio/aistor/mcp-server-aistor:latest \
 --allowed-directories /Downloads \
 --allow-admin \
 --allow-delete \
 --allow-write \
 --http \
 --http-port 8090

Configure the client

In the client, add the following configuration:

• MCP server name: aistor

• Type: StreamableHTTP

• URL: http://localhost:8090/mcp

Test the connection

Check if you can list the tools available in the server. Use the "Tools" tab in the client.

Stop the server

podman stop aistor-mcp-server

Usage

Here are some examples of what you can do:

Basic Operations

• "List all buckets on my AIStor server"

• "List the contents of bucket test"

File Operations

• "Download the file example.pdf to my Downloads directory"

• "Create a bucket my-bucket"

• "Upload document.pdf from Downloads to bucket my-bucket"

Metadata Operations

• "Get metadata of file.pdf in bucket my-bucket"

• "List all tags for object config.json"

Admin Operations

• "Show server health status"

• "Get storage usage statistics"

Each command will return human-readable responses with relevant information.