Project `.cursor/mcp.json` is becoming team policy

Teams are committing shared MCP config to git — the new answer to “which agent tools does this repo allow?” Secrets stay personal; approved servers ship with the clone.

Source: Influzer.ai

Cursor MCP is moving from solo hacks to shared repo policy. Teams commit .cursor/mcp.json — versioned, PR-reviewed — and treat it like package.json for agent tools.

Three-tier model:

Tier 1 (in git): GitHub read, Context7, Influzer Discovery — no secrets
Tier 2 (documented local): staging DB creds in env, not in JSON
Tier 3 (banned): random npx, prod write tools, duplicate scrapers

Why it matters: when agents can call external systems, “which connectors does this codebase ship?” is a security and onboarding question — not a personal preference.

Setup basics: First MCP servers in Cursor. Full playbook: .cursor/mcp.json is becoming team policy.