Jeremiah Lowin commited on
Commit
6fc0f8b
·
1 Parent(s): ef267ad

Update Claude Desktop to reflect remote server support

Browse files
docs/integrations/claude-desktop.mdx CHANGED
@@ -6,7 +6,11 @@ icon: desktop
6
  ---
7
 
8
 
9
- Claude Desktop supports MCP servers through local STDIO connections, allowing you to extend Claude's capabilities with custom tools, resources, and prompts from your FastMCP servers.
 
 
 
 
10
 
11
  <Note>
12
  This guide focuses specifically on using FastMCP servers with Claude Desktop. For general Claude Desktop MCP setup and official examples, see the [official Claude Desktop quickstart guide](https://modelcontextprotocol.io/quickstart/user).
@@ -15,10 +19,10 @@ This guide focuses specifically on using FastMCP servers with Claude Desktop. Fo
15
 
16
  ## Requirements
17
 
18
- Claude Desktop requires MCP servers to run locally using STDIO transport. This means your server will communicate with Claude through standard input/output rather than HTTP.
19
 
20
  <Tip>
21
- If you need to connect to remote servers, you can create a **proxy server** that runs locally via STDIO and forwards requests to remote HTTP servers. See the [Proxy Servers](#proxy-servers) section below.
22
  </Tip>
23
 
24
  ## Create a Server
@@ -181,7 +185,7 @@ Claude Desktop runs servers in a completely isolated environment with no access
181
  ## Remote Servers
182
 
183
 
184
- Claude Desktop only supports local STDIO servers, but FastMCP can create a proxy server that forwards requests to a remote HTTP server. You can install the proxy server in Claude Desktop.
185
 
186
  Create a proxy server that connects to a remote HTTP server:
187
 
 
6
  ---
7
 
8
 
9
+ Claude Desktop supports MCP servers through local STDIO connections and remote servers (beta), allowing you to extend Claude's capabilities with custom tools, resources, and prompts from your FastMCP servers.
10
+
11
+ <Note>
12
+ Remote MCP server support is currently in beta and available for users on Claude Pro, Max, Team, and Enterprise plans (as of June 2025). Most users will still need to use local STDIO connections.
13
+ </Note>
14
 
15
  <Note>
16
  This guide focuses specifically on using FastMCP servers with Claude Desktop. For general Claude Desktop MCP setup and official examples, see the [official Claude Desktop quickstart guide](https://modelcontextprotocol.io/quickstart/user).
 
19
 
20
  ## Requirements
21
 
22
+ Claude Desktop traditionally requires MCP servers to run locally using STDIO transport, where your server communicates with Claude through standard input/output rather than HTTP. However, users on certain plans now have access to remote server support as well.
23
 
24
  <Tip>
25
+ If you don't have access to remote server support or need to connect to remote servers, you can create a **proxy server** that runs locally via STDIO and forwards requests to remote HTTP servers. See the [Proxy Servers](#proxy-servers) section below.
26
  </Tip>
27
 
28
  ## Create a Server
 
185
  ## Remote Servers
186
 
187
 
188
+ Users on Claude Pro, Max, Team, and Enterprise plans have first-class remote server support via integrations. For other users, or as an alternative approach, FastMCP can create a proxy server that forwards requests to a remote HTTP server. You can install the proxy server in Claude Desktop.
189
 
190
  Create a proxy server that connects to a remote HTTP server:
191