Skip to content

Commit c7f3ef4

Browse files
authored
Merge branch 'main' into davidsp/fix-endpoint
2 parents 53399ff + eb02b2a commit c7f3ef4

File tree

5 files changed

+83
-48
lines changed

5 files changed

+83
-48
lines changed

docs/clients.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ This page provides an overview of applications that support the Model Context Pr
3535
| [Goose][Goose] ||||||| Supports tools. |
3636
| [gptme][gptme] ||||||| Supports tools. |
3737
| [HyperAgent][HyperAgent] ||||||| Supports tools. |
38-
| [JetBrains AI Assistant][JetBrains AI Assistant] ||||||| Supports tools for all JetBrains IDEs. |
38+
| [JetBrains AI Assistant][JetBrains AI Assistant] ||||||| Supports tools for all JetBrains IDEs. |
3939
| [Klavis AI Slack/Discord/Web][Klavis AI] ||||||| Supports tools and resources. |
4040
| [LibreChat][LibreChat] ||||||| Supports tools for Agents |
4141
| [Lutra][Lutra] ||||||| Supports any MCP server for reusable playbook creation. |

docs/specification/draft/basic/index.mdx

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22
title: Overview
33
---
44

5+
<div id="enable-section-numbers" />
6+
57
<Info>**Protocol Revision**: draft</Info>
68

79
The Model Context Protocol consists of several key components that work together:
@@ -116,3 +118,29 @@ There is also a
116118
[JSON Schema](https://github.com/modelcontextprotocol/specification/blob/main/schema/draft/schema.json),
117119
which is automatically generated from the TypeScript source of truth, for use with
118120
various automated tooling.
121+
122+
### General fields
123+
124+
#### `_meta`
125+
126+
The `_meta` property/parameter is reserved by MCP to allow clients and servers
127+
to attach additional metadata to their interactions.
128+
129+
Certain key names are reserved by MCP for protocol-level metadata, as specified below;
130+
implementations must not make assumptions about values at these keys.
131+
132+
Additionally, definitions in the [schema](https://github.com/modelcontextprotocol/specification/blob/main/schema/draft/schema.ts)
133+
may reserve particular names for purpose-specific metadata, as declared in those definitions.
134+
135+
**Key name format:** valid `_meta` key names have two segments: an optional **prefix**, and a **name**.
136+
137+
**Prefix:**
138+
139+
- If specified, must be a series of labels separated by dots (`.`), followed by a slash (`/`).
140+
- Labels must start with a letter and end with a letter or digit; interior characters can be letters, digits, or hyphens (`-`).
141+
- The `modelcontextprotocol.[*]/` and `mcp.[*]/` prefixes are reserved for MCP use (where `[*]` stands for any top-level domain).
142+
143+
**Name:**
144+
145+
- Unless empty, must begin and end with an alphanumeric character (`[a-z0-9A-Z]`).
146+
- Could contain hyphens (`-`), underscores (`_`), dots (`.`), and alphanumerics in between.

docs/specification/draft/server/utilities/completion.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ what is being completed through a reference type:
7878
}
7979
```
8080

81-
For prompts or URI templates with multiple arguments, clients should resolve them in the order they are presented by the server, and include each previous completion in the `context.arguments` object to provide context for subsequent requests.
81+
For prompts or URI templates with multiple arguments, clients should include previous completions in the `context.arguments` object to provide context for subsequent requests.
8282

8383
**Request:**
8484

0 commit comments

Comments
 (0)