MCP in code
Instrument the MCP stdio client
Page 6 adds signals that distinguish bad input from component failure in the MCP stdio client calling one local tool.
1Learn the idea
Read
Emit stage signals
Instrument the MCP stdio client calling one local tool so a run records enough structure to debug offline: counts, latency if relevant, pass/fail of discovery count, and a stable stage name. Redact secrets and raw credentials from every event.
Read
Emit and assert
const event={stage:'mcp-client', discovered:1, called:'echo', timeout:false};
console.log(JSON.stringify(event));
Expected evidence: mcp telemetry. Prefer JSON or structured text you can grep in CI over prose logs for mcp-in-code.
Read
Lock signals with a regression test
Turn one historical failure—especially calling a tool not in the discovered list—into a test that fails if the signal disappears for the MCP stdio client. Observability without a failing test is optional decoration; observability with a test is part of the mcp-in-code artifact.
Read
Lab notebook: signal schema
Draft a three-field event for the MCP stdio client: stage, ok, and one domain field derived from discovery count; successful call; timeout on hung server. Add fixture_id or docs_version when content can change. Explicitly list fields that must never appear (tokens, passwords, raw prompts) because auto-approving every discovered tool including filesystem writes is in scope for this lab.
Wire one assertion that fails if the MCP stdio client event is missing after a run. Observability that cannot fail a test will not survive contact with a busy mcp-in-code repository.
Read
Worked judgment
Imagine a teammate opens only your event stream after a bad deploy. Could they tell whether local stdio server exposing one read-only echo tool was wrong, whether calling a tool not in the discovered list, or hanging on stderr noise returned, or whether auto-approving every discovered tool including filesystem writes slipped through? If not, rename fields until those three stories are distinguishable.
Read
Why this stage matters for the MCP stdio client
At the testing and observability stage for mcp-in-code, the job is narrower than finishing a product demo. You are creating one progressive evidence piece about local stdio server exposing one read-only echo tool that later pages inherit without redefining success. Keep that fixture small enough to inspect by hand, keep outputs copy-pasteable as text, and refuse to narrate this baseline as if it were a production SLA: direct function call without MCP discovery.
For this page specifically, success looks like a structured event schema locked by a test while still centering the user decision to connect to a local MCP server, list tools, and invoke one allowlisted tool safely. If you cannot point to a file, command, or assertion that proves that for the MCP stdio client, stay on this page instead of advancing.
Glossary: tool · Glossary: structured output · Cheatsheet: production ops signals
Go deeper
Before you start
Why this matters
Write the single log line or metric event that would tell you whether a bad result came from input vs implementation for the MCP stdio client. If your line could not tell them apart, redesign it before coding.
In the wild
See how this idea shows up as a product and a company — then come back to the lesson. Skills transfer across vendors.
Related lessons
Check your understanding
Page assessment
Answer from memory. Completion is saved from this evidence, not from opening the next page.
All responses are required.