pletzenauer — digital consulting

Installing Claude Desktop: my approach on Windows, macOS, and Linux

Before anyone clicks the installer, I clarify three things: which plan, which data is allowed in, and which MCP servers come later. That prevents rework.

Three things to consider first

Which plan, which login. Free, Pro, Team, or Enterprise – the app holds only one login per profile. Anyone working privately and professionally in parallel is better off planning two user profiles.

Which data goes in. I clarify this in writing before the app is unlocked. It prevents discussions once the first knowledge bases appear.

Think about MCP servers early. Anyone who will connect MCP servers later should know the configuration path up front. A short advance list of the desired integrations saves duplicated work.

Installation per operating system

Windows 10 and 11

Download the installer from claude.ai/download, run it with admin rights, accept the license terms. Configuration path: %APPDATA%Claude. There is no official support for Windows 7 and 8.

macOS (Apple Silicon and Intel)

Load the universal image, drag the application into the Applications folder. On first launch, allow the sign-in in Keychain Access. Configuration path: ~/Library/Application Support/Claude. The Homebrew cask claude works as well.

Linux (Ubuntu, Fedora, Arch)

Ubuntu 22.04+: official .deb via apt. Fedora 38+: .rpm via dnf. Arch: AppImage or community repository. Configuration path: ~/.config/Claude.

The five steps I always recommend after installation

Start with real tasks. Not with gimmicks, but with two or three genuine work tasks: research, summarizing, writing.

Set up the keyboard shortcut. The global shortcut saves several minutes of context switching per day. On macOS it is Cmd+Esc by default.

Add the configuration path to your backup. It contains skills, knowledge bases, and MCP configuration. Anyone who forgets it will regret it at the next device change.

Define update behavior for the team. In the team plan, a rollout window is advisable. That avoids surprises after an update.

Prepare the MCP server list. Document briefly which data sources Claude may reach. That saves later discussions with IT.

Updating and uninstalling cleanly

The app updates itself on start. Before a team rollout I check the release notes for changes to MCP behavior and the skill API.

Uninstalling is more than the system tool. The configuration directory has to be deleted manually – otherwise skills, caches, and MCP entries remain.

Frequently asked questions

Which operating systems does Claude Desktop run on?

Windows 10 and 11, macOS with Apple Silicon or Intel, and Linux (Ubuntu 22.04+, Fedora 38+, Arch). Windows 7 and 8 have no official support.

Where is the Claude Desktop configuration file?

On macOS under ~/Library/Application Support/Claude, on Windows under %APPDATA%Claude, on Linux under ~/.config/Claude. Know this path early if you plan to use MCP servers.

What should I clarify before installing?

Three things: which plan and login, which data may enter the app, and which MCP servers will follow. That avoids duplicated work.

Can I separate personal and work use?

Each profile holds only one login. If you use both, plan for two user profiles.