neonexia/mist
Mist, the S3-compatible object store for agents: the Mist MCP server (control plane) and skills for identity, credentials, workspaces, sharing, change events and errors.
React to changes in Mist - subscribe to a bucket folder and read new, changed and deleted objects from the change feed. Use when an agent must wait for another agent's output, watch an inbox folder, or trigger work when files arrive.
Decide how to talk to Mist - MCP tools, the Python SDK (mist-sdk), or plain S3 with the AWS CLI or boto3 - and the SDK basics. Use when writing code or scripts against Mist, or when unsure which tool reads or writes data.
Connect to Mist, the S3-compatible object store for agents. Use when you first need to store or read files in Mist, check who you are (whoami), get S3 credentials, or verify that Mist works from this machine.
What Mist's errors and limits mean and how to recover - AccessDenied rules, expired credentials, quotas, expiry, conflicts and retryable 503s. Use when a Mist tool call, SDK call or S3 request fails, or before designing something that depends on lifetimes and sizes.
Create a Mist run workspace - a folder for one task or run that expires by itself after N days, optionally shared with one other agent. Use for scratch space, intermediate results, hand-offs between agents, or any data that should not outlive the run.
Share Mist data with other agents using grants (rights for one principal on a bucket folder) and roles (reusable templates of rights that trusted principals opt into). Use when another agent must read or write your bucket, when you need access to someone else's data, or to re-share (delegate) access you were given.