Why do I need to sync MCP config across multiple tools?

Claude Code, Cursor, Windsurf, VS Code, and Claude Desktop each have their own MCP config files. The single goal of syncing: keep the server list identical across tools so you don't hit “works here, broken there”. The chapter's three rules: pick one main config and copy from it; server names must be byte-identical; restart every tool after changes — none of them hot-reload.

Where is each tool's MCP config file located?

macOS quick reference: Claude Desktop = `~/Library/Application Support/Claude/claude_desktop_config.json`; Cursor = `~/.cursor/mcp.json`; Windsurf = `~/.codeium/windsurf/mcp_config.json`; Claude Code = `~/.claude.json` (not MCP-only); VS Code = `~/Library/Application Support/Code/User/settings.json`. Claude Code CLI does not currently support MCP server config via `.claude.json` — use the `claude mcp add` command.

How does VS Code's MCP config differ from Cursor's?

Different structure. Claude Desktop and Cursor use a top-level `mcpServers` field; VS Code requires `mcp.servers` nested under `mcp`. The chapter's troubleshooting calls this out: “VS Code can't see MCP” almost always means you wrote `mcpServers` — change it to `mcp.servers` and it works.

How do I check whether two tools' MCP configs match in one command?

The chapter's minimal compare script: sort-export with `jq -S`, then diff. For Cursor vs Claude Desktop: `jq -S '.mcpServers // {}' ~/.cursor/mcp.json > /tmp/cursor-mcp.json`, do the same for claude_desktop_config.json, then `diff -u /tmp/cursor-mcp.json /tmp/claude-mcp.json`. The `-S` flag sorts keys so diff isn't confused by field order.

How should I handle API keys in MCP config safely?

Three security rules: (1) prefer environment variables for API keys — never hardcode in JSON; (2) `chmod 600` the config file so only you can read it; (3) never commit configs with keys to git. Put keys in `~/.zshrc` via `export OPENAI_API_KEY=...` and reference them from the MCP env field — far safer than inline plaintext.

MCP Config Sync - Vibe Coding

学AI来匠人

📖

Vibe Coding

38 chapters

·Introduction

基础篇6

01
Vibe Coding 是什么
5分钟
02
安装 Cursor 与环境准备
10分钟
03
写出第一个 Prompt
10分钟
04
Vibe Coding 思维模型
8分钟
05
高质量 Prompt 模板
12分钟
06
理解与校验 AI 的回复
10分钟

进阶篇18

07
🔒用 AI 做 Debug
20分钟
08
🔒与 AI 结对编程
18分钟
09
🔒多文件协作与项目级修改
25分钟
10
🔒交付一个小功能的全流程
30分钟
11
🔒用 AI 做测试与质量保障
20分钟
12
性能与成本优化
18分钟
13
安全与隐私最佳实践
15分钟
14
🔒团队协作与 PR 流程
18分钟
15
工具与模型最新动态
12分钟
16
🔒AI Agents 与工具调用
25分钟
17
🔒前后端协同与 API 生成
25分钟
18
🔒数据与知识库协作
22分钟
19
持续改进与自动化
18分钟
20
🔒AI 辅助重构与架构演进
22分钟
21
AI 辅助 UX 文案与交互
15分钟
22
🔒可观测性与 Guardrails
18分钟
23
脚手架与自动化交付
15分钟
24
🔒实战：Todo App
45分钟

工具篇13

25
🔒MCP 服务器配置
20分钟
26
🔒MCP 配置同步
15分钟
27
Cursor Rules 编写指南
15分钟
28
Git Commit 规范与 Emoji
10分钟
29
五个为什么分析法
8分钟
30
Mermaid 图表生成
12分钟
31
任务实施方法论
10分钟
32
Claude Code Skills 进阶
15分钟
33
Claude Code + GLM 4.6 配置
15分钟
34
Claude Code 自定义命令
12分钟
35
Claude Code 子代理配置
15分钟
36
Claude Code 全面拆解
25分钟
37
Claude Skill Codebook 简明教程
12分钟

实战篇1

38
Vibe Coding 全流程 SOP
15分钟

Resources

🗺️ Learning Roadmap
📚 Wiki Docs
📋 Cheat Sheets

Home/Learn/Vibe Coding/MCP Config Sync

🎯Learn More Efficiently

Keep your learning uninterrupted

✏️
Study Notes
Take notes while learning, synced to cloud
📈
Progress Tracking
Auto-save, resume anytime
🏅
Completion Certificate
Shareable learning achievement
💬
Community Q&A
Connect with 2000+ learners

Sign Up Free→Already have an account? Sign in

👥2,847 learners active

AI学习面试课程学习中心