[FEATURE] /init should ask which MCPs are needed for that project and create a .mcp.json

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

It's very useful to specify which MCPs should be enabled for each project users are working, as having unrelated MCPs enabled takes up context space.

Currently to do that users need to manually create a configuration file for each of their projects, which is a good solution already, but could be automated.

Proposed Solution

When running the /init command, claude could ask the user which currently configured MCPs are relevant to the project and create the .mcp.json on its own.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_