Introducing MCP

Model Context Protocol (MCP) Study Notes

**I. Core Concepts**

• Definition: MCP is a communication layer designed to provide Claude with context and tools without requiring the developer to write extensive code.
• Architecture: MCP consists of two major elements: the Client and the Server.
• Server Components: The MCP Server typically contains tools, resources, and prompts.
• The Tool: A tool exposes functionality related to an outside service (e. g. , accessing GitHub data).

**II. The Problem MCP Solves**

• Developer Burden: Building a complete chatbot (e. g. , one accessing all GitHub features) requires developers to author a massive number of tool schemas and function implementations.
• MCP's Role: MCP shifts the burden of defining and running tools from the developer's server to a dedicated MCP Server.
• Benefit: Developers do not have to author all the tool schemas and functions; this is handled by the MCP Server.

**III. MCP Server Functionality**

• Function: An MCP Server acts as an interface to an outside service.
• Implementation: It wraps the functionality of an external service (e. g. , GitHub) and places it into the form of a set of pre-built tools.
• Authorship: Anyone can create an MCP server implementation, though service providers often release official versions.

**IV. MCP vs. Direct API Calls**

• Direct API Call: Requires the developer to author both the tool schema and the function implementation themselves.
• Using MCP: Saves time because the MCP Server handles the authoring and implementation of the tool's schema and function.

**V. MCP vs. Tool Use (Key Distinction)**

• Relationship: MCP servers and tool use are complementary, not the same thing.
• Tool Use: Refers to the action of using a function.
• MCP Server: Refers to who is doing the work—it is the entity that provides the pre-built tool function and schema.

Takeaways

• MCP is a communication layer designed to provide Claude with context and tools without requiring developers to write extensive code.
• The MCP Server acts as an interface that wraps external services into a set of pre-built tools, significantly reducing the developer burden.
• Using MCP saves time compared to direct API calls because the MCP Server handles the authoring and implementation of tool schemas and functions.
• MCP servers and tool use are complementary: the MCP Server is the entity that provides the pre-built tool, while tool use is the action of utilizing that function.