Introducing MCP

Model Context Protocol (MCP) Study Notes

**I. Core Concepts of MCP**

• Definition: MCP is a communication layer designed to provide Claude with necessary context and tools without requiring developers to write extensive, tedious code.
• Architecture: MCP consists of two major elements: the Client and the Server.
• Server Components: The MCP Server typically contains internal components named tools, resources, and prompts.
• The Problem Solved: Traditionally, developers must write, test, and maintain all the schemas and functions for complex integrations (e. g. , building a full GitHub chatbot). MCP shifts this burden.
• MCP Server Function: An MCP Server acts as an interface to an outside service. It wraps the functionality of that service (e. g. , GitHub) and presents it as a set of tools.
• Tool Definition: A tool is a mechanism that exposes functionality related to an outside service.

**II. Key Benefits and Comparisons**

• Developer Benefit: By using an MCP server, developers do not have to author all the tool schemas and functions themselves.
• **MCP vs. Direct API Call:**
• Direct API Call: Requires the developer to author the tool schema and the function implementation.
• MCP: Saves time by providing a pre-built layer that handles the schema and function implementation.
• **MCP vs. Tool Use:**
• These concepts are complementary, not identical.
• Tool Use: Refers to the action of using a tool.
• MCP: Refers to who is doing the work—it is the mechanism that provides the pre-built tool function and schema.

**III. Implementation Details**

• Authorship: Anyone can create an MCP server implementation.
• Service Providers: Service providers (e. g. , AWS) often release official MCP server implementations containing a wide variety of tools.

Takeaways

• MCP is a communication layer designed to provide Claude with necessary context and tools without requiring developers to write extensive code.
• The MCP Server acts as an interface to an outside service, wrapping its functionality into defined tools, resources, and prompts.
• It significantly reduces developer burden by providing pre-built tool schemas and function implementations, unlike direct API calls.
• MCP is the mechanism that provides the pre-built tool function and schema, which is complementary to the action of Tool Use.