Feature Request: Default MCP Server Installation Scope

Feature Request

Summary

Add a configuration option to set a default installation scope for new MCP servers (user/project/local).

Current Behavior

When adding MCP servers, users must manually specify the scope each time. There is no way to configure a default preference.

Proposed Behavior

Allow users to set a default scope preference in their settings, for example:

{
  "mcp": {
    "defaultScope": "user"
  }
}

This would automatically use the specified scope when installing new MCP servers via the /plugin command or other installation methods, while still allowing manual override when needed.

Use Case

Users who consistently prefer a specific scope (e.g., always wanting servers at user scope for cross-project availability) currently need to manually select this option every time they add a new MCP server.

Suggested Implementation

• Add a mcp.defaultScope setting in user/project settings
• Valid values: "user", "project", "local"
• Fall back to current behavior if not set
• Allow override during manual installation

This would improve the user experience for those with consistent scope preferences while maintaining flexibility for users who vary their choices.