Skip to content

Docs: avoid dotnet run build output on MCP stdio#136

Open
zdeneksrejber wants to merge 3 commits into
TALXIS:masterfrom
zdeneksrejber:fix/mcp-readme-safe-stdio-startup
Open

Docs: avoid dotnet run build output on MCP stdio#136
zdeneksrejber wants to merge 3 commits into
TALXIS:masterfrom
zdeneksrejber:fix/mcp-readme-safe-stdio-startup

Conversation

@zdeneksrejber
Copy link
Copy Markdown
Member

Disclaimer: I don't know if this should be merged, but I have troubles running the MCP locally, these are the steps that helped me actually run it

Summary

  • update src/TALXIS.CLI.MCP/README.md to avoid plain dotnet run for stdio MCP sessions
  • document the safe local workflow: build first, then run with --no-build
  • update Inspector and command-line debugging examples to keep stdout reserved for MCP traffic

Why

dotnet run performs a build before launching the MCP server. Build warnings can be emitted before the stdio transport is ready, and MCP clients may try to parse those warning lines as protocol messages. The updated guidance separates the build step from the stdio session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant