npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@schlegel/mcp-sync

v0.2.0

Published

Project-first MCP server manager. Like dotenv + Homebrew for MCP servers.

Downloads

188

Readme

mcp-sync

Like .env + Homebrew for MCP servers.

npm CI TypeScript License: MIT MCP Node


The Problem

MCP configs are a mess:

  • Scattered across Claude Desktop, Cursor, and Claude Code
  • Global configs pollute every project with irrelevant servers
  • No version control -- team members set up MCP manually
  • Absolute paths break across machines
  • No way to check if your servers actually work

The Solution

One mcps.json per project. Version controlled. Synced everywhere.

npx @schlegel/mcp-sync init

Or use a custom config filename:

npx @schlegel/mcp-sync --config .mcp-sync.json init

Quickstart

# Initialize in your project (creates mcps.json)
npx @schlegel/mcp-sync init

# Start with a template (web, python, fullstack, devops, data, minimal)
npx @schlegel/mcp-sync use fullstack

# Or add servers manually
npx @schlegel/mcp-sync add-json filesystem '{"command":"npx","args":["-y","@modelcontextprotocol/server-filesystem","${workspaceFolder}"]}'

# See what you've got
npx @schlegel/mcp-sync list

# Sync to all your AI tools
npx @schlegel/mcp-sync sync

# Health check
npx @schlegel/mcp-sync doctor

Using a Custom Config Filename

By default, mcp-sync uses mcps.json. You can specify a custom filename with the --config flag:

# Use .mcp-sync.json instead
npx @schlegel/mcp-sync --config .mcp-sync.json init
npx @schlegel/mcp-sync --config .mcp-sync.json add-json myserver '{"command":"echo"}'
npx @schlegel/mcp-sync --config .mcp-sync.json sync

# Or any other filename you prefer
npx @schlegel/mcp-sync --config my-servers.json init

The --config flag must come before the command name.


CLI Preview


How It Works

mcps.json (in your project root)
    |
    |--- mcp-sync sync --->  Claude Desktop config
    |--- mcp-sync sync --->  Cursor .cursor/mcp.json
    |--- mcp-sync sync --->  Claude Code .mcp.json
  1. Define MCP servers in mcps.json (default) or use --config for a custom filename
  2. Use workspace variables for portability (${workspaceFolder}, ${env:API_KEY})
  3. Commit to git -- your whole team gets the same MCP setup
  4. Run mcp-sync sync to push configs to all your AI tools
  5. Run mcp-sync doctor to verify everything works

Config Format

The config file (default: mcps.json) uses this format:

{
  "$schema": "https://raw.githubusercontent.com/schlegel/mcp-sync/main/schema/mcp-sync.schema.json",
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "${workspaceFolder}"]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_TOKEN": "${env:GITHUB_TOKEN}"
      }
    }
  },
  "sync": {
    "clients": ["claude-desktop", "cursor", "claude-code"]
  }
}

Note: You can name your config file anything you want using the --config flag. For backward compatibility with older projects, you might use .mcp-sync.json, or choose any name that fits your workflow.

Workspace Variables

| Variable | Resolves To | |----------|------------| | ${workspaceFolder} | Directory containing config file (e.g., mcps.json) | | ${env:VAR_NAME} | Environment variable value | | ${home} | User home directory | | ${platform} | win32, darwin, or linux |

Variables stay as templates in your config file and are resolved at sync time -- making configs portable across machines.


Commands

Global Options

| Option | Description | |--------|-------------| | -c, --config <filename> | Config filename (default: mcps.json) | | -V, --version | Show version number |

Command List

| Command | Description | |---------|-------------| | mcp-sync init | Create mcps.json in current project | | mcp-sync add <name> | Add server interactively | | mcp-sync add-json <name> <json> | Add server from JSON string | | mcp-sync remove <name> | Remove a server | | mcp-sync list | List all configured servers | | mcp-sync status | Quick status overview | | mcp-sync sync | Sync to Claude Desktop / Cursor / Claude Code | | mcp-sync sync --dry | Preview sync without writing files | | mcp-sync doctor | Health check all servers + system deps | | mcp-sync import | Import from existing client configs | | mcp-sync use <template> | Apply preset template | | mcp-sync env | Audit environment variables referenced in config | | mcp-sync diff | Show diff between config and client configs | | mcp-sync enable <name> | Enable a disabled server | | mcp-sync disable <name> | Disable a server without removing it | | mcp-sync export | Export resolved config as JSON (pipe-friendly) |


Templates

Get started fast with prebuilt server bundles:

npx @schlegel/mcp-sync use web        # filesystem + GitHub + Puppeteer
npx @schlegel/mcp-sync use python     # filesystem + GitHub + memory
npx @schlegel/mcp-sync use fullstack  # filesystem + GitHub + Postgres + Puppeteer + memory
npx @schlegel/mcp-sync use devops     # filesystem + GitHub + Docker
npx @schlegel/mcp-sync use data       # filesystem + Postgres + SQLite + memory
npx @schlegel/mcp-sync use minimal    # filesystem + memory

Templates merge into your existing config -- they never overwrite servers you already have.


Comparison

| Feature | mcp-sync | MCPM.sh | mcptools | MetaMCP | |---------|-------|---------|----------|---------| | Project-first config | mcps.json per project (customizable) | Global profiles | Global aggregation | Docker proxy | | Multi-client sync | Claude Desktop + Cursor + Claude Code | Partial | No | No | | Git-friendly | Workspace variables | No | No | No | | Zero install | npx @schlegel/mcp-sync | pip install | Go binary | Docker | | Health checks | JSON-RPC ping | No | No | No | | Import existing | From all clients | No | Scan only | No | | Templates | 6 presets | No | No | No |


Sync Targets

| Client | Config Path | |--------|-------------| | Claude Desktop | %APPDATA%\Claude\claude_desktop_config.json (Win) / ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) | | Cursor | .cursor/mcp.json (project) | | Claude Code | .mcp.json (project) |

mcp-sync merges your servers into existing configs -- it never deletes servers you added manually.


Migration from .mcp-sync.json

If you have an existing project using .mcp-sync.json:

Option 1: Continue using .mcp-sync.json

# Always specify --config flag
npx @schlegel/mcp-sync --config .mcp-sync.json list
npx @schlegel/mcp-sync --config .mcp-sync.json sync

Option 2: Rename to mcps.json

# Simply rename the file
mv .mcp-sync.json mcps.json

# Then use without --config flag
npx @schlegel/mcp-sync list
npx @schlegel/mcp-sync sync

Option 3: Use shell alias

# Add to your .bashrc or .zshrc
alias mcp-sync='npx @schlegel/mcp-sync --config .mcp-sync.json'

Requirements

  • Node.js >= 20.0.0
  • npm >= 8.0.0

License

MIT


Built by Aditya Gaurav