added naming convention and default transport

Author: amirejaz

docs/toolhive/guides-cli/run-mcp-servers.mdx

@@ -32,13 +32,32 @@ thv run fetch
 
 ### Remote MCP servers
 
-For remote MCP servers in the registry, such as the Neon or Stripe servers:
+Remote MCP servers in the registry don't run as local containers but instead use ToolHive's transparent http proxy to forward requests to remote servers. For example:
 
 ```bash
 thv run neon
 thv run stripe
 ```
 
+When you run a remote server from the registry, ToolHive uses the pre-configured remote URL and authentication settings. By default, remote servers use the `streamable-http` transport. If the server uses Server-Sent Events (SSE), specify the transport flag:
+
+```bash
+thv run <SERVER_NAME> --transport sse
+```
+
+:::note[Naming convention]
+
+Remote MCP servers use the `-remote` suffix **when they have a local containerized counterpart** to distinguish between the two versions. For example:
+- `github-remote` indicates this is the remote version of a server that also has a local `github` version
+- `neon` and `stripe` don't have local counterparts, so they don't use the `-remote` suffix
+
+To run a remote github mcp server, you should use the `github-remote` name.
+
+```bash
+thv run github-remote
+```
+:::
+
 :::info[What's happening?]
 
 When you run an MCP server from the registry, ToolHive handles different server
@@ -56,11 +75,12 @@ types automatically:
    ```
 
 **For remote MCP servers:**
-1. Automatically detects if the remote server requires authentication.
-2. Handles OAuth/OIDC authentication flows if needed.
-3. Starts an HTTP proxy process on a random port to forward client requests to
+1. Uses the pre-configured remote URL from the registry.
+2. Automatically detects if the remote server requires authentication.
+3. Handles OAuth/OIDC authentication flows if needed.
+4. Starts an HTTP proxy process on a random port to forward client requests to
    the remote server.
-4. Manages the server like any other ToolHive workload. No conatainer is created for remote MCP servers.
+5. Manages the server like any other ToolHive workload. No container is created for remote MCP servers.
 
 :::