Merge pull request #32 from modelcontextprotocol/justin/clarify-clients
Clarify "hosts" vs. "clients" terminology in a few places
This commit is contained in:
commit
959353e00d
2 changed files with 32 additions and 31 deletions
|
|
@ -129,7 +129,7 @@ When servers fail to connect:
|
||||||
|
|
||||||
### Server-side logging
|
### Server-side logging
|
||||||
|
|
||||||
When building a server that uses the local stdio [transport](/docs/concepts/transports), all messages logged to stderr (standard error) will be captured by the client (e.g., Claude Desktop) automatically.
|
When building a server that uses the local stdio [transport](/docs/concepts/transports), all messages logged to stderr (standard error) will be captured by the host application (e.g., Claude Desktop) automatically.
|
||||||
|
|
||||||
<Warning>
|
<Warning>
|
||||||
Local MCP servers should not log messages to stdout (standard out), as this will interfere with protocol operation.
|
Local MCP servers should not log messages to stdout (standard out), as this will interfere with protocol operation.
|
||||||
|
|
|
||||||
|
|
@ -3,14 +3,14 @@ title: "Quickstart"
|
||||||
description: "Get started with MCP in less than 5 minutes"
|
description: "Get started with MCP in less than 5 minutes"
|
||||||
---
|
---
|
||||||
|
|
||||||
MCP is a protocol that enables secure connections between clients, such as the Claude Desktop app, and local services. In this quickstart guide, you'll learn how to:
|
MCP is a protocol that enables secure connections between host applications, such as [Claude Desktop](https://claude.ai/download), and local services. In this quickstart guide, you'll learn how to:
|
||||||
|
|
||||||
- Set up a local SQLite database
|
- Set up a local SQLite database
|
||||||
- Connect Claude Desktop to it through MCP
|
- Connect Claude Desktop to it through MCP
|
||||||
- Query and analyze your data securely
|
- Query and analyze your data securely
|
||||||
|
|
||||||
<Note>
|
<Note>
|
||||||
While this guide focuses on using Claude Desktop as an example MCP client, the protocol is open and can be implemented by any application. IDEs, AI tools, and other software can all act as MCP clients to access local integrations in a standardized way.
|
While this guide focuses on using Claude Desktop as an example MCP host, the protocol is open and can be integrated by any application. IDEs, AI tools, and other software can all use MCP to connect to local integrations in a standardized way.
|
||||||
</Note>
|
</Note>
|
||||||
|
|
||||||
<Warning>
|
<Warning>
|
||||||
|
|
@ -22,19 +22,19 @@ Claude Desktop's MCP support is currently in developer preview and only supports
|
||||||
MCP (Model Context Protocol) is an open protocol that enables secure, controlled interactions between AI applications and local or remote resources. Let's break down how it works, then look at how we'll use it in this guide.
|
MCP (Model Context Protocol) is an open protocol that enables secure, controlled interactions between AI applications and local or remote resources. Let's break down how it works, then look at how we'll use it in this guide.
|
||||||
|
|
||||||
### General Architecture
|
### General Architecture
|
||||||
At its core, MCP follows a client-server architecture where multiple services can connect to any compatible client:
|
At its core, MCP follows a client-server architecture where a host application can connect to multiple servers:
|
||||||
|
|
||||||
```mermaid
|
```mermaid
|
||||||
flowchart LR
|
flowchart LR
|
||||||
subgraph "Your Computer"
|
subgraph "Your Computer"
|
||||||
Client["MCP Clients\n(Claude, IDEs, Tools)"]
|
Host["MCP Host\n(Claude, IDEs, Tools)"]
|
||||||
S1["MCP Server A"]
|
S1["MCP Server A"]
|
||||||
S2["MCP Server B"]
|
S2["MCP Server B"]
|
||||||
S3["MCP Server C"]
|
S3["MCP Server C"]
|
||||||
|
|
||||||
Client <-->|"MCP Protocol"| S1
|
Host <-->|"MCP Protocol"| S1
|
||||||
Client <-->|"MCP Protocol"| S2
|
Host <-->|"MCP Protocol"| S2
|
||||||
Client <-->|"MCP Protocol"| S3
|
Host <-->|"MCP Protocol"| S3
|
||||||
|
|
||||||
S1 <--> R1[("Local\nResource A")]
|
S1 <--> R1[("Local\nResource A")]
|
||||||
S2 <--> R2[("Local\nResource B")]
|
S2 <--> R2[("Local\nResource B")]
|
||||||
|
|
@ -45,7 +45,8 @@ flowchart LR
|
||||||
end
|
end
|
||||||
```
|
```
|
||||||
|
|
||||||
- **MCP Clients**: Applications like Claude Desktop, IDEs, or AI tools that want to access resources
|
- **MCP Hosts**: Programs like Claude Desktop, IDEs, or AI tools that want to access resources through MCP
|
||||||
|
- **MCP Clients**: Protocol clients that maintain 1:1 connections with servers
|
||||||
- **MCP Servers**: Lightweight programs that each expose specific capabilities through the standardized Model Context Protocol
|
- **MCP Servers**: Lightweight programs that each expose specific capabilities through the standardized Model Context Protocol
|
||||||
- **Local Resources**: Your computer's resources (databases, files, services) that MCP servers can securely access
|
- **Local Resources**: Your computer's resources (databases, files, services) that MCP servers can securely access
|
||||||
- **Remote Resources**: Resources available over the internet (e.g., through APIs) that MCP servers can connect to
|
- **Remote Resources**: Resources available over the internet (e.g., through APIs) that MCP servers can connect to
|
||||||
|
|
@ -342,9 +343,9 @@ Want to give Claude Desktop more local integration capabilities? Add these serve
|
||||||
</Accordion>
|
</Accordion>
|
||||||
</AccordionGroup>
|
</AccordionGroup>
|
||||||
|
|
||||||
## MCP clients
|
## More MCP Hosts
|
||||||
|
|
||||||
While this guide demonstrates MCP using Claude Desktop, several other applications support MCP integration:
|
While this guide demonstrates MCP using Claude Desktop as a host, several other applications support MCP integration:
|
||||||
|
|
||||||
<CardGroup cols={2}>
|
<CardGroup cols={2}>
|
||||||
<Card
|
<Card
|
||||||
|
|
@ -362,7 +363,7 @@ While this guide demonstrates MCP using Claude Desktop, several other applicatio
|
||||||
</Card>
|
</Card>
|
||||||
</CardGroup>
|
</CardGroup>
|
||||||
|
|
||||||
Each client may implement MCP features differently or support different capabilities. Check their respective documentation for specific setup instructions and supported features.
|
Each host application may implement MCP features differently or support different capabilities. Check their respective documentation for specific setup instructions and supported features.
|
||||||
|
|
||||||
## Troubleshooting
|
## Troubleshooting
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue