Claude Desktop Setup

Tool use without the terminal. This is the one.

Safety first. Claude is a powerful tool with real access to your systems. Before you set it up, read the AI Safety page — nine rules for keeping your work safe, your data backed up, and your boundaries enforced.

Why Desktop, not the browser

The browser version of Claude (claude.ai) is a chatbot. You type, it types back. That's fine for asking questions. It's not YOU++.

YOU++ requires tool use — the AI reading your files, querying your databases, connecting to your email, running scripts, pulling Jira tickets. The browser can't do that. It's walled off from your computer. It can only see what you paste into the chat window.

Claude Desktop is a native app that looks like iMessage but connects to your actual systems through small connector programs called MCP servers (short for Model Context Protocol — a standard way for Claude to talk to other software). It's the graphical equivalent of the CLI — same capabilities, different interface. If you're not a terminal person, this is your door in.

What MCP servers do

An MCP server is a small program that gives Claude access to an external system. Each server handles one integration. You configure them in a JSON file (a plain-text settings file — think of it as a recipe card that tells Claude which tools to load). Claude Desktop connects to them automatically on launch.

Real examples from the workflows on this site:

Gmail MCP — Claude reads your inbox, searches messages, creates drafts. This is how the morning briefing summarizes email.
Jira MCP — Claude queries tickets, checks status, reads comments. This is how ticket triage works without opening a browser tab.
Filesystem MCP — Claude reads and writes files on your local machine. Project documents, config files, data exports.
Snowflake MCP — Claude runs SQL queries against your data warehouse. This is the fallback path for the six-country audit.

Without MCP servers, Claude Desktop is just a pretty chatbot. With them, it's an agent that can see your world and act in it.

Install

Download Claude Desktop from claude.ai/download
Install it (Mac: drag to Applications. Windows: run the installer.)
Sign in with your Anthropic account (Pro or Max subscription required for full use)
Open it. You'll see a chat interface. This is the baseline — no tools yet.

Add MCP servers

Don't want to edit JSON by hand? Ask Claude to do it. If you're already running Claude Code in the terminal, tell it what MCP servers you want and it will edit the config file for you. Claude configuring Claude. It knows the format, the file paths, and the available servers. You just say what you want connected.

MCP servers are configured in a JSON file:

Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

See the JSON format (if you want to edit it yourself)

npx is a tool that comes with Node.js — it downloads and runs packages on the fly.

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/you/Documents"
      ]
    },
    "gmail": {
      "command": "npx",
      "args": ["-y", "@anthropic/gmail-mcp-server"]
    }
  }
}

Each key is a server name. Each value tells Claude how to start it.

Restart Claude Desktop after changing the config. The servers appear in the chat interface — you'll see tool icons indicating what's connected.

The mental model

Think of Claude Desktop as a colleague sitting at your desk, logged into your systems. It can see your files. It can read your email. It can check your tickets. It can query your databases. But it doesn't do anything without you telling it to — and it asks before taking any action that changes state.

The same principle from every other page on this site: you think, it executes. The difference between the browser and the desktop app is that the desktop app can actually reach your stuff.

When to use Desktop vs. CLI

Use Claude Desktop when:

You prefer a visual chat interface
You want to drag files into the conversation
You're doing MCP-connected work (email triage, ticket review, database queries)
You want Projects with persistent instructions and reference docs

Use Claude Code (CLI) when:

You're working inside a codebase or project directory
You want the AI to run commands directly on your computer
You need version tracking (git), file editing, and the ability to build and test software
You want skills — saved instructions that run multi-step tasks with a single command, like a macro
You're building something — a website, a distribution system, a report

Most of the work on this site — the memoir production, the book factory, the Snowflake (cloud database) audits, this website — was done in the CLI. But the morning briefing with email and Jira triage runs great in Desktop. Use whichever fits the task. They're the same brain with different hands.

Your first project

You've got the tool. Now use it on something real.

Download this file: youplus-starter.md

Read it yourself first. This file contains instructions that an AI will follow on your behalf. That's software. Before you hand it to Claude, open it in any text editor and read every line. It's plain text — no code, no scripts, nothing that runs on its own. Confirm you're comfortable with what it asks Claude to do. If anything looks wrong, don't use it.

Then drag it into your Claude Desktop chat and say:

"Help me with my first project."

It will walk you through solving a small, real problem you actually have. By the end you'll have something you can use today. If you like the pattern, you can turn it into a skill — a saved command that runs the same workflow anytime you type its name. Or toss it and build something new in five minutes. That's the point.

Next steps

Read the safety page first. Trust the tool. Verify the output. Back everything up.
Want the terminal instead? More power, more automation.
See real workflows — patterns that use both interfaces.
Case studies — what gets built when you combine thinking with tool use.

Disclosure: This page was generated by Claude (Anthropic) under Bill's direction. MCP configuration details are current as of April 2026.