--- title: How to install community MCP servers description: You don't have to build MCP servers from scratch. Hundreds of community servers are ready to install in minutes. Here is how to find them, configure them, and start using them with the Filesystem server as our walkthrough example. author: FractionalSkill ---

How to install community MCP servers

Building your own MCP server teaches you how the protocol works. But here's what changes the math on MCP for most operators: you don't have to build anything to start getting value from it.

MCP is an open standard. That means anyone can publish a server, and hundreds of developers already have. File access, databases, note-taking apps, cloud storage, APIs for tools you already use. The community has built servers for all of it. You find one, copy a config block, restart Claude Desktop, and the new tools appear.

This guide walks through the full process using the Filesystem MCP server, one of the most practical community servers available. By the end you'll know how to find, install, and configure any third-party server, not only this one.

Where to find community MCP servers

The central hub for community servers is the official MCP protocol GitHub repository. Anthropic and the broader developer community maintain a collection of reference servers at github.com/modelcontextprotocol/servers. Each server lives in its own folder with documentation, source code, and installation instructions.

What to look for when evaluating a server:

• README quality. A well-documented server tells you what tools it exposes, how to configure it, and what permissions it needs. If the README is sparse, move on. There are enough options that you don't need to reverse-engineer anything.
• Install method. Most community servers support npx, which means you can run them without cloning a repository or installing anything permanently on your machine. Docker is the other common option but adds more setup.
• Tool list. Every MCP server exposes a specific set of tools. Read the list before installing. If a server exposes 3 tools and only 1 is relevant to your work, it might not be worth the configuration.

Beyond the official repository, individual tool makers publish their own MCP servers in their docs. Search for [tool name] MCP server and you'll often find setup instructions specific to Claude Desktop.

> Start with proven servers. The reference servers in the official repository are well-tested and actively maintained. Third-party servers from unknown developers may work fine, but inspect the documentation and source code before granting file or API access.

Install the Filesystem server step by step

The Filesystem MCP server gives Claude Desktop read and write access to specific folders on your computer. Not your entire machine. Only the directories you explicitly allow. That access control is built into the configuration.

Here is the full install process.

Step 1: Open your Claude Desktop config file. In Claude Desktop, go to Developer Settings. This opens or reveals your claudedesktopconfig.json file. This is the same config file used for any MCP server you've added before.

Step 2: Add the Filesystem server entry. Paste the following into your config. If you already have other servers configured, add the filesystem key inside the existing mcpServers object.

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/yourname/Documents",
        "/Users/yourname/Projects"
      ]
    }
  }
}

The last entries in the args array are your allowed directories. Replace those paths with the actual folders you want Claude to access. Add as many as you need, separated by commas.

Step 3: Save the file and restart Claude Desktop. MCP servers load at startup. Editing the config mid-session won't take effect until you fully quit and reopen the app.

Step 4: Verify the connection. Start a new conversation in Claude Desktop. You should see the server's tools listed in the tools panel. The Filesystem server exposes 13 tools out of the box.

That's the entire installation. No git clone, no dependency installs, no build steps. The npx command pulls the server package on demand and runs it.

> Need Node.js? The npx command requires Node.js installed on your machine. If you get an error about npx not being found, install Node.js from nodejs.org first. Copy and paste any error messages into your preferred AI model for help, the fix is usually one terminal command.

What the Filesystem server can actually do

Once installed, the server gives Claude Desktop 13 distinct tools for working with files and folders inside your allowed directories. Here is the complete list.

Here is what that looks like in practice. You ask Claude Desktop a plain English question and it selects the right tool automatically.

You: What files are in my Projects folder?

Claude: Using list_directory on /Users/yourname/Projects...

  [DIR]  client-acme/
  [DIR]  client-watson/
  [DIR]  internal-tools/
  [FILE] notes.md
  [FILE] quarterly-plan.md

You: What packages does the client-acme project use?

Claude: Using read_text_file on /Users/yourname/Projects/client-acme/package.json...

  Dependencies:
  - express: ^4.18.2
  - dotenv: ^16.3.1
  - axios: ^1.6.0

You: Create a summary.md file in client-acme with a project overview based on the package.json and README.

Claude: Using read_text_file on README.md...
        Using write_file to create summary.md...

  Created /Users/yourname/Projects/client-acme/summary.md

Each tool invocation triggers a permission prompt. You approve, deny, or set it to always allow. The same permission model you're used to from other MCP servers.

The Obsidian vault use case and beyond

The Filesystem server gets particularly interesting when you point it at structured knowledge you already maintain.

> Practical use case: Obsidian vaults. If you take notes in Obsidian, all of your notes are markdown files stored locally on your machine. Point the Filesystem server at your vault folder and Claude Desktop can search your notes, read specific files, create new notes, and even organize content across folders. You get an AI assistant that has full context on everything you've written, without uploading anything to the cloud.

The same pattern applies to any local folder structure where you keep reusable content. Client proposal templates. SOPs saved as markdown. Meeting note archives. Research folders organized by topic. Anywhere you've built a local knowledge base, the Filesystem server turns it into something Claude can query and build on.

This is the real takeaway from installing your first community server. You didn't write any code. You didn't build an API integration. You copied a config block, pointed it at folders you care about, and got 13 new capabilities in Claude Desktop.

That's the entire premise of the MCP protocol at work. Developers build servers once, publish them, and every MCP-compatible client can use them. The Filesystem server is one option out of hundreds. The installation pattern is the same for all of them: find the server, copy the config, set your parameters, restart the app.

Pick the next server that matches a tool you already use daily. The workflow for installing it is identical to what you did here.