Specification feature · interfaces
MCP loggingMCP 2026-07-28
Receive structured log messages emitted by an MCP server.
Terminology basis: MCP 2026-07-28. MCP 2026-07-28
MCP logging: 1 supported, 0 partial, 0 unsupported, 30 unreviewed across 31 cataloged products.
Current evidence by product
Can my agent use MCP logging?
Read across for the answer. 1 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.
Web
9 productsDesktop
13 productsCLI
9 productsDefinition and scope
What this capability means
Receive structured log messages emitted by an MCP server.
This row remains unknown for a product until exact, dated evidence covers this capability rather than MCP generally.
Traceable compatibility
Assertion ledger
Documentation evidence only. No runtime conformance test is implied.
- Target
- VS Code source commit a39698f7 · dated-documentation
- Environment
- local-default
- Observed
- 2026-08-28
- protocol-revisionthe handler implements structured notifications/message logging; MCP 2026-07-28 retains this notification with revised per-request log-level semantics
- Microsoft VS Code — MCP server connection implementationdocumented · reviewed 2026-08-28
- 1. VS Code source dispatches MCP notifications/message payloads to its structured MCP log translator.
No sourced issues are attached to this row.
- Model Context Protocol specification spec
- Microsoft VS Code — MCP server connection implementation documented · Microsoft · reviewed 2026-08-28
Found a wrong or incomplete result?
Name the exact product, describe what happened, add the date, and link public evidence when available. A community report starts a review. It does not change the support state by itself.