Bring your own storage
Add Wasabi, S3, R2, MinIO or Backblaze as a writable asset destination.
Add BYOK storage from Workspace → Storage or let an authorized agent use the storage tools. Credentials are encrypted and never returned after saving.
Connect a bucket through MCP
- 1
Authenticate the MCP client
Add https://postward.cc/mcp to your client and complete the OAuth browser flow. Authentication must happen before tools can run; Postward does not use static API keys.
- 2
Check your role and current storage
Ask the agent to call get_storage_configuration. Connecting credentials requires ADMIN or OWNER role.
- 3
Validate without saving
Give the credentials to your trusted local MCP client and ask it to call validate_storage. Postward performs a temporary write/read/delete probe and removes the probe object.
- 4
Connect and select
After validation, ask the agent to call create_storage and then set_default_storage. create_storage validates again before encrypting and saving the secret.
- 5
Verify the result
Call list_storages. Confirm status ACTIVE, isDefaultWrite true and the intended asset resolution order.
Configure my S3-compatible bucket as Postward storage.
First call get_storage_configuration and confirm I have permission.
Validate the credentials before saving anything.
If validation succeeds, create the storage, make it the default write destination, and show me the final sanitized configuration.
Never repeat or expose the secret access key in your response.s3:PutObject
s3:GetObject
s3:DeleteObject
s3:ListBucketTreat chat history as sensitive
Storage secrets are never returned by Postward, but entering one into an MCP client may place it in that client's local conversation history. Prefer a short-lived or dedicated least-privilege key and rotate it after setup when your provider supports that workflow.