Skip to content

Commit 53e2656

Browse files
committed
fix: update spec links from latest to draft
1 parent e6c71bb commit 53e2656

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@
3838
## Overview
3939

4040
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:
4242

4343
- Create MCP servers that expose resources, prompts and tools
4444
- Build MCP clients that can connect to any MCP server
@@ -158,7 +158,7 @@ const server = new McpServer({
158158

159159
### Tools
160160

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,
162162
and the arguments.
163163

164164
```typescript
@@ -259,7 +259,7 @@ Tools can return `ResourceLink` objects to reference resources without embedding
259259

260260
### Resources
261261

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.
263263

264264
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.
265265

@@ -333,7 +333,7 @@ server.registerResource(
333333

334334
### Prompts
335335

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.
337337

338338
```typescript
339339
import { completable } from '@modelcontextprotocol/sdk/server/completable.js';

0 commit comments

Comments
 (0)