Skip to main content
Glama
pickstar-2002

MinIO Storage MCP

connect_minio

Establish a connection to MinIO object storage servers using endpoint, port, and authentication credentials to enable file management operations.

Instructions

连接到MinIO服务器

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endPointYesMinIO服务器地址
portYesMinIO服务器端口
useSSLNo是否使用SSL连接
accessKeyYes访问密钥
secretKeyYes秘密密钥
regionNo区域设置(可选)

Implementation Reference

  • MCP tool dispatch handler for 'connect_minio'. Validates input using MinIOConfigSchema, connects via MinIOStorageClient, and returns success message.
    case 'connect_minio': {
      const config = MinIOConfigSchema.parse(args);
      await this.minioClient.connect(config);
      return {
        content: [
          {
            type: 'text',
            text: `成功连接到MinIO服务器 ${config.endPoint}:${config.port}`
          }
        ]
      };
    }
  • src/index.ts:67-82 (registration)
    Tool registration definition including name, description, and input schema in the ListTools response.
    {
      name: 'connect_minio',
      description: '连接到MinIO服务器',
      inputSchema: {
        type: 'object',
        properties: {
          endPoint: { type: 'string', description: 'MinIO服务器地址' },
          port: { type: 'number', description: 'MinIO服务器端口' },
          useSSL: { type: 'boolean', description: '是否使用SSL连接', default: false },
          accessKey: { type: 'string', description: '访问密钥' },
          secretKey: { type: 'string', description: '秘密密钥' },
          region: { type: 'string', description: '区域设置(可选)' }
        },
        required: ['endPoint', 'port', 'accessKey', 'secretKey']
      }
    },
  • Zod schema (MinIOConfigSchema) for validating the input parameters of the connect_minio tool. Used in handler for parsing.
    export const MinIOConfigSchema = z.object({
      endPoint: z.string().describe('MinIO服务器地址'),
      port: z.number().min(1).max(65535).describe('MinIO服务器端口'),
      useSSL: z.boolean().default(false).describe('是否使用SSL连接'),
      accessKey: z.string().describe('访问密钥'),
      secretKey: z.string().describe('秘密密钥'),
      region: z.string().optional().describe('区域设置(可选)')
    });
  • Core implementation of MinIO connection in MinIOStorageClient.connect(). Creates Minio.Client instance and tests connection by listing buckets.
    async connect(config: MinIOConfig): Promise<void> {
      try {
        this.client = new Minio.Client({
          endPoint: config.endPoint,
          port: config.port,
          useSSL: config.useSSL,
          accessKey: config.accessKey,
          secretKey: config.secretKey,
          region: config.region
        });
    
        // 测试连接
        await this.client.listBuckets();
        this.config = config;
      } catch (error) {
        throw new Error(`连接MinIO服务器失败: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool connects to a server but doesn't describe what this entails—whether it establishes a session, validates credentials, returns a connection handle, or has side effects like authentication. For a connection tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence ('连接到MinIO服务器') that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every word contributing to clarity. No fluff or redundancy is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a connection tool (6 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what the tool returns (e.g., a connection object, status), error conditions, or how it integrates with sibling tools. For a foundational operation like server connection, more context is needed to guide effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with all parameters documented in the schema (e.g., endPoint, port, useSSL, accessKey, secretKey, region). The description adds no additional parameter semantics beyond what's in the schema. According to the rules, when coverage is high (>80%), the baseline score is 3 even without param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '连接到MinIO服务器' (Connect to MinIO server) clearly states the tool's purpose as establishing a connection to a MinIO server. It uses a specific verb ('连接到' - connect to) and resource ('MinIO服务器' - MinIO server), making the action clear. However, it doesn't differentiate from sibling tools, which are all MinIO operations but focus on different actions like bucket/object management rather than connection establishment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., this must be called before other MinIO operations), exclusions, or relationships to sibling tools like bucket_exists or upload_file. Without such context, users must infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pickstar-2002/minio-storage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server