MinIO / AIStor MCP server

Created By
pavelannia year ago
Overview

what is MinIO / AIStor MCP server?

MinIO / AIStor MCP server is a Model Context Protocol (MCP) designed for interacting with MinIO servers, allowing users to manage buckets and objects effectively.

how to use MinIO / AIStor MCP server?

To use the MCP server, you need to set up a MinIO server, provide the necessary credentials, and configure the server according to your needs. You can then interact with the server using commands to list, upload, and download files.

key features of MinIO / AIStor MCP server?

  • List buckets and objects on the MinIO server.
  • Upload and download files securely.
  • Get and set object tags.
  • Admin functions to check server status and diagnostics.
  • Security features to manage user access levels.

use cases of MinIO / AIStor MCP server?

  1. Managing file storage in cloud applications.
  2. Performing administrative tasks on MinIO servers.
  3. Integrating with AI storage solutions for enhanced data management.

FAQ from MinIO / AIStor MCP server?

  • What is the purpose of the MCP server?

The MCP server facilitates interaction with MinIO servers, allowing for efficient file management and server administration.

  • Is it safe to use the MCP server?

Yes, but it is crucial to configure user permissions correctly to avoid unauthorized access.

  • Can I run the MCP server on Windows?

Yes, the MCP server can be configured to run on macOS, Linux, and Windows.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pavelanni
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago