Krea | Workspace Picker and Upload URLs Improve MCP Workflows
Krea has updated its MCP workflow with a new workspace picker and presigned uploads for local files. Published on July 1, 2026, the changelog improves how MCP sessions connect to a specific Krea workspace, how compute units are billed, where uploaded assets are saved, and how local media files can be passed into generation workflows through get_upload_url.
Krea makes MCP sessions easier to control across workspaces
Krea's latest MCP update is mainly about control. When a client asks a user to sign in to Krea through OAuth, the consent screen now includes a workspace picker. That means users can choose which workspace the MCP session should run against instead of relying only on a default workspace.
For creative teams, web designers, and template creators using AI-assisted workflows, that detail matters. A personal workspace and a shared studio workspace may have different budgets, assets, permissions, and production expectations. Binding the MCP session to the correct workspace helps keep billing and media outputs in the right place.
The workspace picker affects billing and asset scope
When a workspace is selected during OAuth consent, that workspace becomes bound to the MCP session. Krea explains that the selected workspace determines where compute units are billed and where uploaded assets are saved.
This is useful for teams that use Krea through MCP-compatible clients such as coding assistants or creative automation tools. If a session should use a shared studio workspace instead of a personal workspace, the user can select that during connection. To change the binding later, the user needs to disconnect Krea in the MCP client and reconnect.
Presigned uploads make local files easier to use
Krea also updated the MCP upload flow with presigned URLs. The new get_upload_url tool returns a short-lived URL that the client can use to upload a local file as multipart/form-data. The response then returns an asset URL that can be passed into a later generate call.
For web design workflows, this is practical when a local image, style reference, product visual, moodboard asset, or starting frame needs to be used as input for generation. Instead of manually hosting the file somewhere first, the MCP client can request the upload URL, send the file, and reuse the returned asset URL in the next generation step.
Media URL inputs are now more consistent
Krea notes that endpoints accepting media URLs now support three forms consistently: an external public URL, a base64 data URI, or an uploaded asset URL from POST /assets or MCP's get_upload_url.
This gives developers and creative builders more flexibility. A quick test can use a public image URL or inline data URI, while a repeatable team workflow can rely on uploaded asset URLs. That consistency can make automation easier to document and less fragile across image, video, and reference-based workflows.
IMPORTANT: Presigned upload URLs are valid for three hours. If a file is already available through a public URL or can be encoded as a base64 data URI, Krea says you can skip get_upload_url and pass that value directly instead.{alertWarning}
Why this matters for AI-assisted design workflows
This update is not a new visual model, but it can still matter for production workflows. MCP integrations become more useful when they handle account context, billing, asset storage, and media input cleanly. Without that clarity, teams can easily generate assets in the wrong workspace or lose track of where files were uploaded.
For template creators, this can support workflows where an agent lists available models, checks schemas, uploads local references, generates images or videos, and returns assets without requiring every API step to be written manually. The result is a more practical bridge between creative automation and real project assets.
Daisuki's Take: What This Means for Web Designers
For web designers, the useful part of this Krea update is workflow reliability. AI tools become easier to use in real projects when the system knows which workspace is paying for the work and where uploaded assets should live.
We think presigned uploads are especially helpful for template and content workflows. Many creative tasks start with local files: a reference image, a draft visual, a brand asset, or a product photo. Making those files easier to pass into MCP generation can reduce friction when building landing page visuals, campaign assets, or design experiments.
The practical takeaway is to treat workspace selection as part of setup, not an afterthought. Before using Krea through MCP in a team workflow, confirm the workspace, billing source, uploaded asset location, and media input format so the generation process stays organized.
Sources and Recommended Links
- Krea changelog | Krea Official Documentation
- Model Context Protocol (MCP) server | Krea Official Documentation
- API Reference | Krea Official Documentation
