[DOCS] Contradictory definitions of strictMcpConfig between CLI and SDK docs
Resolved 💬 2 comments Opened Jan 25, 2026 by coygeek Closed Feb 27, 2026
Documentation Type
unclear/confusing documentation
Documentation Location
https://platform.claude.com/docs/en/agent-sdk/typescript and https://code.claude.com/docs/en/cli-reference
Section/Topic
strictMcpConfig option descriptions in both CLI reference and TypeScript SDK reference
Current Documentation
CLI Reference:
Only use MCP servers from --mcp-config, ignoring all other MCP configurations
TypeScript SDK:
Enforce strict MCP validation
What's Wrong or Missing?
The two descriptions describe fundamentally different behaviors:
- CLI description describes a loading behavior: only load MCP servers from the specified config, ignore system/user-level configs
- SDK description describes a validation behavior: enforce strict validation on MCP configurations
These are not the same thing. A developer reading the SDK docs would expect schema/format validation, while the actual behavior (per CLI docs) is about config file precedence.
Suggested Improvement
Align the SDK description with the CLI behavior (assuming CLI is the source of truth):
Before (SDK):
Enforce strict MCP validation
After (SDK):
Only use MCP servers from the specified config, ignoring system and user-level MCP configurations
Impact
Medium - Makes feature difficult to understand
Additional Context
- None
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗