Skip to content

Commit 31a382d

Browse files
committed
Fix a couple of ambiguities around "client" vs. "host"
1 parent 231bf61 commit 31a382d

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

docs/specification/architecture/_index.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,13 +52,15 @@ The host process acts as the container and coordinator:
5252
- Manages context aggregation across clients
5353

5454
### Clients
55-
Each client maintains an isolated server connection:
55+
Each client is created by the host and maintains an isolated server connection:
5656
- Establishes one stateful session per server
5757
- Handles protocol negotiation and capability exchange
5858
- Routes protocol messages bidirectionally
5959
- Manages subscriptions and notifications
6060
- Maintains security boundaries between servers
6161

62+
A host application creates and manages multiple clients, with each client having a 1:1 relationship with a particular server.
63+
6264
### Servers
6365
Servers provide specialized context and capabilities:
6466
- Expose resources, tools and prompts via MCP primitives

docs/specification/server/resources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ The Model Context Protocol (MCP) provides a standardized way for servers to expo
1212

1313
## User Interaction Model
1414

15-
Resources in MCP are designed to be **application-driven**, with clients determining how to incorporate context based on their needs.
15+
Resources in MCP are designed to be **application-driven**, with host applications determining how to incorporate context based on their needs.
1616

1717
For example, applications could:
1818
* Expose resources through UI elements for explicit selection, in a tree or list view

0 commit comments

Comments
 (0)