|
38 | 38 | ## Overview |
39 | 39 |
|
40 | 40 | The Model Context Protocol allows applications to provide context for LLMs in a standardized way, separating the concerns of providing context from the actual LLM interaction. This TypeScript SDK implements |
41 | | -[the full MCP specification](https://modelcontextprotocol.io/specification/latest), making it easy to: |
| 41 | +[the full MCP specification](https://modelcontextprotocol.io/specification/draft), making it easy to: |
42 | 42 |
|
43 | 43 | - Create MCP servers that expose resources, prompts and tools |
44 | 44 | - Build MCP clients that can connect to any MCP server |
@@ -158,7 +158,7 @@ const server = new McpServer({ |
158 | 158 |
|
159 | 159 | ### Tools |
160 | 160 |
|
161 | | -[Tools](https://modelcontextprotocol.io/specification/latest/server/tools) let LLMs take actions through your server. Tools can perform computation, fetch data and have side effects. Tools should be designed to be model-controlled - i.e. AI models will decide which tools to call, |
| 161 | +[Tools](https://modelcontextprotocol.io/specification/draft/server/tools) let LLMs take actions through your server. Tools can perform computation, fetch data and have side effects. Tools should be designed to be model-controlled - i.e. AI models will decide which tools to call, |
162 | 162 | and the arguments. |
163 | 163 |
|
164 | 164 | ```typescript |
@@ -259,7 +259,7 @@ Tools can return `ResourceLink` objects to reference resources without embedding |
259 | 259 |
|
260 | 260 | ### Resources |
261 | 261 |
|
262 | | -[Resources](https://modelcontextprotocol.io/specification/latest/server/resources) can also expose data to LLMs, but unlike tools shouldn't perform significant computation or have side effects. |
| 262 | +[Resources](https://modelcontextprotocol.io/specification/draft/server/resources) can also expose data to LLMs, but unlike tools shouldn't perform significant computation or have side effects. |
263 | 263 |
|
264 | 264 | Resources are designed to be used in an application-driven way, meaning MCP client applications can decide how to expose them. For example, a client could expose a resource picker to the human, or could expose them to the model directly. |
265 | 265 |
|
@@ -333,7 +333,7 @@ server.registerResource( |
333 | 333 |
|
334 | 334 | ### Prompts |
335 | 335 |
|
336 | | -[Prompts](https://modelcontextprotocol.io/specification/latest/server/prompts) are reusable templates that help humans prompt models to interact with your server. They're designed to be user-driven, and might appear as slash commands in a chat interface. |
| 336 | +[Prompts](https://modelcontextprotocol.io/specification/draft/server/prompts) are reusable templates that help humans prompt models to interact with your server. They're designed to be user-driven, and might appear as slash commands in a chat interface. |
337 | 337 |
|
338 | 338 | ```typescript |
339 | 339 | import { completable } from '@modelcontextprotocol/sdk/server/completable.js'; |
|
0 commit comments