Skip to content

Prevent server panels from jumping when one of them becomes connected #1956

Closed

Description

@xenon615

Which client?

Web

The problem

Say i have some configured servers . At my box they suited by three in line . When one of them got connected, the right side panel appears thereby reducing the server panel and causing the server tiles to move to adapt to the changing space.
This behavior is wholly understandable but little annoying , especially if connected server is last in the row

Solution you have in mind (optional)

the first thing that comes to mind is showing side panel regardless is there connected servers or not

Alternatives or workarounds you have tried

No response

Already built it locally?

No response

Before you submit

  • I searched existing issues and this is not a duplicate.
  • This is a request for the Inspector itself, not for the MCP specification or an SDK.

Activity

  1. added this to the v2.3.0 milestone on Aug 10, 2026
  2. cliffhall commented on Aug 10, 2026

    @cliffhall
    Member

    The behavior is intentional. As you describe, the side panel being displayed after connection can scroll the connected server offscreen when the server list width shrinks. If it is offscreen, the inspector scrolls the connected server into view. It was more annoying when the connected server was not in view and you had to scroll to it manually if you wanted to view its connection info.

    scroll-to-connected-server.mov

    You might be able to avoid the scrolling by simply keeping your server list collapsed.

    servers-collapsed.mov
  3. xenon615 commented on Aug 11, 2026

    @xenon615
    Author

    I have a feeling I wasn't understood very well, if only because I didn't mention scrolling at all.
    In fact, the problem I described isn't all that serious, although a constantly visible sidebar could solve it (even if it were empty when no one was connected.
    On the other hand, no one will die if everything stays as is, so the issue can be closed.

  4. removed this from the v2.3.0 milestone on Aug 17, 2026
  5. self-assigned this
    on Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature requestv2Issues and PRs for v2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions