CLI ToolsMay 12, 2026·2 min read

MCP Linker — Sync MCP Servers Across Clients

MCP Linker is a cross-platform app with a curated MCP marketplace to add and sync server configs across clients like Claude Code, Cursor, and VS Code.

MCP Hub
MCP Hub · Community
Agent ready

Safe staging for this asset

This asset is staged first. The copied prompt tells the agent to inspect the staged files and ask before activating scripts, MCP config, or global config.

Stage only · 17/100Policy: stage
Agent surface
Any MCP/CLI agent
Kind
CLI Tool
Install
Stage only
Trust
Trust: Established
Entrypoint
Asset
Safe staging command
npx -y tokrepo@latest install 8b6e5e84-eb8c-5215-8cc3-68b69182371f --target codex

Stages files first; activation requires review of the staged README and plan.

Intro

Stop editing MCP JSON by hand: MCP Linker turns “add this server” into a repeatable UI flow and keeps multiple clients in sync.

Best for: Anyone maintaining MCP setups for multiple clients (Claude Code/Desktop, Cursor, VS Code, Cline, Windsurf, Codex, etc.)

Works with: macOS/Windows/Linux; marketplace + local sync; optional encrypted cloud sync (Pro) per README

Setup time: 5–10 minutes

Key facts (verified)

  • README claims a built-in marketplace with 600+ curated MCP servers.
  • README lists supported clients: Claude Desktop/Code, Cursor, VS Code, Cline, Windsurf, Codex, Roo Code, and more.
  • Homebrew install is brew install --cask mcp-linker after a tap (per README).
  • GitHub: 310 stars · 27 forks; pushed 2026-05-01 (GitHub API verified).

Main

To make MCP configs maintainable:

  1. Treat your MCP server list like dependencies—keep a minimal set and update deliberately.
  2. Use the marketplace flow to add a server once, then sync to multiple clients instead of copy/paste JSON.
  3. Keep environment-specific values (tokens, DB URLs) as per-client secrets, even if the “shape” of config is shared.

This approach reduces drift: your Cursor config and your Claude Code config stop diverging over time.

FAQ

Q: Does it require an LLM to add servers? A: The README says no LLM calls are required for adding/syncing server configs.

Q: Which clients are supported? A: The README lists Claude Desktop/Code, Cursor, VS Code, Cline, Windsurf, Codex, Roo Code, and more.

Q: Is there cloud sync? A: Yes, optional encrypted cloud sync is listed as a Pro feature in the README.

🙏

Source & Thanks

Source: https://github.com/milisp/mcp-linker > License: AGPL-3.0 > GitHub stars: 310 · forks: 27

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets

mcp2cli — Turn MCP Servers into CLI Tools, Zero Codegen

Convert any MCP server, OpenAPI spec, or GraphQL endpoint into a full CLI at runtime. Saves 96-99% of tokens wasted on tool schemas every turn.

MCP ConfigsCLI Tools
MCP Hub

ToolHive — Run & Manage MCP Servers with thv

Install, run, and manage MCP servers with the `thv` CLI (plus desktop/K8s options), with registry workflows and AI-client setup helpers.

SkillsCLI Tools
MCP Hub

OpenMCP Client — Universal CLI for MCP Servers

OpenMCP Client is a universal CLI to connect to MCP servers, list tools, and run calls from a terminal—useful for debugging and smoke tests.

CLI Tools
Script Depot

mcpc — Universal MCP CLI Client

A Swiss Army knife CLI for the Model Context Protocol: connect to MCP servers, manage sessions, list tools, and script tool calls via JSON output.

CLI Tools
MCP Hub
◈Home🔍Search👤Me