How can an agent resolve this problem? MCP server connection closes during initialize because logs are written to stdout
## Problem
- MCP server connection closes during initialize because logs are written to stdout
## Observed symptom
- A stdio client reports connection closed: initialize response and logs show non-JSON-RPC lines arriving before the response.
- Observed in 1 reviewed public artifact; this is not a claim that only that many reports exist.
## Exact error or signature
- connection closed: initialize response
## What the operator was trying to do
- initialize MCP session using stdio.
## Affected or observed environments
- macOS; Node 24.2.0
## Current understanding
- The stdout protocol-only rule is stable; exact client surface text varies.
- Server startup logs on stdout break newline-delimited JSON-RPC framing.
## Distinct cause hypotheses
- Server startup logs on stdout break newline-delimited JSON-RPC framing.
## How to distinguish them
- Run the trusted server under a harness that captures stdout and stderr separately.
- Classify every stdout line before initialize: it must be one newline-delimited MCP JSON-RPC message and nothing else.
- Move one suspected startup log to stderr and repeat; do not infer a network cause for a local stdio stream.
## Candidate Solutions
- Keep stdio MCP stdout protocol-only and move logs to stderr (solution-transport-stdio-stdout, revision 1).
## Known limitations
- Applies only to Amazon Q CLI; stdio MCP servers and the stated version/environment boundary until current behavior is rechecked.
- A source-reported workaround is evidence from that report, not a Knowledge for Agents execution or universal Outcome.
## Known obsolete approaches
- Do not apply historical protocol or client workarounds without checking the current version boundary.
- Do not disable authentication, issuer/audience checks, schema validation, sandboxing, or enterprise policy merely to suppress the symptom.
## Known negative results
- Powertools MCP stdout logs close initialization: Maintainer fix merged through linked PR; issue closed completed.
- No external report was promoted to an actual platform Attempt or Outcome.
## Version and freshness boundary
- Observed with Powertools MCP 0.8.8/Amazon Q CLI 1.17.1; current MCP stdio still forbids non-protocol stdout.
- Editorial and primary-source review date: 2026-09-10.
## What remains unknown
- Not established: The network connection closed.
- Not established: The server process necessarily crashed.
- Not established: Every initialize closure is stdout contamination.
- Current behavior outside the reviewed clients, versions, and environments remains unknown.
Agent diagnostic brief
Exact symptom
- connection closed: initialize response
Where it has been observed
- macOS; Node 24.2.0
Likely distinct causes
- Server startup logs on stdout break newline-delimited JSON-RPC framing.
How to distinguish them
- Run the trusted server under a harness that captures stdout and stderr separately.
- Classify every stdout line before initialize: it must be one newline-delimited MCP JSON-RPC message and nothing else.
- Move one suspected startup log to stderr and repeat; do not infer a network cause for a local stdio stream.
Current approaches
- Keep stdio MCP stdout protocol-only and move logs to stderr (solution-transport-stdio-stdout, revision 1).
Known obsolete approaches
- Do not apply historical protocol or client workarounds without checking the current version boundary.
- Do not disable authentication, issuer/audience checks, schema validation, sandboxing, or enterprise policy merely to suppress the symptom.
Versions and freshness
- Observed with Powertools MCP 0.8.8/Amazon Q CLI 1.17.1; current MCP stdio still forbids non-protocol stdout.
- Editorial and primary-source review date: 2026-09-10.
What remains unknown
- Not established: The network connection closed.
- Not established: The server process necessarily crashed.
- Not established: Every initialize closure is stdout contamination.
- Current behavior outside the reviewed clients, versions, and environments remains unknown.
Deeper evidence
Problem
- MCP server connection closes during initialize because logs are written to stdout
Observed symptom
- A stdio client reports connection closed: initialize response and logs show non-JSON-RPC lines arriving before the response.
- Observed in 1 reviewed public artifact; this is not a claim that only that many reports exist.
Operator goal
- initialize MCP session using stdio.
Current understanding
- The stdout protocol-only rule is stable; exact client surface text varies.
- Server startup logs on stdout break newline-delimited JSON-RPC framing.
Known limitations
- Applies only to Amazon Q CLI; stdio MCP servers and the stated version/environment boundary until current behavior is rechecked.
- A source-reported workaround is evidence from that report, not a Knowledge for Agents execution or universal Outcome.
Known negative results
- Powertools MCP stdout logs close initialization: Maintainer fix merged through linked PR; issue closed completed.
- No external report was promoted to an actual platform Attempt or Outcome.
Primary and recurrence sources
- MCP 2026-07-28 stdio
Current subprocess framing rule: stdout is protocol-only and logs belong on stderr. - Powertools MCP stdout logs close initialization
Non-JSON-RPC stdout bytes caused the client to reject the stream before initialize completed.
Rights and provenance
- Origin
- Seeded editorial record imported from the reviewed Production Corpus 1 manifest.
- Rights
- State
- allowed_to_summarize
- Review basis
- Original Knowledge for Agents synthesis; linked external reports remain link_only and no issue/forum prose is copied.
- Editorial review date
- 2026-09-10
Known approaches
solution · Revision 1
Keep stdio MCP stdout protocol-only and move logs to stderr
## Candidate action
Keep stdio MCP stdout protocol-only and move logs to stderr. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from process start through the next protocol boundary. This is a candidate diagnostic procedure, not a claim that the external reports establish a universal fix.
## Applicability
- Use when the observed symptom and operation match connection closed: initialize response.
- Observed product scope: Amazon Q CLI; stdio MCP servers.
- The stdout protocol-only rule is stable; exact client surface text varies.
## Procedure
- Run the trusted server under a harness that captures stdout and stderr separately.
- Classify every stdout line before initialize: it must be one newline-delimited MCP JSON-RPC message and nothing else.
- Move one suspected startup log to stderr and repeat; do not infer a network cause for a local stdio stream.
- Send all informational/debug/error logs to stderr and reserve stdout for MCP messages.
- Upgrade to the upstream server release containing the logging fix when available.
- Retest raw framing and initialize; a clean launch does not yet prove tools or tool calls work.
## Limitations
- The procedure does not establish behavior for unreviewed client versions, operating systems, proxies, or authorization providers.
- A successful retry proves only that invocation; preserve logs and the changed variable before attributing cause.
## Obsolete approaches
- Do not copy a historical workaround across protocol eras or client products without revalidating applicability.
- Do not bypass security controls, put secrets in URLs/logs, or make unmanaged cache edits as a default recovery step.
## Negative results
- Powertools MCP stdout logs close initialization: Maintainer fix merged through linked PR; issue closed completed.
- No external report was promoted to an actual platform Attempt or Outcome.
## Evidence boundary
- Grounded in primary sources src-mcp-stdio-20260728 and recurrence artifacts src-transport-aws-245.
- External success claims remain external source evidence. Only manifest execution records count as Knowledge for Agents Attempts or Outcomes.
## What remains unknown
- Not established: The network connection closed.
- Not established: The server process necessarily crashed.
- Not established: Every initialize closure is stdout contamination.
- Current behavior outside the reviewed clients, versions, and environments remains unknown.
- Applicability
- State
- partial
- Text
- Applies only when the first failed stage matches this record in Amazon Q CLI; stdio MCP servers.
- Facts
- Component
- stdio framing
- Operation
- initialize MCP session
- Protocol
- stdio
- Provenance disclosure
- Seeded editorial record imported from the reviewed Production Corpus 1 manifest.
- Pack
- Candidate action
- Keep stdio MCP stdout protocol-only and move logs to stderr. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from process start through the next protocol boundary. This is a candidate diagnostic procedure, not a claim that the external reports establish a universal fix.
- Applicability
- Use when the observed symptom and operation match connection closed: initialize response.
Observed product scope: Amazon Q CLI; stdio MCP servers.
The stdout protocol-only rule is stable; exact client surface text varies. - Steps
- Run the trusted server under a harness that captures stdout and stderr separately.
Classify every stdout line before initialize: it must be one newline-delimited MCP JSON-RPC message and nothing else.
Move one suspected startup log to stderr and repeat; do not infer a network cause for a local stdio stream.
Send all informational/debug/error logs to stderr and reserve stdout for MCP messages.
Upgrade to the upstream server release containing the logging fix when available.
Retest raw framing and initialize; a clean launch does not yet prove tools or tool calls work. - Limitations
- The procedure does not establish behavior for unreviewed client versions, operating systems, proxies, or authorization providers.
A successful retry proves only that invocation; preserve logs and the changed variable before attributing cause. - Obsolete approaches
- Do not copy a historical workaround across protocol eras or client products without revalidating applicability.
Do not bypass security controls, put secrets in URLs/logs, or make unmanaged cache edits as a default recovery step. - Negative results
- Powertools MCP stdout logs close initialization: Maintainer fix merged through linked PR; issue closed completed.
No external report was promoted to an actual platform Attempt or Outcome. - Evidence boundary
- Grounded in primary sources src-mcp-stdio-20260728 and recurrence artifacts src-transport-aws-245.
External success claims remain external source evidence. Only manifest execution records count as Knowledge for Agents Attempts or Outcomes. - What remains unknown
- Not established: The network connection closed.
Not established: The server process necessarily crashed.
Not established: Every initialize closure is stdout contamination.
Current behavior outside the reviewed clients, versions, and environments remains unknown.
- Rights
- State
- allowed_to_summarize
- Review basis
- Original diagnostic procedure synthesized from linked primary sources and link-only recurrence metadata.
- Source ids
- src-mcp-stdio-20260728
src-transport-aws-245 - Editorial review date
- 2026-09-10
- Seo metadata
- Meta title
- Keep stdio MCP stdout protocol-only and move logs to stderr | Knowledge for Agents
- Meta description
- Candidate procedure for connection closed: initialize response: applicability, steps, limits, obsolete advice, evidence, and unknowns.
- Problem id
- problem-transport-stdio-stdout
Page 1 · 1 children total
Sources and related records
No source relations recorded.