AI as Workspace

Community

Cross-platform AI chat client with MCP support and local-first storage.

★ 1.8k Stars Category · Dev Tools Very popular

47FMRS · D

AI as Workspace is a cross-platform, local-first AI chat client that acts as an MCP client supporting Tools, Prompts and Resources over STDIO and HTTP, with features such as multiple workspaces, Artifacts, a plugin system and dynamic prompts. Note that the repository is marked deprecated and succeeded by Nya AI, so new users should consider the successor project first.

Reliability

8/20

Security and permissions

11/20

Maintenance

6/20

Documentation

12/20

Setup experience

10/20

Read the FMRS scoring method →

AI as Workspace is a full-featured yet lightweight AI chat client available across Web, PWA, Windows, Linux, macOS and Android. It offers multiple workspaces, a plugin system, Artifacts and dynamic prompts, and acts as an MCP client supporting MCP Tools, Prompts and Resources over STDIO and HTTP connections. Data is stored locally first, with optional cloud synchronization after login for cross-device use. The project is marked deprecated and succeeded by Nya AI.

Setup

Source install steps:

Run pnpm i to install dependencies.
Run quasar dev to start the app in development mode (hot reload, error reporting).
Run quasar build to build the production SPA, or quasar build -m pwa for PWA.
For self-hosting, refer to the official self-hosting guide.

MCP configuration: install MCP-type plugins from the plugin marketplace, or manually add MCP servers using STDIO or HTTP connection methods.

Fit and risk

Best for

Users who want a consistent AI chat experience across multiple operating systems
Users who prefer local-first conversation storage with optional cloud sync
Users who want to consume tools, prompts and resources through the MCP protocol
Advanced users who value plugins and dynamic prompt variables for customization

Not for

Users looking for an actively maintained project (this one is deprecated; migration to Nya AI is recommended)
Users who only need a simple command-line tool without a graphical interface
Enterprise-grade centralized control or strict compliance auditing scenarios

Required permissions

Network access: connect to configured AI providers (OpenAI, Anthropic, Google, DeepSeek, xAI, Azure, etc.)
Local storage/file system: store data and file attachments locally first
Process execution: launch local MCP server processes over STDIO
Cloud account: used for cross-device data synchronization after login

Risks and side effects

The project is deprecated and may no longer receive security updates or feature fixes
Local MCP servers launched over STDIO inherit client process permissions; only add servers you trust
Cloud sync uploads data to a server, creating privacy and data leakage risks
Plugins and third-party services may access conversation content, risking data exposure when untrusted
Connecting to third-party AI providers sends conversation content to those providers

Troubleshooting

If an MCP server fails to connect, verify the STDIO command path or the HTTP address is correctly configured
If local data is not syncing, confirm you are logged in and the sync service is reachable
If the build fails, confirm pnpm dependencies are installed and a compatible Node.js version is used
If behavior is abnormal on a platform, try updating to the latest release or using the Web/PWA version
If a plugin does not work, check it is correctly installed and enabled from the plugin marketplace

Use cases

Everyday cross-platform AI conversations with multiple workspaces

Using it as an MCP client to connect local or remote MCP servers with Tools, Prompts and Resources

Converting assistant responses into editable, version-controlled Artifacts

Extending capabilities via plugins such as calculator, document parsing, video parsing and image generation

Working offline-first and syncing data across devices after login

Related MCP servers

Compare with other MCP servers