Does every editor support project-scoped MCP config?

Cursor, VS Code, and Claude Code all support project-scoped MCP config files committed to the repo. Windsurf does not — it only reads a single global config file at ~/.codeium/windsurf/mcp_config.json.

Can I commit API keys if the repo is private?

No. Private repos can become public and credentials in git history are difficult to fully remove. Always use environment variables or the VS Code inputs mechanism to keep keys out of the file.

How do I update a shared MCP server for the whole team?

Change the pinned version in the committed config file and push. Teammates get the update on their next git pull. Using @latest causes silent upgrades, which is why pinning a specific version is safer.

What if teammates use different editors?

Commit all the relevant files: .cursor/mcp.json, .vscode/mcp.json, and .mcp.json. Each editor ignores the others files, so there is no conflict.

How to Share MCP Servers with Your Team

Commit a project-scoped MCP config to share servers with your team: .cursor/mcp.json in Cursor (mcpServers key), .vscode/mcp.json in VS Code (servers key), .mcp.json in Claude Code (mcpServers key). Never commit API key values — use environment variables or the VS Code inputs feature instead. Windsurf has no project-scoped config; document servers in the README for Windsurf teams.

A project-scoped config file committed to the repo is all it takes to share MCP servers across a team. Here is the right file, the right key name, and the right way to handle secrets for Cursor, VS Code, and Claude Code.