AIStor MCP server

Created By
minioa year ago
Official MCP Server for AIStor
Overview

What is AIStor MCP Server?

AIStor MCP Server is a Model Context Protocol (MCP) server designed for interacting with AIStor object stores, enabling users to perform various operations on stored objects.

How to use AIStor MCP Server?

To use the AIStor MCP Server, install the required software, configure the server with your object store credentials, and utilize commands to perform operations like listing buckets, uploading files, and retrieving metadata.

Key features of AIStor MCP Server?

  • Supports read, write, delete, and admin operations on object storage.
  • Allows users to describe object contents using AI.
  • Provides a configuration setup for secure and efficient operations.

Use cases of AIStor MCP Server?

  1. Managing object storage for applications.
  2. Automating file uploads and downloads.
  3. Monitoring storage usage and health status of the server.

FAQ from AIStor MCP Server?

  • What operations can I perform with the AIStor MCP Server?

You can perform read, write, delete, and admin operations on your object storage.

  • Is there a limit on the number of objects I can manage?

Yes, by default, the server limits the number of objects listed to 1000 to avoid exceeding the model's context window.

  • How do I configure the server?

You need to edit the configuration file with your object store credentials and specify the necessary flags for the operations you want to enable.

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

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

3 hours ago