Thanks to visit codestin.com
Credit goes to www.typeui.sh

Workspaces

A workspace is your TypeUI home. It keeps your design systems, projects, MCP usage, and dashboard settings connected to your account.

When you use the dashboard or connect through MCP, TypeUI uses your workspace to keep the same design systems and settings available everywhere.

What a workspace contains

  • Design systems you create, import, edit, and publish.
  • Projects that can use a selected design system.
  • MCP usage activity for your account.
  • Settings that affect how TypeUI responds to your AI tool.

How workspaces connect to MCP

When your AI coding tool connects to TypeUI MCP, TypeUI uses your signed-in account to find the right workspace. From there, it can read your published design systems, prompts, and usage settings.

That keeps the MCP experience consistent with what you see in the dashboard.

Design system versions in workspaces

Workspace design systems are versioned when you publish them. The first published package is Version 1, and every later publish creates the next version with its own release notes.

The current published version is the default version for MCP installs. If you roll back from the dashboard, TypeUI points the workspace design system back to that older version, and MCP uses it as the default until you publish a new version.

MCP can also list all published versions for a workspace design system and install a specific version by version number or version ID. This lets one project stay pinned to an older design system while another project updates to the latest version.

Typical workflow

Open design systems

Go to Dashboard design systems to create or import a design system.

Publish when ready

Publish the design system with release notes so TypeUI MCP can use that version when your AI coding tool asks for UI guidance.

Use it from your AI tool