From 81605d89183b84ecfd2ad5d97e54b93ed8a0cda2 Mon Sep 17 00:00:00 2001 From: Zack Lee Date: Tue, 19 Nov 2024 16:16:26 -0500 Subject: [PATCH] migrated specs --- specification/overview.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/specification/overview.mdx b/specification/overview.mdx index 5215929..92e5e7a 100644 --- a/specification/overview.mdx +++ b/specification/overview.mdx @@ -2,14 +2,12 @@ title: Overview --- -_**NOTE:** This is a very early draft. Feel free to discuss changes, requirements, etc._ - -# Goal The Model Context Protocol (MCP) is an attempt to allow implementors to provide context to various LLM surfaces such as editors/IDEs, [claude.ai](https://claude.ai), etc., in a pluggable way. It separates the concerns of providing context from the LLM loop and its usage within. This makes it **much** easier for anyone to script LLM applications for accomplishing their custom workflows, without the application needing to directly offer a large number of integrations. # Terminology + The Model Context Protocol is inspired by Microsoft's [Language Server Protocol](https://microsoft.github.io/language-server-protocol/), with similar concepts: * **Server**: a process or service providing context via MCP.