[ENHANCEMENT] Include MCP settings in the exported settings

[fancl20]

Problem (one or two sentences)

Currently the exported settings don't contain content from mcp_settings.json, causing autoImport not able to configure MCP.

Context (who is affected and when)

Version: 3.39.1 (e39c241)

Desired behavior (conceptual, not technical)

Include mcp configs in exported settings

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Problem

Currently, when users export their Roo Code settings, the MCP server configurations from mcp_settings.json are not included. This prevents autoImport from configuring MCP servers and makes it difficult to share or backup MCP configurations.

Proposed Solution

1. Modify exportSettings function in src/core/config/importExport.ts

Add an optional mcpHub parameter to read and include MCP settings in the exported JSON:

type ExportOptions = {
  providerSettingsManager: ProviderSettingsManager
  contextProxy: ContextProxy
  mcpHub?: McpHub  // Add optional McpHub parameter
}

The export will:

• Read the MCP settings file via mcpHub.getMcpSettingsFilePath()
• Include mcpSettings in the exported JSON alongside providerProfiles and globalSettings

2. Modify importSettingsFromPath function

Update the import schema to accept mcpSettings and write them to the MCP settings file:

const schema = z.object({
  providerProfiles: providerProfilesSchema,
  globalSettings: globalSettingsSchema.optional(),
  mcpSettings: z.object({
    mcpServers: z.record(z.any())
  }).optional(),  // Add optional mcpSettings schema
})

The import will:

• Parse mcpSettings from the imported JSON
• Merge with existing MCP settings (preserving user's existing servers while adding new ones)
• Write the merged settings to the MCP settings file

3. Update webviewMessageHandler.ts

Pass the mcpHub to the exportSettings call:

case "exportSettings":
  await exportSettings({
    providerSettingsManager: provider.providerSettingsManager,
    contextProxy: provider.contextProxy,
    mcpHub: provider.getMcpHub(),  // Add mcpHub
  })

4. Add types for MCP settings export/import

Create a schema for MCP settings validation to ensure proper structure during import.

Exported JSON Structure (after implementation)

{
  "providerProfiles": { ... },
  "globalSettings": { ... },
  "mcpSettings": {
    "mcpServers": {
      "server-name": {
        "command": "...",
        "args": [...],
        ...
      }
    }
  }
}

Benefits

• Users can export/import complete configurations including MCP servers
• autoImport functionality will be able to configure MCP servers
• Settings portability between machines/installations is improved
• Backward compatible - existing exports without mcpSettings will still import correctly

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[hannesrudolph]

@fancl20 are you expecting the export to export and import just the MCPs configured globally?

[fancl20]

yes that's my expectation. I'm also fine with having a different way to import/export the global MCPs. or should I just copy the config file directly? In that case I would prefer having a setting for the path instead for ease of provision.