[FEATURE] Collapse MCP tools by server in /context view
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
When using MCP servers that expose many tools (e.g., Linear with 30+ tools), the /context view lists every tool individually. Since MCP tools are listed at the bottom of the output and the command leaves the cursor there, you have to scroll up past 30+ tool names to see the important parts — token usage, memory files, and skills.
These are deferred tools that don't consume context tokens until invoked, so the expanded list provides little actionable information while pushing the useful content off-screen.
Proposed Solution
Collapse MCP tools by server name in the /context view.
Current behavior:
MCP tools · /mcp (loaded on-demand)
Available
└ mcp__linear-server__get_attachment
└ mcp__linear-server__create_attachment
└ mcp__linear-server__delete_attachment
└ mcp__linear-server__list_comments
... (30+ more lines)
Proposed behavior:
MCP tools · /mcp (loaded on-demand)
Available
└ linear-server (32 tools)
└ ide (2 tools)
Or show frequently used tools expanded with the rest collapsed:
└ linear-server (32 tools)
└ get_issue
└ list_issues
└ save_issue
└ ... 29 more
Alternative Solutions
None.
Priority
Low - Nice to have
Feature Category
Interactive mode (TUI)
Use Case Example
- I run
/contextto check my session state (token usage, memory files, skills) - The command output ends at the bottom with the MCP tool list, so the cursor lands there
- I have to scroll up past 30+ Linear tool names to see the important context info at the top (token usage breakdown, memory files, skills)
- With this feature, the MCP section would be 2-3 lines instead of 30+, and the useful information would still be visible without scrolling
Additional Context
This becomes more relevant as users connect multiple MCP servers. With 2-3 servers each exposing 10-30 tools, the /context view could easily be 90% MCP tool names.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗