Krea | Workspace Picker and Presigned Uploads Improve MCP
Krea has updated its MCP workflow with a new Workspace picker, presigned uploads, and more consistent media URL inputs across the API. The update is especially useful for creators, studios, and developers connecting Krea to MCP-compatible tools, because it makes workspace selection, billing, asset storage, and local file uploads clearer.
Krea makes MCP workflows clearer for creative teams
Krea's latest changelog update focuses on a practical part of AI creative workflows: how files, workspaces, and media inputs move through MCP-connected tools. The new Workspace picker lets users choose which Krea workspace an MCP session should run against when signing in through OAuth.
For designers and studios using Krea through connected clients, this matters because a workspace is not just a label. It determines where compute units are billed and where uploaded assets are saved. That makes the update useful for teams that separate personal work, client projects, shared studio spaces, or production environments.
The Workspace picker gives more control during MCP sign-in
When an MCP client asks a user to sign in to Krea, the OAuth consent screen now shows every workspace the user belongs to. The default workspace is pre-selected, but users can switch to another workspace before continuing the session.
This is useful when a creator wants an MCP session to run inside a shared studio workspace instead of a personal one. The selected workspace is bound to the OAuth session, so teams have a clearer connection between the work being generated, the compute usage, and the place where uploaded assets are stored.
Presigned uploads make local files easier to use
Krea's MCP upload flow now uses presigned URLs through a new get_upload_url tool. The tool returns a short-lived URL that the client can use to upload a local file as multipart/form-data. After the upload, the response includes an asset URL that can be passed directly into a generate call.
For creative workflows, this reduces friction when working with local references, source images, moodboards, or assets that are not already hosted online. Instead of manually preparing a public URL before generating, an MCP-connected client can upload the file and use the returned asset URL in the next generation step.
Media URL inputs are now more consistent across the API
Krea also updated its API behavior so endpoints that accept media URLs can use the same three input forms: an external URL, a base64 data URI, or an uploaded asset URL from POST /assets or MCP's get_upload_url.
This consistency matters for developers building creative tools around Krea. A workflow can choose the input method that fits the situation: public URLs for already hosted files, base64 data URIs for inline scripts, or uploaded asset URLs for local files that need to be sent through Krea's upload flow.
Why this matters for design and AI production workflows
This is a technical update, but it has a practical creative impact. Many AI design workflows depend on moving reference images, source media, brand assets, or generated outputs between tools. If uploads are unclear or workspace billing is ambiguous, teams can lose time managing the workflow instead of refining the creative result.
With workspace selection and more predictable media inputs, Krea becomes easier to integrate into studio pipelines, internal tools, and MCP-based creative assistants. That can help teams build workflows where assets are uploaded, generated, reviewed, and stored in the correct workspace from the start.
IMPORTANT: Presigned upload URLs are valid for three hours. If a file is already available as a public URL or can be passed as a base64 data URI, the upload step can be skipped. To change the workspace bound to an MCP OAuth session, disconnect Krea in the MCP client and reconnect.{alertWarning}
Daisuki's Take: What This Means for Designers
Krea's MCP update is useful because creative AI workflows are becoming more connected. Designers may not care about every technical detail of OAuth or presigned URLs, but they do care when files upload cleanly, assets land in the right workspace, and the right account is billed for a session.
The Workspace picker is especially important for teams. It helps avoid confusion between personal and shared production spaces, which matters when a studio is testing prompts, uploading client assets, or building repeatable generation workflows with MCP-compatible clients.
We would treat this as a workflow reliability update. It does not change the visual style of Krea's models directly, but it can make the production process cleaner for teams that use Krea as part of a larger creative system. Better upload handling and clearer workspace binding usually mean fewer interruptions before the actual design work begins.
Sources and Recommended Links
- Workspace picker and presigned uploads for MCP | Krea Official Changelog
