Skip to content

Commit fc5fc3d

Browse files
committed
Require JSON-RPC batch support
1 parent 3f700fd commit fc5fc3d

File tree

1 file changed

+15
-5
lines changed

1 file changed

+15
-5
lines changed

docs/specification/draft/basic/_index.md

Lines changed: 15 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ support exactly the features they need.
2828

2929
All messages between MCP clients and servers **MUST** follow the
3030
[JSON-RPC 2.0](https://www.jsonrpc.org/specification) specification. The protocol defines
31-
three types of messages:
31+
these types of messages:
3232

3333
### Requests
3434

@@ -70,14 +70,17 @@ Responses are sent in reply to requests, containing the result or error of the o
7070
```
7171

7272
- Responses **MUST** include the same ID as the request they correspond to.
73-
- **Responses** are further sub-categorized as either **successful results** or **errors**. Either a `result` or an `error` **MUST** be set. A response **MUST NOT** set both.
74-
- Results **MAY** follow any JSON object structure, while errors **MUST** include an error code and
75-
message at minimum.
73+
- **Responses** are further sub-categorized as either **successful results** or
74+
**errors**. Either a `result` or an `error` **MUST** be set. A response **MUST NOT**
75+
set both.
76+
- Results **MAY** follow any JSON object structure, while errors **MUST** include an
77+
error code and message at minimum.
7678
- Error codes **MUST** be integers.
7779

7880
### Notifications
7981

80-
Notifications are sent from the client to the server or vice versa, as a one-way message. The receiver **MUST NOT** send a response.
82+
Notifications are sent from the client to the server or vice versa, as a one-way message.
83+
The receiver **MUST NOT** send a response.
8184

8285
```typescript
8386
{
@@ -91,6 +94,13 @@ Notifications are sent from the client to the server or vice versa, as a one-way
9194

9295
- Notifications **MUST NOT** include an ID.
9396

97+
### Batching
98+
99+
JSON-RPC also defines a means to
100+
[batch multiple requests and notifications](https://www.jsonrpc.org/specification#batch),
101+
by sending them in an array. MCP implementations **MAY** support sending JSON-RPC
102+
batches, but **MUST** support receiving JSON-RPC batches.
103+
94104
## Auth
95105

96106
MCP provides an [Authorization]({{< ref "/specification/draft/basic/authorization" >}})

0 commit comments

Comments
 (0)