claude-code - 💡(How to fix) Fix [Feature Request] Suppress verbose output from /context command with large MCP tool definitions [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49547Fetched 2026-04-17 08:38:03
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1
RAW_BUFFERClick to expand / collapse

Bug Description

When using /context with any significant MCP tools on your account, the output gets massive. We should suppress that output to make that slash command easier to read, and expose the list of mcp toolings if the user requests it, in another fashion.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.92
  • Feedback ID: 72ff231b-f309-44cf-b95b-b6517fb6a477

extent analysis

TL;DR

Modify the /context command to suppress excessive output by default and provide an option to display the list of MCP toolings upon user request.

Guidance

  • Review the current implementation of the /context command to identify the source of the excessive output.
  • Consider adding a flag or parameter to the /context command that allows users to opt-in to viewing the list of MCP toolings, rather than displaying it by default.
  • Investigate potential filtering or pagination mechanisms to limit the amount of output displayed to the user.
  • Evaluate the feasibility of displaying the list of MCP toolings in a separate output or interface, such as a dropdown menu or a secondary command.

Notes

The ideal solution will depend on the specific requirements and constraints of the MCP tools and the /context command, which are not fully specified in the issue.

Recommendation

Apply workaround: Modify the /context command to suppress excessive output by default and provide an option to display the list of MCP toolings upon user request, as this approach addresses the user experience issue without requiring significant changes to the underlying system.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Feature Request] Suppress verbose output from /context command with large MCP tool definitions [1 comments, 2 participants]