Appendix
Appendix
Section titled “Appendix”This appendix provides supplementary information, including a glossary of common MCP terms and a list of useful resources to help you further explore and work with the Model Context Protocol.
Glossary of MCP Terms
Section titled “Glossary of MCP Terms”- Client (MCP Client): An application or component that consumes services from an MCP Server. Clients request resources, invoke prompts, and call tools to provide context to LLMs or automate tasks.
- Server (MCP Server): An application or component that implements the MCP specification to expose data and capabilities. Servers provide resources, prompts, and tools to connected MCP Clients.
- Resource: A piece of contextual information provided by an MCP Server (e.g., a file, a database record, a calendar event). Resources are typically identified by a URI and fetched using the
mcp_getResourcemethod. - Prompt (MCP Prompt): A server-exposed capability that allows a client to request the server to construct a prompt for an LLM, often incorporating contextual information from its resources. Invoked using
mcp_invokePrompt. - Tool (MCP Tool): A server-exposed capability that allows a client to request the server to perform an action or computation. Tools can have side effects (e.g., sending an email, updating a database). Invoked using
mcp_invokeTool. - Capabilities: The set of features, methods, and specifications supported by an MCP Client or Server. Negotiated upon connection using methods like
mcp_getCapabilities. - JSON-RPC: The remote procedure call protocol format used by MCP for structuring requests and responses. MCP messages are JSON-RPC 2.0 messages.
- Host Application: An application that embeds or manages MCP clients and/or servers, such as an IDE, a desktop application, or a web service.
- Transport: The underlying communication mechanism used to exchange MCP messages (e.g., WebSockets, HTTP, IPC).
- MCP Inspector: A utility (if available) for developers to connect to, test, and debug MCP servers by directly invoking methods and inspecting responses.
- SDK (Software Development Kit): Libraries provided to simplify the development of MCP clients and servers in specific programming languages (e.g., TypeScript, Python).
Useful Links
Section titled “Useful Links”Here are some essential links for finding more information, documentation, and community resources related to MCP. (Note: These are general placeholder links and should be replaced with actual URLs from the official MCP website.)
- Official MCP Website:
https://modelcontextprotocol.io(This is the primary source of truth) - MCP Specification Repository: (e.g.,
https://github.com/model-context-protocol/specification) - Link to the GitHub repository containing the formal MCP specification. - MCP TypeScript SDK Repository: (e.g.,
https://github.com/model-context-protocol/mcp-sdk-ts) - Link to the official TypeScript SDK. - MCP Python SDK Repository: (e.g.,
https://github.com/model-context-protocol/mcp-sdk-py) - Link to the official Python SDK. - MCP Servers Repository: (e.g.,
https://github.com/model-context-protocol/mcp-servers) - Link to a collection of official and community-contributed MCP servers, if such a repository exists. - Community Discussion Forum/Channel: (e.g., Link to GitHub Discussions, Discord server, or other community platforms mentioned on the official site).
Always refer to the official MCP website for the most current and accurate list of resources.