Claude Desktop

Bring Claude, files, and local tools into one desktop workspace.

Claude Desktop is Anthropic’s official desktop client for conversations, files, Projects, Artifacts, Connectors, MCP, and Desktop Extensions. This guide covers installation, MCP extensions, and the correct way to use it with OmniDino.

Official Anthropic Download Open-Source MCP Servers Claude Code Guide

CHAT Desktop Conversations Handle conversations, files, projects, and generated content in a dedicated client.

MCP Local and Remote Tools Access external data and services through MCP and Connectors.

EXT Desktop Extensions Connect local apps and data with one-click extensions.

AI Anthropic Account Client model access is provided through your Claude account and Anthropic services.

Overview

How is Claude Desktop different from Claude Code?

Desktop focuses on graphical conversations, files, and extensions. Claude Code focuses on terminals, repositories, and LLM gateways.

Desktop is Claude’s desktop client, not a general-purpose API client.

It signs in with a Claude account and uses Anthropic’s client model service. MCP can add tools, but it does not replace the underlying model with an arbitrary OpenAI- or Anthropic-compatible gateway.

Claude Desktop Best for chat, file uploads, Projects, Artifacts, Connectors, Cowork, MCP, and desktop extensions.

Claude Code Best for terminal coding, Git, command execution, Hooks, CLAUDE.md, and connecting to an LLM gateway through environment variables.

OmniDino Best for model APIs, unified Keys, and usage billing. To use OmniDino Claude routes directly, use Claude Code or a third-party client that supports custom APIs.

Claude Desktop cannot directly accept an OmniDino Base URL and API Key.

Claude Desktop currently does not expose a ANTHROPIC_BASE_URL gateway configuration entry like Claude Code. Desktop conversations still use Anthropic account services and cannot be redirected to OmniDino by editing ordinary MCP JSON. OmniDino can power a custom MCP server used as a tool, but that creates two separate usage layers: Anthropic usage in Claude Desktop and OmniDino API usage inside the MCP tool.

Download Center

Official clients and open-source GitHub tools.

Claude Desktop itself is closed source and must be downloaded from Anthropic. The development and helper tools below link to GitHub.

Claude Desktop

Anthropic’s official desktop client for macOS, Windows, and gradually released Linux builds.

Official Client macOS Windows Linux Beta

Official Download

MCP

MCP Reference Servers

Official Model Context Protocol reference servers and community indexes for learning MCP structure and choosing servers.

Open Source Reference Tools Resources

GitHub Project

MCPB

MCPB Desktop Extensions

Open format and tools for packaging a local MCP server as an installable Desktop Extension.

Open Source Extension Packaging Desktop

GitHub Project

SDK

TypeScript MCP SDK

Official TypeScript SDK for custom MCP servers, including tools backed by the OmniDino API.

TypeScript Server Client Open Source

GitHub Project

Python MCP SDK

Use Python to build local or remote MCP servers connected to OmniDino APIs or internal business data.

Python FastMCP Tools Open Source

GitHub Project

Visual Studio Code

For developing and reviewing MCP servers, JSON configuration, logs, and OmniDino API tool code.

Editor Terminal Git Open Source

GitHub Project

Do not download modified Claude Desktop builds from file-sharing sites, forums, or unknown repositories. Claude Desktop has no official open-source installer repository. Use Anthropic’s download page.

Install Claude Desktop

Choose your operating system.

Windows Installation

Download the Windows installer from Anthropic, install it, and open Claude from the Start menu.

Use the official Anthropic download page.

Use a supported Windows version.

Check Extensions and Connectors in Settings.

Open Official Download

Claude Desktop · Windows ●

New chat

Projects

Connectors

Extensions

Analyze the project brief I uploaded and list the next actions.

I will read the files first, then organize the goals, risks, and execution steps.

macOS Installation

Download the correct macOS build, move Claude to Applications, and sign in.

Confirm that macOS meets the current minimum version.

The first launch may require system security approval.

Local MCP configuration is usually stored in the user Library directory.

Manage Desktop Extensions in Settings.

Open Official Download

Claude Desktop · macOS ●

Claude

Cowork

Projects

Extensions

Connect my local file tool and read the specified directory.

After authorization, I can access approved directories through the installed MCP Extension.

Linux Installation

Anthropic is gradually releasing an official Linux Desktop beta. Check the download page for supported distributions, architectures, and installation methods.

Prefer Anthropic’s official Linux package.

Avoid outdated third-party repackaging guides.

Check amd64, arm64, and distribution compatibility.

Beta features may differ from macOS and Windows.

Check Linux Downloads

Claude Desktop · Linux Beta β

Chat

Files

MCP

Settings

Read this log file and identify error patterns.

I will inspect the file first, then group issues by time and error type.

Claude Desktop’s interface and features change over time. Menus may appear as Extensions, Connectors, Cowork, Settings, or other names depending on the current version.

MCP and Desktop Extensions

Extend Claude with tools rather than replacing the Claude model.

Desktop Extensions package local MCP servers. Remote Connectors connect to remote MCP services by URL.

Local Files

Read and process files only in approved directories. Expose the smallest required scope.

CAL

Calendar and Email

Connect calendars, email, and collaboration tools through extensions or Connectors.

Database Tools

Query test databases and prefer read-only accounts in production.

WEB

Remote MCP

Connect to server-hosted tools using Streamable HTTP and OAuth.

MCPB

Installable Extension

Package a local MCP server as an installable extension to simplify dependencies and configuration.

OMNI

OmniDino Tools

You can build an MCP server that lets Claude call OmniDino APIs for model testing, image generation, or internal business tasks.

Manual Local MCP

JSON configuration is available for legacy or development scenarios.

New users should prefer Desktop Extensions. Edit configuration files manually only for development or troubleshooting.

Configuration File Locations

Local MCP configuration paths differ by operating system.

macOS ~/Library/Application Support/Claude/claude_desktop_config.json

Windows %APPDATA%\Claude\claude_desktop_config.json

Linux Refer to the current official documentation.

After changing configuration, fully quit Claude Desktop, including tray or menu-bar processes, then restart it.

Local MCP Configuration Structure

{ "mcpServers": { "my-local-tool": { "command": "/absolute/path/to/your-mcp-server", "args": ["--stdio"], "env": { "EXAMPLE_TOKEN": "Use secure system storage or a controlled environment variable" } } } }

Do not copy unknown npx -y package-name configuration from old tutorials. Before running anything, review the package repository, maintenance status, dependencies, and permissions.

Using OmniDino Correctly

Three supported approaches.

Claude Code + OmniDino

This is the clearest option for direct OmniDino Claude API access. Claude Code supports LLM gateway environment variables.

Third-Party Client + OmniDino

Choose a client that explicitly supports Anthropic Base URL, Messages, and custom API Keys.

Claude Desktop + OmniDino MCP

Build an MCP server with OmniDino as the tool backend. This does not replace the Claude model inside Desktop.

OmniDino MCP Tool Flow Example

Claude Desktop ↓ Calls an MCP Tool Your OmniDino MCP Server ↓ Uses a securely stored server-side Key https://api.omnidino.com/v1 ↓ OmniDino model or image endpoint ↓ MCP Server returns the result to Claude Desktop

Complete Workflow

From installation to your first MCP tool.

Install Claude Desktop from Anthropic

Download the official build for your operating system and avoid third-party repackaged clients.

Sign in to Your Claude Account

Claude Desktop model access depends on your Claude account and available plan.

Check Extensions and Connectors

Review installable extensions, remote Connectors, and organization policies in Settings.

Start with Low-Permission Tools

Start with read-only files, a test calendar, or a development database. Do not expose production systems directly.

Test an MCP Call

Ask Claude to list available tools, then run a minimal task that does not modify data.

Build an OmniDino MCP as Needed

Use the official TypeScript or Python SDK to expose only the required OmniDino APIs as clearly scoped tools.

Protect the OmniDino API Key

Store the Key server-side or in secure storage. Never include it in public extensions or screenshots.

Review Both Usage Systems

Anthropic usage in Claude Desktop and OmniDino usage inside MCP are separate and must be reviewed independently.

FAQ

Troubleshoot configuration issues here.

Not currently. Claude Desktop signs in with a Claude account and does not expose a custom Anthropic Base URL and API Key gateway for ordinary users. Use Claude Code or a client with custom Anthropic API support for direct OmniDino Claude routing.

No. MCP adds tools to Claude but cannot replace Claude Desktop’s base model. A custom MCP tool can call OmniDino, while Desktop itself remains powered by Anthropic models.

The official Linux version is being rolled out gradually or remains in beta. Availability may vary by region and architecture. Use Anthropic’s current download page and avoid outdated repackaging guides.

Check JSON syntax, absolute command paths, dependencies, environment variables, and logs. Fully quit and reopen Claude Desktop after changes. Prefer the Desktop Extensions manager in Settings.

Desktop Extensions package a local MCP server, dependencies, configuration, and icons into an installable extension. Manual JSON is better suited to development, debugging, and custom servers.

Features may depend on client version, plan, organization policy, region, and staged rollout. Update Claude Desktop and review Settings and Anthropic release notes.

Use least privilege and expose only necessary directories. Never share your entire home directory, SSH keys, browser data, or production credential directories with a file MCP. Review extension permissions regularly.

Ordinary Claude Desktop conversations do not pass through OmniDino, so no record is expected. Records appear only when a custom MCP tool calls OmniDino or when Claude Code or another client connects to OmniDino.

Still having trouble with Claude Desktop or MCP?

When contacting support, provide your operating system, Claude Desktop version, extension or MCP name, configuration method, error message, and logs. Hide API Keys, access tokens, and sensitive paths.

[email protected]

Continue to the next client guide.

Claude Code

Use Claude models directly in the terminal through the OmniDino Messages Gateway.

Gemini CLI

Install Gemini CLI and configure a suitable model, tools, and development workflow.