Merge branch 'main' into spec/sampling-includecontext

LucaButBoring · web-flow · commit f65cbaacdea9 · 2025-05-30T16:03:40.000-07:00
diff --git a/docs/specification/2024-11-05/index.mdx b/docs/specification/2024-11-05/index.mdx
@@ -122,9 +122,9 @@ implementors **SHOULD**:
 Explore the detailed specification for each protocol component:
 
 <CardGroup cols={5}>
-  <Card title="Architecture" icon="sitemap" href="architecture" />
-  <Card title="Base Protocol" icon="code" href="basic" />
-  <Card title="Server Features" icon="server" href="server" />
-  <Card title="Client Features" icon="user" href="client" />
-  <Card title="Contributing" icon="pencil" href="contributing" />
+  <Card title="Architecture" icon="sitemap" href="/specification/2024-11-05/architecture" />
+  <Card title="Base Protocol" icon="code" href="/specification/2024-11-05/basic" />
+  <Card title="Server Features" icon="server" href="/specification/2024-11-05/server" />
+  <Card title="Client Features" icon="user" href="/specification/2024-11-05/client" />
+  <Card title="Contributing" icon="pencil" href="/specification/contributing" />
 </CardGroup>
diff --git a/docs/specification/2024-11-05/server/index.mdx b/docs/specification/2024-11-05/server/index.mdx
@@ -25,7 +25,7 @@ Each primitive can be summarized in the following control hierarchy:
 Explore these key primitives in more detail below:
 
 <CardGroup cols={3}>
-  <Card title="Prompts" icon="message" href="prompts" />
-  <Card title="Resources" icon="file-lines" href="resources" />
-  <Card title="Tools" icon="wrench" href="tools" />
+  <Card title="Prompts" icon="message" href="/specification/2024-11-05/server/prompts" />
+  <Card title="Resources" icon="file-lines" href="/specification/2024-11-05/server/resources" />
+  <Card title="Tools" icon="wrench" href="/specification/2024-11-05/server/tools" />
 </CardGroup>
diff --git a/docs/specification/2024-11-05/server/prompts.mdx b/docs/specification/2024-11-05/server/prompts.mdx
@@ -20,7 +20,7 @@ interface, which allows users to naturally discover and invoke available prompts
 
 For example, as slash commands:
 
-![Example of prompt exposed as slash command](slash-command.png)
+![Example of prompt exposed as slash command](/specification/2024-11-05/server/slash-command.png)
 
 However, implementors are free to expose prompts through any interface pattern that suits
 their needs&mdash;the protocol itself does not mandate any specific user interaction
diff --git a/docs/specification/2024-11-05/server/resources.mdx b/docs/specification/2024-11-05/server/resources.mdx
@@ -23,7 +23,7 @@ For example, applications could:
 - Allow the user to search through and filter available resources
 - Implement automatic context inclusion, based on heuristics or the AI model's selection
 
-![Example of resource context picker](resource-picker.png)
+![Example of resource context picker](/specification/2024-11-05/server/resource-picker.png)
 
 However, implementations are free to expose resources through any interface pattern that
 suits their needs&mdash;the protocol itself does not mandate any specific user
diff --git a/docs/specification/2025-03-26/index.mdx b/docs/specification/2025-03-26/index.mdx
@@ -124,9 +124,9 @@ implementors **SHOULD**:
 Explore the detailed specification for each protocol component:
 
 <CardGroup cols={5}>
-  <Card title="Architecture" icon="sitemap" href="architecture" />
-  <Card title="Base Protocol" icon="code" href="basic" />
-  <Card title="Server Features" icon="server" href="server" />
-  <Card title="Client Features" icon="user" href="client" />
-  <Card title="Contributing" icon="pencil" href="contributing" />
+  <Card title="Architecture" icon="sitemap" href="/specification/2025-03-26/architecture" />
+  <Card title="Base Protocol" icon="code" href="/specification/2025-03-26/basic" />
+  <Card title="Server Features" icon="server" href="/specification/2025-03-26/server" />
+  <Card title="Client Features" icon="user" href="/specification/2025-03-26/client" />
+  <Card title="Contributing" icon="pencil" href="/specification/contributing" />
 </CardGroup>
diff --git a/docs/specification/2025-03-26/server/index.mdx b/docs/specification/2025-03-26/server/index.mdx
@@ -25,7 +25,7 @@ Each primitive can be summarized in the following control hierarchy:
 Explore these key primitives in more detail below:
 
 <CardGroup cols={3}>
-  <Card title="Prompts" icon="message" href="prompts" />
-  <Card title="Resources" icon="file-lines" href="resources" />
-  <Card title="Tools" icon="wrench" href="tools" />
+  <Card title="Prompts" icon="message" href="/specification/2025-03-26/server/prompts" />
+  <Card title="Resources" icon="file-lines" href="/specification/2025-03-26/server/resources" />
+  <Card title="Tools" icon="wrench" href="/specification/2025-03-26/server/tools" />
 </CardGroup>
diff --git a/docs/specification/2025-03-26/server/prompts.mdx b/docs/specification/2025-03-26/server/prompts.mdx
@@ -19,7 +19,7 @@ interface, which allows users to naturally discover and invoke available prompts
 
 For example, as slash commands:
 
-![Example of prompt exposed as slash command](slash-command.png)
+![Example of prompt exposed as slash command](/specification/2025-03-26/server/slash-command.png)
 
 However, implementors are free to expose prompts through any interface pattern that suits
 their needs&mdash;the protocol itself does not mandate any specific user interaction
diff --git a/docs/specification/2025-03-26/server/resources.mdx b/docs/specification/2025-03-26/server/resources.mdx
@@ -21,7 +21,7 @@ For example, applications could:
 - Allow the user to search through and filter available resources
 - Implement automatic context inclusion, based on heuristics or the AI model's selection
 
-![Example of resource context picker](resource-picker.png)
+![Example of resource context picker](/specification/2025-03-26/server/resource-picker.png)
 
 However, implementations are free to expose resources through any interface pattern that
 suits their needs&mdash;the protocol itself does not mandate any specific user
diff --git a/docs/specification/draft/client/elicitation.mdx b/docs/specification/draft/client/elicitation.mdx
@@ -4,6 +4,10 @@ title: Elicitation
 
 <Info>**Protocol Revision**: draft</Info>
 
+<Note>
+Elicitation is newly introduced in this version of the MCP specification and its design may evolve in future protocol versions.
+</Note>
+
 The Model Context Protocol (MCP) provides a standardized way for servers to request additional
 information from users through the client during interactions. This flow allows clients to
 maintain control over user interactions and data sharing while enabling servers to gather
diff --git a/docs/specification/draft/index.mdx b/docs/specification/draft/index.mdx
@@ -125,9 +125,9 @@ implementors **SHOULD**:
 Explore the detailed specification for each protocol component:
 
 <CardGroup cols={5}>
-  <Card title="Architecture" icon="sitemap" href="architecture" />
-  <Card title="Base Protocol" icon="code" href="basic" />
-  <Card title="Server Features" icon="server" href="server" />
-  <Card title="Client Features" icon="user" href="client" />
-  <Card title="Contributing" icon="pencil" href="contributing" />
+  <Card title="Architecture" icon="sitemap" href="/specification/draft/architecture" />
+  <Card title="Base Protocol" icon="code" href="/specification/draft/basic" />
+  <Card title="Server Features" icon="server" href="/specification/draft/server" />
+  <Card title="Client Features" icon="user" href="/specification/draft/client" />
+  <Card title="Contributing" icon="pencil" href="/specification/contributing" />
 </CardGroup>
diff --git a/docs/specification/draft/server/index.mdx b/docs/specification/draft/server/index.mdx
@@ -25,7 +25,7 @@ Each primitive can be summarized in the following control hierarchy:
 Explore these key primitives in more detail below:
 
 <CardGroup cols={3}>
-  <Card title="Prompts" icon="message" href="prompts" />
-  <Card title="Resources" icon="file-lines" href="resources" />
-  <Card title="Tools" icon="wrench" href="tools" />
+  <Card title="Prompts" icon="message" href="/specification/draft/server/prompts" />
+  <Card title="Resources" icon="file-lines" href="/specification/draft/server/resources" />
+  <Card title="Tools" icon="wrench" href="/specification/draft/server/tools" />
 </CardGroup>
diff --git a/docs/specification/draft/server/prompts.mdx b/docs/specification/draft/server/prompts.mdx
@@ -19,7 +19,7 @@ interface, which allows users to naturally discover and invoke available prompts
 
 For example, as slash commands:
 
-![Example of prompt exposed as slash command](slash-command.png)
+![Example of prompt exposed as slash command](/specification/draft/server/slash-command.png)
 
 However, implementors are free to expose prompts through any interface pattern that suits
 their needs&mdash;the protocol itself does not mandate any specific user interaction
diff --git a/docs/specification/draft/server/resources.mdx b/docs/specification/draft/server/resources.mdx
@@ -21,7 +21,7 @@ For example, applications could:
 - Allow the user to search through and filter available resources
 - Implement automatic context inclusion, based on heuristics or the AI model's selection
 
-![Example of resource context picker](resource-picker.png)
+![Example of resource context picker](/specification/draft/server/resource-picker.png)
 
 However, implementations are free to expose resources through any interface pattern that
 suits their needs&mdash;the protocol itself does not mandate any specific user
