|
39 | 39 | ## Overview |
40 | 40 |
|
41 | 41 | 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 |
42 | | -[the full MCP specification](https://modelcontextprotocol.io/specification/latest), making it easy to: |
| 42 | +[the full MCP specification](https://modelcontextprotocol.io/specification/draft), making it easy to: |
43 | 43 |
|
44 | 44 | - Create MCP servers that expose resources, prompts and tools |
45 | 45 | - Build MCP clients that can connect to any MCP server |
@@ -159,7 +159,7 @@ const server = new McpServer({ |
159 | 159 |
|
160 | 160 | ### Tools |
161 | 161 |
|
162 | | -[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, |
| 162 | +[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, |
163 | 163 | and the arguments. |
164 | 164 |
|
165 | 165 | ```typescript |
@@ -260,7 +260,7 @@ Tools can return `ResourceLink` objects to reference resources without embedding |
260 | 260 |
|
261 | 261 | ### Resources |
262 | 262 |
|
263 | | -[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. |
| 263 | +[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. |
264 | 264 |
|
265 | 265 | 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. |
266 | 266 |
|
@@ -334,7 +334,7 @@ server.registerResource( |
334 | 334 |
|
335 | 335 | ### Prompts |
336 | 336 |
|
337 | | -[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. |
| 337 | +[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. |
338 | 338 |
|
339 | 339 | ```typescript |
340 | 340 | import { completable } from '@modelcontextprotocol/sdk/server/completable.js'; |
|
0 commit comments