Temp Storage
Ephemeral private file storage for AI handoffs and shareable download links.
Overview
Private ephemeral file storage for AI workflows. Store files between tool calls, read them via MCP, share via presigned links, or pass file_id to other integrations (Email, Gmail, WordPress).
Prerequisites
- A stackgate.ai account
- Temp Storage enabled on your hub (platform administrator configures object storage)
Getting credentials
- Open Integrations → Temp Storage.
- Click Activate — no upstream account or API key is required.
- Your company admin may need to allow Temp Storage on Company Integrations.
Using with AI clients
- Dedicated endpoint:
POST /mcp/temp-storage - Private gateway:
temp-storage__*tools
Standalone workflow: create_file → read_file or create_temp_link → delete_file.
Cross-tool workflow: email__download_attachment or gmail__download_attachment with store_in_temp_storage=true, or drive__download_file with mode=temp-storage → returns file_id → wordpress__upload_media with file_id.
Always pass file_id between tools — never bucket paths.
Troubleshooting
- 503 not configured — hub administrator must configure Temp Storage object storage.
- 422 not activated — activate Temp Storage on My Integrations.
- 429 quota exceeded — daily hub limits apply; retry after UTC midnight.
- File expired — files auto-delete after
ttl_hours(default 2, max 24); store again if needed. - File too large — default max 50 MB per file.
Available tools
-
create_file
Store a private file in Temp Storage. Returns file_id for cross-tool handoff.
-
read_file
Read a stored file by file_id. Returns embedded binary under 10 MB or a resource_link for larger files.
-
create_temp_link
Create a presigned download URL for a stored file. Link expires independently of the MCP session.
-
delete_file
Delete a stored file before its expiry time.
MCP endpoint:
https://stackgate.ai/mcp/temp-storage
(HTTP) or via the
private gateway.
Related workflows
Multi-integration playbooks that use Temp Storage to solve concrete business outcomes.