Claude Desktop App vs Web: What the Desktop App Adds

The Claude desktop app for macOS and Windows is claude.ai with a way into your computer: local MCP servers and desktop extensions, the local half of Cowork, quick entry on a Mac, and a bridge for Claude in Chrome. What it adds, how to install it on each system, what stays the same, and when the browser is all you need.

7 min read

The Claude desktop app is the same Claude you use at claude.ai, with the same account, chats, projects and plan, plus one thing a browser tab cannot have: access to your own computer. That access is what the desktop app adds. It runs local MCP servers and desktop extensions, lets Cowork read and write your files, use a browser and operate other apps, and on a Mac gives you a system-wide shortcut to Claude. If you never need Claude to touch anything on your machine, the web app does the rest just as well.

What the desktop app adds

Local MCP servers and desktop extensions

MCP servers come in two kinds, and only one needs the app. Anthropic’s page on desktop and web connectors (opens in a new tab) puts it plainly: remote connectors work on every Claude surface once connected, while desktop extensions run locally and are only available in Claude Desktop and Claude Code, not on the web or mobile. A desktop extension is a single-click package for a local MCP server, installed from Settings, Extensions, either from a directory Anthropic reviews or from a file you install yourself. Local servers you configure by hand live in the app’s config file; the file format is in the Claude Desktop MCP config guide, and fixes for when it will not load are in Claude Desktop MCP not working.

Cowork on your own computer

Cowork runs new sessions in Anthropic’s cloud on every surface (existing desktop installs can still run local sessions in a Linux VM), but three things need the desktop app open: local file access, browser use and computer use. With the app running, Cowork reads from and writes to folders on your computer without uploads, uses a browser built into the app by default, and, on Pro and Max, can operate other desktop apps in beta, asking before each app. Without the app, Cowork on the web works with files saved to your Claude account and connected services only. When to reach for Cowork rather than Claude Code is covered in Claude Cowork vs Claude Code.

Quick entry and always-on access

The app sits in your dock or taskbar, so Claude is a window away rather than a tab you have to find. On a Mac there is more. Anthropic’s page on quick entry (opens in a new tab) says a double tap of the Option key opens Claude over whatever you are doing, and from there you can drag to capture part of the screen, click a window to attach its contents, or press Caps Lock to dictate. It needs macOS 12 or later, macOS 14 for dictation, and screen recording, accessibility and speech permissions. Quick entry is macOS only for now; the Windows app has no equivalent yet.

A bridge for Claude in Chrome

Claude in Chrome is a browser extension and works on its own: its side panel does not need the desktop app. What does need the app is Claude driving your Chrome from somewhere else, as when a Cowork task or a Claude Code session opens pages in your signed-in browser. For that, Anthropic says the desktop app must be open and connected. Permissions and safety are covered in Claude in Chrome.

The Code tab

The desktop app also includes Claude Code, as a Code tab next to chat, with no separate install. How it compares with the terminal and the VS Code extension is in Claude Code desktop vs CLI vs VS Code.

Installing it on Windows and Mac

Download it from Anthropic’s download page (opens in a new tab), which offers a universal macOS build, Windows builds for x64 and ARM64, and a Linux beta for Ubuntu and Debian.

  • Mac: macOS 11 (Big Sur) or later. Open the downloaded file to install, launch Claude from Applications and sign in.
  • Windows: Windows 10 or later. Run the installer, accept the Windows UAC prompt, launch Claude from the Start menu and sign in. Pick the ARM64 build on an ARM-based Windows laptop.
  • Windows and Cowork: install with administrator rights. Anthropic’s Windows deployment guide (opens in a new tab) says people without admin rights can install Claude, but Cowork on desktop will not be available, and that Cowork needs the Windows Virtual Machine Platform feature. Virtual machines and VDI hosts without nested virtualisation cannot run it.
  • Linux: a beta for Ubuntu 22.04 or later and Debian 12 or later, installed with apt; computer use and dictation are not available there.
  • Companies: IT can deploy the app centrally, as MSIX packages on Windows, and Owners on Team and Enterprise plans can switch on an allowlist that limits which desktop extensions people may install.

The full per-system steps are on Anthropic’s page on installing Claude Desktop (opens in a new tab).

What is the same on both

  • Your account and plan. There is nothing to buy separately; the app signs in to the same account.
  • Chats, projects and memory. A conversation started in the browser is in the app, and the other way round.
  • Remote connectors. Anything added as a connector by URL, including custom connectors to remote MCP servers, works in both once you have connected it.
  • Artifacts, file uploads, web search and research.
  • Cowork sessions started anywhere, which you can pick up on either, and scheduled tasks, which run in the cloud whichever you used to set them up.

When the web app is enough

Stay in the browser if all of these are true: the tools you connect Claude to are online services with remote connectors; you are happy to upload the files a chat needs; and you do not want Cowork working in your local folders or apps. That covers most writing, research and analysis, and it suits locked-down work laptops where installing software is a request to IT. It is also the only option on a machine you do not own.

Install the app when any one of these is true: you want a local MCP server or a desktop extension, you want Cowork to work in folders on your computer or drive other apps, you want Claude to drive your own Chrome from a task, or you are on a Mac and want quick entry. The cost is small; the app and the browser can be used side by side.

A board both can reach

Because remote connectors work on every surface, a task board connected once is there in the browser, the desktop app, Cowork and mobile. fenbs is a small board built for that: add https://fenbs.ai/api/mcp as a custom connector, sign in in the browser, and tick what Claude may do, read, write or comment. It then acts with your role on the board, sees tasks in To Do, Next Up, In Progress and Completed, and every change it makes is recorded in History under its own name. No config file, no local process, and nothing that only works on one machine.

Related

Connect in two minutes with Claude and fenbs. What connectors can reach: Claude connectors explained. The protocol underneath: what MCP is.

Questions people ask.

Is the Claude desktop app free?

The app itself is a free download and works with any Claude account, including the free plan. What you can do in it depends on your plan: Cowork, for example, is on paid plans only.

Is there a Claude desktop app for Windows?

Yes. It runs on Windows 10 or later, with builds for x64 and ARM64. Install it with administrator rights if you want Cowork, which also needs the Windows Virtual Machine Platform feature.

Can I use MCP servers in Claude on the web?

Remote MCP servers, yes, as custom connectors, and they then work on every surface. Local MCP servers and desktop extensions run on your computer and work only in the desktop app and Claude Code.

Do I need the desktop app to use Claude Code?

No. The desktop app includes Claude Code as its Code tab, but Claude Code also runs in a terminal, in VS Code and JetBrains, and on the web at claude.ai/code.

Start with one thing.

There is nothing to set up first. Write one line and you’ve started.