Claude Type

You can extend Claude Desktop with a set of MCP servers that run locally and coordinate through a unified configuration. These servers let you perform file operations, manage Git and GitHub interactions, run web searches, automate browser tasks, execute shell commands, and fetch content from the web, all under tight security and with centralized control. This setup enables powerful development workflows without incurring per-token API costs.

How to use

You interact with the MCP system through an MCP client. Start by configuring the MCP servers you want to run locally, then point your client at the local STDIO endpoints. Use the available servers to perform tasks like editing files, running Git commands, querying GitHub, searching the web with structured results, automating browser tasks, executing shell commands safely, and fetching page content as Markdown.

How to install

Prerequisites: Node.js v18 or higher, Bun runtime, and Claude Desktop installed on your machine. You will also need API keys for Brave Search and Sonar (Perplexity/Sonar) if you plan to use those capabilities.

# Clone the MCP server collection
git clone https://github.com/yourusername/claude-ts-mcps.git
cd claude-ts-mcps

# Install dependencies
bun install

# Optional: verify Node.js and Bun are properly installed
node -v
bun -v

Configuration and startup details

The MCP servers are configured via a single configuration object. Each server is defined with a name, a runtime command, and arguments. Some servers expose environment variables for API keys and tokens. Use the following configuration as the local setup and tailor the environment variables to your own credentials.

{
  "mcpServers": {
    "filesystem": {
      "name": "filesystem",
      "type": "stdio",
      "command": "/Users/username/.bun/bin/bun",
      "args": ["run", "/path/to/claude-ts-mcps/src/filesystem.ts", "/Users/username"]
    },
    "git": {
      "name": "git",
      "type": "stdio",
      "command": "/Users/username/.bun/bin/bun",
      "args": ["run", "/path/to/claude-ts-mcps/src/git.ts"]
    },
    "github": {
      "name": "github",
      "type": "stdio",
      "command": "/Users/username/.bun/bin/bun",
      "args": ["run", "/path/to/claude-ts-mcps/src/github.ts"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_DEFAULT_TOKEN",
        "GITHUB_TOKEN_WORK": "YOUR_WORK_ACCOUNT_TOKEN",
        "GITHUB_TOKEN_PERSONAL": "YOUR_PERSONAL_ACCOUNT_TOKEN"
      }
    },
    "brave-search": {
      "name": "brave_search",
      "type": "stdio",
      "command": "/Users/username/.bun/bin/bun",
      "args": ["run", "/path/to/claude-ts-mcps/src/brave-search.ts"],
      "env": {
        "BRAVE_API_KEY": "YOUR_BRAVE_API_KEY"
      }
    },
    "sonar": {
      "name": "sonar",
      "type": "stdio",
      "command": "/Users/username/.bun/bin/bun",
      "args": ["run", "/path/to/claude-ts-mcps/src/sonar.ts"],
      "env": {
        "PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY"
      }
    },
    "puppeteer": {
      "name": "puppeteer",
      "type": "stdio",
      "command": "/Users/username/.bun/bin/bun",
      "args": ["run", "/path/to/claude-ts-mcps/src/puppeteer/index.ts"]
    },
    "shell": {
      "name": "shell",
      "type": "stdio",
      "command": "/Users/username/.bun/bin/bun",
      "args": ["run", "/path/to/claude-ts-mcps/src/shell.ts"]
    },
    "fetch": {
      "name": "fetch",
      "type": "stdio",
      "command": "/Users/username/.bun/bin/bun",
      "args": ["run", "/path/to/claude-ts-mcps/src/fetch.ts"],
      "env": {
        "CUSTOM_USER_AGENT": "YOUR_CUSTOM_USER_AGENT",
        "IGNORE_ROBOTS_TXT": "false"
      }
    }
  }
}

Security considerations

Files and commands are restricted to predefined directories and allowlisted actions to minimize risk. Never grant broad filesystem or network access. Store API keys securely using environment variables and avoid embedding secrets directly in configuration files.

Notes and troubleshooting

If you modify the configuration, restart Claude Desktop to apply the new MCP server settings. Monitor logs from each server to confirm successful startup and proper handling of requests. If a server fails to start, verify the command path, ensure Bun is installed, and check that the environment variables are correctly set.

Examples of typical workflows

Development workflow: you ask for a new React component, Claude uses filesystem to create files and then runs needed package managers to install dependencies. Research workflow: you request information about complex topics; Claude uses sonar for deep research with citations. Automation workflow: you ask to extract data from a site; Claude uses puppeteer to navigate pages and compile results.

Available tools

filesystem

Manage files with read/write, rename, delete, and archive capabilities within restricted directories.

git

Full Git workflow: init, add, commit, branch, checkout, diff, log, and tags handling.

github

GitHub API access for repositories, issues, PRs, releases, and multi-account management.

brave_search

AI-powered Brave Search integration with API key-based access.

sonar

Perplexity Sonar-based search with multiple models for fast answers and deep research.

puppeteer

Browser automation with 30+ functions for navigation, interaction, and data extraction.

shell

Controlled command execution with allowlists, streaming output, and security restrictions.

fetch

URL content fetching with HTML-to-Markdown conversion and optional user-agent control.