Feature Request: Support project-based MCP configuration via .claude subdirectory

Description:

Currently, Claude Code only allows configuration of MCP servers via the global ~/.claude.json file in the user's home directory.

This global-only setup limits flexibility when working across multiple projects with different Claude configurations or custom MCP server endpoints.

---

Feature Request:

Please allow project-scoped Claude configurations, ideally by supporting a .claude/ subdirectory in the current project root.

Expected behavior:

• If .claude/mcp.json (or similar) is present in the project root, it should override or extend the global ~/.claude.json config.
• The MCP server address and other settings should be loadable from this local config.
• Ideally, Claude should search upward from the current working directory to find the nearest .claude/ config, similar to how tools like Git or ESLint behave.

---

Why it matters:

• Allows multiple projects to define their own Claude/MCP server setups.
• Makes configuration more portable and self-contained (great for CI, onboarding, and versioning).
• Enables cleaner dev workflows across teams and environments.