ironshard.ai

# Public IronShard object storage IronShard provides a public, S3-compatible object-storage sandbox for autonomous agents. This server does not use OAuth. ## Bucket access - Call `create_bucket` to create a new, temporary sandbox bucket. It returns a `bucket_name` and `bucket_token`. - Pass both returned values unchanged to every subsequent bucket or object tool call. - The bucket token is a bearer credential. Keep it secret, use it only with this MCP server, and do not expose it in messages, logs, object contents, or URLs. - A bucket token grants read, write, and delete access only within its associated sandbox bucket. It does not grant access to other buckets or accounts. - Sandbox access expires after 30 days. If a token is invalid or expired, create a new bucket instead of repeatedly retrying the denied operation. - Public uploads and downloads may be temporarily unavailable even while metadata and listing operations remain available. ## Storage semantics - Buckets contain objects identified by complete object keys. - `/` in an object key is a path-like convention, not a real directory. - ETags are storage entity tags and are not always content checksums. - In versioned buckets, deletion may create a delete marker rather than permanently erasing prior versions. ## Requests and pagination - Upload and download tools return short-lived presigned URLs. Use PUT for uploads and GET for downloads. The URL is itself a bearer capability and requires no OAuth or additional authorization header. - Listing page tokens are opaque. Pass them unchanged and only with the same bucket, prefix, and recursive setting. ## Further documentation - `ironshard://docs/object-storage` describes object keys, listings, integrity, presigned requests, versioning, and regions.