Getting StartedΒ·
beginner
Β·8 min readΒ·Apr 4, 2026

How to Set Up Your First MCP Server in 5 Minutes

A quick-start guide to installing and configuring your very first MCP server with Claude Desktop. Get up and running in minutes.

setupquickstartClaude Desktopinstallationbeginner
Interactive Tool
1-Click Export

Generate & Validate Multi-Client MCP Config

One-click export with environment variables & path locators for Claude Desktop, Cursor, Windsurf, and OpenAI Codex CLI.

Open in Generator

Set Up Your First MCP Server in 5 Minutes

This guide walks you through installing your first MCP server (the Filesystem server) and connecting it to Claude Desktop, turning a standard LLM chat interface into a capable local coding assistant.

Prerequisites

  • β–ΈNode.js 18+ installed on your system (node -v to check)
  • β–ΈClaude Desktop application (download from anthropic.com)
  • β–ΈBasic familiarity with your operating system's terminal or command line.

Step 1: Install Claude Desktop

Download and install Claude Desktop from the official Anthropic website. This will act as your MCP host β€” the application that connects to and coordinates your MCP servers.

Step 2: Locate Your Configuration File

Claude Desktop stores its MCP connection string configuration in a JSON file:

  • β–ΈmacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • β–ΈWindows: %APPDATA%\Claude\claude_desktop_config.json

Create this file if it doesn't already exist.

Step 3: Add Your First Server

Let's start with the official filesystem MCP server. Edit your config file:

json
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "C:/Users/yourusername/Documents/sandbox"
      ]
    }
  }
}

Best Practices

[!WARNING] Replace C:/Users/yourusername/Documents/sandbox with a real, absolute path on your system. Always use forward slashes / even on Windows paths. Backslashes \ act as escape characters in JSON and will silently corrupt your file paths.

  • β–ΈSandbox Your Environments: For your first server, point the path to an empty directory or a safe "sandbox" project. Do not point it to your root drive C:/.

Step 4: Restart Claude Desktop & Test

  1. β–ΈQuit Claude Desktop completely (do not just close the window; right-click and exit the application from the system tray or macOS menu bar).
  2. β–ΈRelaunch Claude Desktop.
  3. β–ΈLook at the chat input box. You should now see a Hammer icon (πŸ”¨) in the bottom-right corner. Hovering over it will list the tools exposed by the filesystem server: read_file, write_file, list_directory, etc.
  4. β–ΈTry asking Claude:

    "List the files inside my configured sandbox folder and write a hello.txt file inside it."

Troubleshooting Guide

If the Hammer icon does not appear, check the local logs generated by the host:

  • β–ΈWindows: %APPDATA%\Claude\logs\mcp.log
  • β–ΈmacOS: ~/Library/Logs/Claude/mcp.log

Common Error: command not found: npx

This means Node.js is not added to your system $PATH, or Claude Desktop was launched in an environment where it couldn't inherit your user's path. Specify the absolute path to your npx.cmd (Windows) or npx (macOS/Linux) binary inside the "command" property.

Common Error: Invalid JSON Format

Ensure your JSON contains matching double quotes and no trailing commas. Even a single syntax error in claude_desktop_config.json will cause Claude to ignore the entire file silently. Validate your config via any online JSON parser.

Ready to Deploy?

Build your full agent toolstack in the Visual Generator

Combine How to Set Up Your First with databases, search APIs, and memory graphs in a single configuration file.

Customize in Generator

Related Guides