Skip to content

Support for Multiple Open Projects #16

@noreff

Description

@noreff

When working with multiple JetBrains IDE projects simultaneously, it's currently difficult to determine which port corresponds to which open project. The current implementation scans ports 63342-63352 and uses the first working port it finds, or allows specifying a single port via the IDE_PORT environment variable.

However, this approach makes it challenging to:

  1. Know which specific project a Claude is currently connected to
  2. Switch between different open projects intentionally
  3. Maintain consistent connections to specific projects

Feature Request

Add support for working with multiple open projects simultaneously, with clear indicators of which port corresponds to which project.

Suggested Solution

  1. Add a project identifier in the JetBrains UI that shows:

    • The port number the MCP server is using for that project
    • A visual indicator showing whether Claude is currently connected to this project
  2. Enhance the configuration to allow naming of project-port mappings:

"mcpServers": {
  "jetbrains": {
    "command": "npx",
    "args": ["-y", "@jetbrains/mcp-proxy"],
    "projects": {
      "projectA": {
        "port": 63342,
        "name": "Frontend App"
      },
      "projectB": {
        "port": 63343,
        "name": "Backend API"
      }
    },
    "defaultProject": "projectA"
  }
}
  1. Add a command in Claude to list available projects and switch between them:
    • /jetbrains list - Show all available projects
    • /jetbrains connect projectA - Connect to a specific project

Benefits

  • Clear visibility into which project Claude is analyzing and modifying
  • Ability to work on multiple projects without confusion
  • Improved developer experience when managing complex workspaces

This would require:

  1. Modifications to the MCP Server plugin to expose project metadata
  2. Updates to the proxy server to handle project switching
  3. UI enhancements in JetBrains IDEs to show the connection status

Has anyone else encountered this issue when working with multiple projects? How are you currently handling this workflow?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions