What is the primary problem that Model Context Protocol (MCP) solves?	The maintenance burden of custom integrations when a third-party service changes its API.
How does MCP shift the maintenance responsibility for integrations?	It shifts the maintenance to the service provider (e.g., Asana, Slack), who publishes and updates the MCP server.
In the context of Claude's capabilities, what is the difference between "Tools" and "Skills"?	Tools connect to proprietary systems (user-owned code/APIs); Skills teach procedures or instructions (user-defined processes).
What is the specific role of MCP in the "Tools vs. Skills vs. MCP" framework?	MCP connects Claude to third-party services where the service provider maintains the integration.
What two key elements must be included in the API request to connect to an MCP server?	The `mcpservers` key (to declare the connection details) and the `tools` key (to grant access).
When connecting to an MCP server, how does Claude discover available tools?	Claude introspects the server, automatically getting the list of tools and their schemas without the user writing any tool schema.
What is the recommended method for limiting Claude's access to only specific tools on a large MCP server?	Set the `default_config` to `{"enabled": False}` and then explicitly enable only desired tools within the `configs` block.
What is the current status of the MCP connector?	It is in beta, requiring the inclusion of a beta header in the request.