Claude Certified Architect – Foundations Practice Question 88: MCP Connector Messages API
Claude Certified Architect, Foundations · Test 9 · question 8 of 10
A backend team calls the Messages API directly and wants Claude to use tools exposed by a vendor's remote MCP server, which is reachable over HTTPS and supports OAuth. The team does not want to write or maintain an MCP client. Which approach fits? (The MCP connector is a beta feature.)
Show answer and explanation
Answer:
B is correct. The MCP connector (beta, enabled with a beta header) lets the Messages API connect to remote MCP servers directly, with no separate MCP client. The request lists the server's URL and authentication in mcp_servers, and an mcp_toolset entry in tools enables its tools (optionally with allowlists or denylists). The server must be publicly exposed over HTTP (Streamable HTTP or SSE).
A is wrong because local stdio servers cannot be connected directly through the connector. C is wrong because it works but is exactly the client plumbing the team wants to avoid. D is wrong because createSdkMcpServer belongs to the Agent SDK for in-process tools; it is not a Messages API request field.
Reference: MCP connector - Claude API Docs