Skip to content

Commit 191e749

Browse files
Merge branch 'main' into feat/tasks
2 parents 6447edd + e343bf5 commit 191e749

File tree

3 files changed

+7
-7
lines changed

3 files changed

+7
-7
lines changed

README.md

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

4141
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:
4343

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

160160
### Tools
161161

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

165165
```typescript
@@ -260,7 +260,7 @@ Tools can return `ResourceLink` objects to reference resources without embedding
260260

261261
### Resources
262262

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

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

@@ -334,7 +334,7 @@ server.registerResource(
334334

335335
### Prompts
336336

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

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

package-lock.json

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@modelcontextprotocol/sdk",
3-
"version": "1.23.0-beta.0",
3+
"version": "1.23.0",
44
"description": "Model Context Protocol implementation for TypeScript",
55
"license": "MIT",
66
"author": "Anthropic, PBC (https://anthropic.com)",

0 commit comments

Comments
 (0)