Key Takeaways
- Cherry Studio (cherry-ai.com) is a free, open-source desktop app licensed under AGPL 3.0.
- It connects to dozens of AI providers (OpenAI, Anthropic, Google Gemini, DeepSeek, and more) plus local runtimes (Ollama, LM Studio) from one interface.
- A built-in Knowledge Base feature adds retrieval-augmented generation (RAG) over your own PDFs, Word documents, and web pages.
- MCP (Model Context Protocol) support lets connected models call external tools through a standard server interface.
- Cherry Studio does not run models itself β it needs a cloud API key or a local runtime like Ollama to actually generate responses.
π In One Sentence
Cherry Studio is a free, open-source (AGPL 3.0) desktop AI client for Windows, macOS, and Linux that connects to dozens of AI providers and local models β including Ollama and LM Studio β from one interface, and adds document knowledge bases and MCP tool support on top.
π¬ In Plain Terms
Cherry Studio doesn't run its own AI models. It's a chat window that can talk to almost any AI service you already have an account with, plus any local model already running on your machine, without forcing you to switch apps to compare answers or switch providers.
Quick Facts: Cherry Studio
- License: AGPL 3.0 (open source, source code publicly available)
- Platforms: Windows, macOS, Linux (Electron-based desktop app)
- Website: cherry-ai.com
- GitHub: github.com/CherryHQ/cherry-studio (source code & releases)
- Cost: Free app; connected cloud providers bill separately by API usage
- Core function: Multi-provider AI chat client with knowledge bases and MCP tool support
What Is Cherry Studio?
Cherry Studio is a free, open-source desktop client that lets you chat with dozens of different AI providers and local models from a single app, instead of switching between separate provider websites. It is licensed under AGPL 3.0, meaning the source code is public and any modified version distributed to others must also stay open source.
The app itself does not host or train any AI model. It is a front end: you connect it to a cloud provider by pasting an API key, or to a local model by pointing it at a running Ollama or LM Studio server. Once connected, Cherry Studio presents every provider and model in the same conversation interface, so switching from a cloud model to a local one is a dropdown change, not a new app.
Beyond chat, Cherry Studio bundles three features aimed at power users: a document knowledge base for retrieval-augmented answers, MCP (Model Context Protocol) support for connecting models to external tools, and a library of prompt-template "agents" for common roles like coding assistant, translator, or writing editor.
What Can You Actually Do With Cherry Studio?
- Connect dozens of providers side by side. Add API keys for OpenAI, Anthropic, Google Gemini, DeepSeek, Moonshot, Zhipu, Alibaba Qwen, OpenRouter, and any OpenAI-compatible endpoint β switch between them per conversation without re-entering credentials.
- Run local models through Ollama or LM Studio. Point Cherry Studio at a running local server and its models appear in the same picker as your cloud providers, so a privacy-sensitive prompt can go to a local model while a general question goes to a cloud model.
- Build a document knowledge base. Upload PDFs, Word files, or web pages into a collection; reference that collection in a chat to get retrieval-augmented answers grounded in your own material rather than the model's training data alone.
- Connect MCP servers for tool use. Model Context Protocol servers give a connected model access to external tools β file search, a database, a browser β through one standard interface instead of custom integration code per provider.
- Use prompt-template agents. A library of preconfigured system prompts (coding assistant, translator, writing editor, and others) sets up a specialized conversation in one click instead of writing a system prompt from scratch each time.
- Organize conversations into topics and folders. Multi-provider usage produces a lot of conversation history; topic folders keep chats with different models and different purposes from blending into one unsorted list.
Who Should Use Cherry Studio?
Cherry Studio is built for people who already use more than one AI provider or model and want one place to manage that, not for someone looking for their first AI chat app.
- β You already pay for 2+ AI provider API keys β a single interface avoids juggling browser tabs and separate chat histories.
- β You run local models with Ollama or LM Studio and want the same interface for cloud fallback β Cherry Studio lists both in one model picker.
- β You want to chat against your own documents without a separate RAG tool β the built-in Knowledge Base covers PDFs, Word files, and web pages.
- β You need MCP tool access without custom integration code β connect an MCP server once and any supported model can use it.
- β You only use one AI provider and don't want to manage API keys β use that provider's own app directly (ChatGPT, Claude, Gemini).
- β You need managed, multi-user deployment for a team β Cherry Studio is a single-user desktop app; use Open WebUI on a server instead.
- If unsure: start with Cherry Studio free, connect one provider you already use, and add local models or a knowledge base only once the basic chat workflow proves useful.
When Should You NOT Use Cherry Studio?
Multi-provider flexibility is not free β it adds configuration steps that a single-provider app skips.
- If you want zero setup: Cherry Studio requires adding at least one provider API key or local server before it does anything useful. A provider's own web or desktop app needs no setup beyond logging in.
- If you need enterprise access controls: Cherry Studio stores its configuration locally per user, with no built-in team roles, audit logs, or centralized API key management. Use a server-hosted tool like Open WebUI for that.
- If your workflow is entirely inside one provider's ecosystem: features like OpenAI's custom GPTs or Anthropic's Projects don't carry over into Cherry Studio's generic chat interface.
- If you need guaranteed uptime and support contracts: Cherry Studio is a community open-source project with no commercial support tier; provider outages or app bugs are handled on the project's own timeline.
How Do You Set Up Cherry Studio?
Setup has two required steps and two optional ones, in this order:
- 1. Download and install. Get the installer for Windows, macOS, or Linux from cherry-ai.com and run it β no account is required to install. The official site currently redirects to a Chinese-language page; if you prefer an English interface, download directly from the GitHub releases page instead.
- 2. Connect a provider or local model. Open Settings β Model Providers and paste an API key for a cloud provider, or point Cherry Studio at a running Ollama or LM Studio server address (typically `http://localhost:11434` for Ollama).
- 3. Select a default model. Pick which connected model answers new conversations by default; switch per conversation at any time from the model dropdown.
- 4. *(Optional)* Add a knowledge base. Go to Knowledge Base, create a collection, and upload PDF, Word, or web-page content to enable retrieval-augmented answers.
- 5. *(Optional)* Connect an MCP server. In Settings β MCP, add a server address to give connected models access to external tools such as file search.
Cherry Studio vs LM Studio vs AnythingLLM vs Msty: Which One?
All four are free desktop AI clients, but each optimizes for a different primary job.
Tool | Link | Best for | Runs local models | Cloud providers | Built-in RAG | MCP support | License |
|---|---|---|---|---|---|---|---|
| Cherry Studio | cherry-ai.com | Managing many providers + local models in one app | Via Ollama / LM Studio (not native) | Dozens | Yes | Yes | AGPL 3.0 |
| LM Studio | lmstudio.ai | Downloading and running GGUF models locally | Native (GGUF) | None built in | No | No | Free (closed) |
| AnythingLLM | anythingllm.com | RAG-first document chat with a vector store | Via Ollama / LM Studio | Several | Yes (core feature) | No | MIT |
| Msty | msty.app | Clean consumer UX with minimal setup | Via Ollama (built in) | Several | Yes | No | Free (closed) |
Deeper comparison of desktop frontends: Best Local LLM Frontends.
Common Mistakes With Cherry Studio
- Expecting Cherry Studio to run models without a provider or local runtime connected. It is a client, not an inference engine β install Ollama or LM Studio first if you want local models, or add a cloud API key.
- Assuming cloud usage through Cherry Studio is free. The app is free; the provider still bills for API usage exactly as if you called their API directly.
- Sending sensitive documents to a cloud-provider model through the Knowledge Base feature. RAG retrieval still sends the retrieved text to whichever model answers the question β use a local model via Ollama for sensitive material.
- Connecting an untrusted MCP server. MCP grants a connected model real tool access (files, databases, browsing); only connect servers whose source and behavior you trust.
Common Questions About Cherry Studio
What is Cherry Studio?
Cherry Studio is a free, open-source desktop application (AGPL 3.0) for Windows, macOS, and Linux that connects to dozens of AI providers and local models from a single chat interface, instead of locking you into one vendor.
Is Cherry Studio free to use?
The app itself is free and open source. Using a cloud provider through Cherry Studio still requires an API key from that provider, billed by the provider directly, not by Cherry Studio. Running a local model through Ollama or LM Studio has no per-token cost.
Which AI providers does Cherry Studio support?
Cherry Studio supports OpenAI, Anthropic, Google Gemini, Azure OpenAI, OpenRouter, DeepSeek, Moonshot, Zhipu, Alibaba Qwen, and local runtimes including Ollama and LM Studio, among others. Any OpenAI-compatible endpoint can also be added manually.
Does Cherry Studio work with local models?
Yes. Point Cherry Studio at a running Ollama or LM Studio server and it lists your locally downloaded models alongside any connected cloud providers in the same model picker.
What is MCP support in Cherry Studio?
MCP (Model Context Protocol) lets a connected model call external tools, such as file search, a database, or a web browser, through a standardized server interface. Cherry Studio can connect to MCP servers so any supported model gains those tool capabilities.
Does Cherry Studio have a built-in knowledge base?
Yes. The Knowledge Base feature lets you upload PDFs, Word documents, and web pages into a collection, then reference that collection in a chat for retrieval-augmented answers grounded in your own content.
How is Cherry Studio different from LM Studio?
LM Studio focuses on running local GGUF models with a built-in model downloader and an OpenAI-compatible API server. Cherry Studio does not download or run models itself; it is a client that connects to local runtimes like LM Studio or Ollama plus dozens of cloud providers in one interface.
How is Cherry Studio different from AnythingLLM?
AnythingLLM is built around retrieval-augmented generation with a workspace-and-document model as its core concept. Cherry Studio treats knowledge bases as one feature among many, alongside multi-provider chat, MCP tool use, and prompt-template agents.
Is data private when using Cherry Studio?
Cherry Studio itself does not send your conversations to its own servers. Data privacy depends on which model you connect: a local Ollama model keeps everything on your machine, while a cloud provider (OpenAI, Anthropic, etc.) processes your messages under that provider's own data policy.
What are the system requirements for Cherry Studio?
Cherry Studio itself is a lightweight Electron desktop app and runs on modest hardware. If you also run local models through Ollama or LM Studio on the same machine, the model's own hardware requirements (RAM, VRAM) apply separately.
Sources
- Cherry Studio official site and documentation β cherry-ai.com
- Cherry Studio source code and license (AGPL 3.0) β github.com/CherryHQ/cherry-studio
- Model Context Protocol specification β modelcontextprotocol.io