Update 2025-01-13-mcp-server.adoc

Co-authored-by: Georgios Andrianakis <[email protected]>

Author: maxandersen

_posts/2024-01-29-ngrok.adoc

@@ -164,11 +164,17 @@ The forecast API requires a two-step process where we first get point metadata a
 
 == Running the Server
 
-To simplify deployment and development, we'll package the server as an uber-jar and enable file logging (since stdio is reserved for the MCP protocol):
+To simplify deployment and development, we'll package the server as an uber-jar. This makes it possible to `mvn install` and publish as a jar to a Maven repository which makes it easiier to share and run for us and others.
 
 [source,properties]
 ----
 quarkus.package.uber-jar=true
+----
+
+Finally, we can optionally enable file logging as without it we would not be able to see any logs from the server as standard input/output is reserved for the MCP protocol.
+
+[source,properties]
+----
 quarkus.log.file.enable=true
 quarkus.log.file.path=weather-quarkus.log
 ----
@@ -199,7 +205,7 @@ image::claude-tools.png[Claude Tools Integration]
 
 [NOTE]
 ====
-You can also run the server directly withou using java - then it would be something like `java -jar <FULL PATH>/weather-1.0.0-SNAPSHOT-runner.jar`. We use JBang here because simpler if you want to share with someone who does not want to build the MCP server locally.
+You can also run the server directly without using java - then it would be something like `java -jar <FULL PATH>/weather-1.0.0-SNAPSHOT-runner.jar`. We use JBang here because simpler if you want to share with someone who does not want to build the MCP server locally.
 ====
 
 == Development Tools