feat: MCP server support — load from Cursor config, pass to Agent SDK

[dimakis]

Summary

• Reads MCP server configs from ~/.cursor/mcp.json (existing Cursor config)
• Optionally reads from MCP_CONFIG_PATH env var for Mitzo-specific overrides
• Converts Cursor-format stdio entries to Agent SDK mcpServers option
• Passes them into query() — Claude sessions get all configured MCP tools (Jira, GitLab, etc.)
• GET /api/config now includes mcpServers array (names only, no secrets)
• Disabled servers and non-stdio types are excluded

How it works

On server startup, loadMcpServers() reads ~/.cursor/mcp.json:

{
  "mcpServers": {
    "atlassian": {
      "command": "/Users/dsaridak/.local/bin/uvx",
      "args": ["mcp-atlassian", "--jira-url", "https://redhat.atlassian.net", ...]
    }
  }
}

This gets passed to the Agent SDK as:

query({ options: { mcpServers: { atlassian: { command: "...", args: [...] } } } })

Claude in Mitzo sessions can now use jira_search, jira_get_issue, jira_create_issue, etc.

Test plan

• 81 tests passing (11 new for mcp-config)
• tsc --noEmit clean
• ESLint --quiet clean
• Manual: start a Mitzo chat, ask Claude to search Jira — should use MCP tools

Made with Cursor