fixed authentication section

Author: amirejaz

docs/toolhive/guides-cli/manage-mcp-servers.md

@@ -18,7 +18,7 @@ thv list
 ```
 
 This shows the server name, package, status, url, port, tool type, group, and created at. Remote
-servers will show their target URL in url, and remote in package and tool type columns making it easy to identify them.
+servers display their target URL in the URL column. The word 'remote' is indicated in both the package and tool type columns, making it easy to identify remote servers.
 
 To include stopped servers in the list:
 

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

@@ -39,11 +39,7 @@ 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
-```
+When you run a remote server from the registry, ToolHive uses the pre-configured remote URL and authentication settings.
 
 :::note[Naming convention]
 
@@ -601,7 +597,15 @@ thv run <URL> [--name <SERVER_NAME>]
 For example:
 
 ```bash
-thv run https://api.example.com/mcp --name my-remote-server
+thv run https://api.example.com/mcp
+```
+
+If you don't specify a name with `--name`, ToolHive will automatically derive a name from the URL by extracting the main domain name (e.g., `notion` from `https://api.notion.com/mcp`).
+
+By default, remote servers use the `streamable-http` transport. If the server uses Server-Sent Events (SSE), specify the transport flag:
+
+```bash
+thv run https://api.example.com/sse --transport sse
 ```
 
 :::info[What's happening?]
@@ -612,7 +616,7 @@ When you run a remote MCP server, ToolHive:
 2. Handles OAuth/OIDC authentication flows if needed.
 3. 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.
+4. Manages the server like any other ToolHive workload. No container is created for remote MCP servers.
 
 :::
 
@@ -630,11 +634,11 @@ examining the server's response headers and status codes:
 thv run https://protected-api.com/mcp --name my-server
 ```
 
-If authentication is required, ToolHive will prompt you to complete the OAuth flow.
+If authentication is required, ToolHive will prompt you to complete the OAuth flow. When no client credentials are provided, ToolHive automatically registers an OAuth client with the authorization server using RFC 7591 dynamic client registration, eliminating the need to pre-configure client ID and secret.
 
-#### OAuth/OIDC authentication
+#### OIDC authentication
 
-For servers requiring OAuth or OIDC authentication, you can provide the issuer URL:
+For servers using OpenID Connect (OIDC), you can provide the issuer URL:
 
 ```bash
 thv run https://api.example.com/mcp \
@@ -643,38 +647,26 @@ thv run https://api.example.com/mcp \
   --remote-auth-client-id my-client-id
 ```
 
-#### Dynamic client registration
+#### OAuth2 authentication
 
-When no client credentials are provided, ToolHive automatically registers an OAuth client
-with the authorization server using RFC 7591 dynamic client registration:
+For servers using OAuth2, you can specify the authorization and token URLs manually:
 
 ```bash
-thv run https://api.example.com/mcp --name my-server
+thv run https://api.example.com/mcp \
+  --name my-server \
+  --remote-auth-authorize-url https://auth.example.com/oauth/authorize \
+  --remote-auth-token-url https://auth.example.com/oauth/token \
+  --remote-auth-client-id my-client-id \
+  --remote-auth-client-secret my-client-secret
 ```
 
-This eliminates the need to pre-configure client ID and secret, making it easier to
-connect to remote MCP servers.
-
 #### Automatic token refresh
 
 ToolHive automatically handles OAuth token refresh for remote MCP servers. When you
 authenticate with a remote server, ToolHive stores both the access token and refresh
 token securely. The refresh token is used to automatically obtain new access tokens
 when they expire, ensuring uninterrupted service without requiring manual re-authentication.
 
-#### Custom OAuth endpoints
-
-For non-OIDC OAuth servers, you can specify custom authorization and token endpoints:
-
-```bash
-thv run https://api.example.com/mcp \
-  --name my-server \
-  --remote-auth-authorize-url https://auth.example.com/oauth/authorize \
-  --remote-auth-token-url https://auth.example.com/oauth/token \
-  --remote-auth-client-id my-client-id \
-  --remote-auth-client-secret my-client-secret
-```
-
 ### Advanced remote server configuration
 
 #### OAuth scopes and parameters