claude-code - 💡(How to fix) Fix [FEATURE] Add per-MCP-server log files [1 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#45529Fetched 2026-04-09 08:03:16
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

I'm trying to write a stdin mcp server and finding the complete lack of errors or warnings from Claude Code a hindrance. I wish I had per-server logs of the interactions so I could better debug my server.

Proposed Solution

I'd like an --mcp-debug flag or something similar to log interactions, warnings, and errors, ideally saved somewhere convenient with per-server files.

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

Duplicate of auto-closed and auto-locked https://github.com/anthropics/claude-code/issues/29035

extent analysis

TL;DR

Implementing an --mcp-debug flag to log interactions, warnings, and errors for the stdin mcp server could provide the necessary debugging information.

Guidance

  • Consider adding a logging mechanism that captures interactions, warnings, and errors for each server instance, potentially saving these logs to per-server files for easier debugging.
  • Evaluate the feasibility of introducing a command-line flag, such as --mcp-debug, to enable or disable this logging feature based on user needs.
  • Review existing logging configurations or frameworks within the Claude Code project to determine the best approach for integrating this new logging functionality.
  • Assess the potential impact of this feature on performance and privacy, ensuring that the logging does not introduce significant overhead or expose sensitive information.

Notes

The implementation details of the --mcp-debug flag and the logging mechanism will depend on the specific requirements and constraints of the Claude Code project, including the programming language, existing architecture, and user expectations.

Recommendation

Apply workaround: Introduce a custom logging solution or modify the existing logging configuration to capture the necessary information for debugging the stdin mcp server, as implementing a new flag like --mcp-debug might require significant changes or updates to the project.

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