run prettier

Author: amirejaz

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

@@ -17,10 +17,10 @@ To see all currently running MCP servers:
 thv list
 ```
 
-This shows the server name, package, status, url, port, tool type, group, and created
-at. Remote 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.
+This shows the server name, package, status, url, port, tool type, group, and
+created at. Remote 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:
 
@@ -64,7 +64,8 @@ thv stop <SERVER_NAME>
 
 This stops the server and the associated proxy process, removes the MCP server's
 entry from your configured clients, but keeps the container for future use. For
-remote servers, this terminates the proxy process but preserves the configuration.
+remote servers, this terminates the proxy process but preserves the
+configuration.
 
 Add the `--group` flag to stop all servers in a specific group:
 
@@ -104,8 +105,8 @@ thv rm <SERVER_NAME>
 
 This removes the container and cleans up the MCP server's entry in your
 configured clients. If the server is still running, it will be stopped as part
-of the removal. For remote servers, this removes the proxy process, configuration,
-and stored authentication tokens.
+of the removal. For remote servers, this removes the proxy process,
+configuration, and stored authentication tokens.
 
 Add the `--group` flag to remove all servers in a specific group:
 
@@ -123,9 +124,9 @@ won't clean up the MCP server's entry in your configured clients. Use
 
 ### Remote server authentication
 
-Remote servers with OAuth authentication will automatically refresh tokens
-when they expire during normal operation. However, restarting a remote server
-always triggers a new OAuth authentication flow:
+Remote servers with OAuth authentication will automatically refresh tokens when
+they expire during normal operation. However, restarting a remote server always
+triggers a new OAuth authentication flow:
 
 ```bash
 thv restart <REMOTE_SERVER_NAME>

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

@@ -32,26 +32,35 @@ thv run fetch
 
 ### Remote MCP 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:
+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.
+When you run a remote server from the registry, ToolHive uses the pre-configured
+remote URL and authentication settings.
 
 :::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
+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?]
@@ -60,6 +69,7 @@ When you run an MCP server from the registry, ToolHive handles different server
 types automatically:
 
 **For local containerized servers:**
+
 1. Pulls the image and launches a container using the configuration from the
    registry.
 2. Starts an HTTP proxy process on a random port to forward client requests to
@@ -71,12 +81,14 @@ types automatically:
    ```
 
 **For remote MCP servers:**
+
 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.
-5. Manages the server like any other ToolHive workload. No container is created for remote MCP servers.
+5. Manages the server like any other ToolHive workload. No container is created
+   for remote MCP servers.
 
 :::
 
@@ -581,10 +593,10 @@ thv run --ca-cert /path/to/special-ca.crt uvx://other-package
 
 ## Run a remote MCP server
 
-You can run remote MCP servers directly by providing their URL. This allows you to
-connect to MCP servers hosted elsewhere without needing to manage containers locally.
-ToolHive creates a transparent proxy that handles authentication and forwards requests
-to the remote server.
+You can run remote MCP servers directly by providing their URL. This allows you
+to connect to MCP servers hosted elsewhere without needing to manage containers
+locally. ToolHive creates a transparent proxy that handles authentication and
+forwards requests to the remote server.
 
 ### Basic remote server setup
 
@@ -600,9 +612,12 @@ For example:
 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`).
+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:
+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
@@ -616,7 +631,8 @@ 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 container is created for remote MCP servers.
+4. Manages the server like any other ToolHive workload. No container is created
+   for remote MCP servers.
 
 :::
 
@@ -634,7 +650,10 @@ 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. 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.
+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.
 
 #### OIDC authentication
 
@@ -649,7 +668,8 @@ thv run https://api.example.com/mcp \
 
 #### OAuth2 authentication
 
-For servers using OAuth2, you can specify the authorization and token URLs manually:
+For servers using OAuth2, you can specify the authorization and token URLs
+manually:
 
 ```bash
 thv run https://api.example.com/mcp \
@@ -662,10 +682,11 @@ thv run https://api.example.com/mcp \
 
 #### 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.
+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.
 
 ### Advanced remote server configuration