Home Docs Model Context Protocol 20 Oct 2026

One change · mcp

Prompts changedspecification/2026-07-28/server/prompts

Nearest release: v2.1.305, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 20 Oct 2026 20:02 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 20:07 UTC.

Upstream edited 20 Oct 2026 20:02 UTC

Recorded here 20 Oct 2026 20:07 UTC

Lines+14added

Lines−16removed

From line 1 where the diff opens

First seen 14 Aug 2026 this site's first read of the page

Recorded edits2to this page, all time

The whole hunk

from line 1, old and new numbered

lines

from line 1

11# Prompts

3<div id="enable-section-numbers" />

53The Model Context Protocol (MCP) provides a standardized way for servers to expose prompt

64templates to clients. Prompts allow servers to provide structured messages and

75instructions for interacting with language models. Clients can discover available

86prompts, retrieve their contents, and provide arguments to customize them.

10<Note>

11 For brevity, the request examples on this page omit the `_meta` request

12 metadata (`io.modelcontextprotocol/protocolVersion`,

13 `io.modelcontextprotocol/clientInfo`, and

14 `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include

15 the required `_meta` fields; see

16 [`_meta`](/specification/2026-07-28/basic/index#meta).

17</Note>

8> [!NOTE]

10> For brevity, the request examples on this page omit the `_meta` request

11> metadata (`io.modelcontextprotocol/protocolVersion`,

12> `io.modelcontextprotocol/clientInfo`, and

13> `io.modelcontextprotocol/clientCapabilities`). Every request **MUST** include

14> the required `_meta` fields; see

15> [`_meta`](/specification/2026-07-28/basic/index#meta).

1816

1917## User Interaction Model

2018

from line 26

2826

2927For example, as slash commands:

3028

31<img src="https://mintcdn.com/mcp/UAHvrCg8SwnAZwI3/specification/2026-07-28/server/slash-command.png?fit=max&auto=format&n=UAHvrCg8SwnAZwI3&q=85&s=7ed7762fc5e3b4b32cba2a71ede48000" alt="Example of prompt exposed as slash command" width="293" height="106" data-path="specification/2026-07-28/server/slash-command.png" />

29![Example of prompt exposed as slash command](https://mintcdn.com/mcp/UAHvrCg8SwnAZwI3/specification/2026-07-28/server/slash-command.png?fit=max\&auto=format\&n=UAHvrCg8SwnAZwI3\&q=85\&s=7ed7762fc5e3b4b32cba2a71ede48000)

3230

3331However, implementors are free to expose prompts through any interface pattern that suits

3432their needs—the protocol itself does not mandate any specific user interaction

from line 218

220218* `role`: Either "user" or "assistant" to indicate the speaker

221219* `content`: One of the following content types:

222220

223<Note>

224 All content types in prompt messages support optional

225 [annotations](/specification/2026-07-28/server/resources#annotations) for

226 metadata about audience, priority, and modification times.

227</Note>

221> [!NOTE]

222>

223> All content types in prompt messages support optional

224> [annotations](/specification/2026-07-28/server/resources#annotations) for

225> metadata about audience, priority, and modification times.

228226

229227#### Text Content

230228