Awesome MCP Servers for Claude Desktop Cowork

One of the defining innovations of Claude Cowork is the Model Context Protocol (MCP). MCP allows you to extend Claude's intelligence by connecting it to external data sources and execution engines via secure, standardized APIs.

Instead of writing custom scripts for every tool, you can plug in community-maintained MCP servers. This guide curates the absolute best open-source MCP servers for productivity and development, providing instant setup codes for your claude_desktop_config.json.

Table of Contents

1. What is an MCP Server?
2. Top 5 Open-Source MCP Servers
3. Example Combined Configuration
4. Best Practices for Running MCPs

What is an MCP Server?

An MCP Server is a local or remote process that exposes a set of "Tools" and "Resources" to Claude.

When configured, Claude Desktop detects these tools at startup and automatically routes relevant user requests to them. For example, if you ask Claude, "Read my Google Calendar to find open slots today", Claude calls the Google Calendar MCP server to fetch the data.

Top 5 Open-Source MCP Servers

Here are the most useful, battle-tested MCP servers you should configure today:

1. File System MCP (@modelcontextprotocol/server-filesystem)

Allows Claude to read, write, edit, and traverse files on your computer inside allowed directories.

• Why use it: This is the default backbone of Cowork's file manipulation abilities.
• Configuration:

"filesystem": {
  "command": "npx",
  "args": [
    "-y",
    "@modelcontextprotocol/server-filesystem",
    "C:\\Users\\YourUsername\\Desktop",
    "C:\\Users\\YourUsername\\Downloads"
  ]
}

2. GitHub MCP (@modelcontextprotocol/server-github)

Allows Claude to view repositories, create issues, search code, commit edits, and manage pull requests.

• Why use it: Ideal for developers who want Claude to manage version control and PR pipelines autonomously.
• Configuration (Requires a GitHub Personal Access Token):

"github": {
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-github"],
  "env": {
    "GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token_here"
  }
}

3. SQLite Database MCP (@modelcontextprotocol/server-sqlite)

Grants Claude standard SQL query capabilities to inspect, update, and create local database files.

• Why use it: Excellent for analyzing local databases, extracting metrics, and generating reports from local business datasets.
• Configuration:

"sqlite": {
  "command": "npx",
  "args": [
    "-y",
    "@modelcontextprotocol/server-sqlite",
    "--db-path",
    "C:\\Users\\YourUsername\\ClaudeWork\\analytics.db"
  ]
}

4. Brave Search MCP (@modelcontextprotocol/server-brave-search)

Connects Claude to Brave's web search API to query current search results, URLs, and summaries.

• Why use it: Keeps Claude updated with real-time web facts, avoiding hallucination on current news or document links.
• Configuration (Requires a Brave Search API key):

"brave-search": {
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-brave-search"],
  "env": {
    "BRAVE_API_KEY": "your_brave_api_key_here"
  }
}

5. Puppeteer Web Scraper MCP (@modelcontextprotocol/server-puppeteer)

Allows Claude to open local headless browser windows to scrape page text, take screenshots of sites, and click elements.

• Why use it: Essential for complex web data collection or automated testing.
• Configuration:

"puppeteer": {
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-puppeteer"]
}

Example Combined Configuration

To run multiple servers, group them in your claude_desktop_config.json under the mcpServers object:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "C:\\Users\\YourUsername\\ClaudeWork"]
    },
    "puppeteer": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-puppeteer"]
    },
    "sqlite": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-sqlite", "--db-path", "C:\\Users\\YourUsername\\ClaudeWork\\db.sqlite"]
    }
  }
}

Best Practices for Running MCPs

• Avoid Globally Installed Packages: Use npx -y to run the servers. This automatically downloads the latest version at launch without polluting your global node modules library.
• Manage Node Environment: Make sure your local terminal has a valid node installation on its environment PATH. If you get a connection failure, test the npx command in your terminal first.
• Scope File Access: Only list directories you actually intend to read/write under the filesystem args. Do not pass root directories like / or C:\ as this is a safety hazard.

Last updated: June 15, 2026

This article is part of CoworkHow.com, an independent resource for Claude Cowork users. We are not affiliated with Anthropic.