Option D is directly supported by both the supplied examination material and Claude Code's MCP documentation. The examination source selects STDIO for this local-process scenario.

Claude Code's official MCP guidance distinguishes remote HTTP servers from local STDIO servers. Anthropic states that STDIO servers run as local processes and communicate through standard input and standard output. They are particularly suitable for local tools requiring direct machine access or for custom scripts. Claude Code can launch the process itself and communicate with it without creating, exposing, securing, or maintaining a network listener.

HTTP is appropriate when the MCP server exists as a separately reachable network service, especially for cloud-hosted or shared services. That requirement is absent here: the server is being invoked locally from a Claude Code session.

A creates duplicate transport infrastructure without a stated availability requirement. B incorrectly assumes one transport is universally superior regardless of deployment topology. C describes HTTP polling rather than the normal MCP transport relationship and introduces unnecessary request overhead.

Therefore, local execution strongly favors STDIO; remote/shared deployment generally favors HTTP.

Relevant Claude Developer topics: MCP architecture, STDIO transport, HTTP transport, Claude Code integrations, local process communication, and deployment topology.

===============