Updates for arcade new generated template (#545)

Update docs

Author: EricGustin

app/en/home/build-tools/call-tools-from-mcp-clients/page.mdx

@@ -33,7 +33,7 @@ Configure your MCP clients to call tools from your MCP server.
 
 ## Using the `arcade configure` command
 
-For popular MCP clients, you can use the `arcade configure` command to configure your MCP client to call your MCP server. This will automatically add the MCP server to your client's configuration file. By default, it will use the stdio transport.
+For popular MCP clients, you can use the `arcade configure` command to configure your MCP client to call your MCP server. This will automatically add the MCP server to your client's configuration file. By default, it will use the stdio transport. You must run this command from the directory of your entrypoint file.
 
 <Tabs
   items={["Cursor IDE", "VS Code", "Claude Desktop"]}
@@ -91,15 +91,15 @@ Claude Desktop does not currently support the http transport.
 
 ### stdio specific configuration
 
-If you are using the stdio transport, `arcade configure` will assume the entrypoint (the script that contains the `MCPApp` instance and calls `app.run()`) to your MCP server is `server.py` and will set the working directory to the root of your project. You can override this with the `--entrypoint` (or `-e`) option:
+If you are using the stdio transport, `arcade configure` will assume the entrypoint (the script that contains the `MCPApp` instance and calls `app.run()`) to your MCP server is `server.py` and will set the working directory to the path of your entrypoint file. You can override this with the `--entrypoint` (or `-e`) option:
 
 <Callout type="info">
   Note that the `--entrypoint` determines only the filename of the entrypoint
   script, not the path to the script.
 </Callout>
 <Callout type="info">
   When using the stdio transport, `arcade configure` will automatically load the
-  secrets from the `.env` file in the root of your project into the appropriate
+  secrets from the `.env` file at the directory of your entrypoint file into the appropriate
   configuration file for your MCP client.
 </Callout>
 
@@ -170,14 +170,14 @@ If you are using the streamable HTTP transport, `arcade configure` will assume t
   </Tabs.Tab>
   <Tabs.Tab>
 
-Claude Desktop does not currently support the http transport.
+Claude Desktop does not currently support the http transport via JSON configuration files.
 
   </Tabs.Tab>
 </Tabs>
 
 ### Other configuration options
 
-If you have modified the default configuration of your MCP client, you can pass the `--config` (or `-c`) option to `arcade configure` to use your custom configuration file:
+If you have modified the default configuration of your MCP client, or want to use a profile/workspace specific configuration file, then you can pass the `--config` (or `-c`) option to `arcade configure` to use your custom configuration file:
 
 <Tabs
   items={["Cursor IDE", "VS Code", "Claude Desktop"]}
@@ -250,7 +250,7 @@ When configuring your MCP client using the stdio transport, you need to ensure t
 
 - Your virtual environment is located at `/path/to/your/project/.venv`
 - Your project is located at `/path/to/your/project`
-- The entrypoint to your MCP server is `server.py`
+- The entrypoint to your MCP server is located at `/path/to/your/server.py`
 - One of your tools requires the `MY_SECRET_KEY` environment variable to be set.
 - Your secrets are stored in the `/path/to/your/project/.env` file
 
@@ -279,15 +279,15 @@ When configuring your MCP client using the Streamable HTTP transport, ensure the
 
 - Your virtual environment is located at `/path/to/your/project/.venv`
 - Your MCP server is located at `/path/to/your/project/server.py`
-- Your secrets are stored in the `.env` file
+- Your secrets are stored in the `/path/to/your/project/.env` file
 
 Activate the virtual environment:
 
 ```bash
 source /path/to/your/project/.venv/bin/activate
 ```
 
-run the MCP server using the http transport. The secrets will be loaded from the `.env` file:
+run the MCP server using the http transport. The secrets will be loaded from the `.env` file that is located at the directory of your entrypoint file:
 
 ```bash
 uv run server.py http

app/en/home/build-tools/create-a-mcp-server/page.mdx

@@ -7,7 +7,7 @@ import { Steps, Tabs, Callout } from "nextra/components";
 
 # Creating an MCP Server with Arcade
 
-The `arcade_mcp_server` package provides powerful ways to run MCP servers with your Arcade tools. This guide walks you through the complete process of creating a custom MCP server with Arcade.
+The `arcade_mcp_server` package provides powerful ways to build and run MCP servers with your Arcade tools. This guide walks you through the complete process of creating a custom MCP server with Arcade.
 
 <GuideOverview>
 <GuideOverview.Outcomes>
@@ -49,15 +49,25 @@ In your terminal, run the following command to scaffold a new MCP Server called
 
 ```bash
 arcade new my_server
-cd my_server
+cd my_server/src/my_server
 ```
 
 <Callout type="info">
   If you aren't already logged into your Arcade account, you will be prompted to
   do so by running `arcade login` in your terminal.
 </Callout>
 
-This generates a complete project with:
+This generates a Python module with the following structure:
+
+```bash
+my_server/
+├── src/
+│   └── my_server/
+│       ├── __init__.py
+│       ├── .env.example
+│       └── server.py
+└── pyproject.toml
+```
 
 - **server.py** Main server file with MCPApp and example tools
 - **pyproject.toml** Dependencies and project configuration

app/en/home/build-tools/organize-mcp-server-tools/page.mdx

@@ -33,18 +33,21 @@ Learn best practices for organizing your MCP server and tools, how to import too
 
 ## Project Structure
 
-We recommend keeping your MCP server file at the root of your project and keeping your tools in separate files in a `tools` directory like so:
+We recommend keeping your MCP server file and tools in separate files in a `tools` directory like so:
 
 ```bash
     my_server/
-    ├── .env
-    ├── server.py          # Main MCPApp
-    ├── tools/
-    │   ├── __init__.py
-    │   ├── math_tools.py  # @tool decorated functions
-    │   └── text_tools.py  # @tool decorated functions
-    ├── pyproject.toml
-    └── README.md
+    ├── src/
+    │   └── my_server/
+    │       ├── .env
+    │       ├── server.py          # Entrypoint file with your MCPApp
+    │       ├── tools/
+    │       │   ├── __init__.py
+    │       │   ├── math_tools.py  # @tool decorated functions
+    │       │   └── text_tools.py  # @tool decorated functions
+    │       ├── pyproject.toml
+    │       └── README.md
+    └── pyproject.toml
 ```
 
 ## Defining tools
@@ -74,23 +77,30 @@ from tools.math_tools import add, multiply
 from tools.text_tools import capitalize_string, word_count
 ```
 
-You could also import from Arcade PyPI packages:
+You could also import specific tools from Arcade PyPI packages:
 
 ```python filename="server.py"
 from arcade_gmail.tools import list_emails
 ```
 
-Add imported tools explicitly to the MCP server app object like this:
+You can also import whole modules that contain tools like this:
+
+```python filename="server.py"
+import arcade_reddit
+```
+
+Add imported tools explicitly to the `MCPApp` instance like this:
 
 ```python filename="server.py"
 app.add_tool(add)
 app.add_tool(list_emails)
+app.add_tools_from_module(arcade_reddit)
 ```
 
 ## Key takeaways
 
 - Keep your MCP server file clean and readable by defining tools in separate files
-- Store your tools in a `tools` directory in your project root alongside your MCP server file
+- Store your tools in a `tools` directory in your project alongside your MCP server file
 - You can import tools from other Arcade packages and your own files
 - Add imported tools explicitly to the MCP server app object
 

app/en/home/build-tools/tool-context/page.mdx

@@ -18,15 +18,15 @@ import { Callout, Tabs } from "nextra/components";
 <Callout type="notice">
 
 Some authorization providers may also include additional structured user
-information in the `ToolContext`.
+information in the `Context`. You can access this information via `context.authorization.user_info`.
 
 </Callout>
 
 ## How `Context` Works
 
-When you invoke a tool that requires authorization, Arcade's Tool SDK automatically:
+When a tool that requires authorization is invoked, the MCP server automatically:
 
-1. Creates a `Context` object
+1. Creates an instance of `Context`
 2. Passes this object to your tool
 
 You can then use the `Context` object to make authenticated requests to external APIs.
@@ -48,6 +48,7 @@ await context.log.debug("Debug message")
 await context.log.info("Information message")
 await context.log.warning("Warning message")
 await context.log.error("Error message")
+await context.log.log("info", "Info message") # equivalent to await context.log.info("Info message")
 ```
 
 ### Secrets Management
@@ -88,7 +89,7 @@ async def my_tool(context: Context, ...):
 
 ## Example Code
 
-The following is an example shows how tools can access runtime features through
+The following is an example that shows how tools can access runtime features through
 `Context`, including logging, secrets, and progress reporting.
 
 ### Environment Variables
@@ -100,7 +101,7 @@ DATABASE_URL="postgresql://localhost/mydb"
 
 <Callout type="warning">
 
-For the code to work, you must define your environment variables in a `.env` file.
+For the code to work, you must define your environment variables in a `.env` file at the same directory as your entrypoint file.
 
 </Callout>
 

app/en/home/custom-mcp-server-quickstart/page.mdx

@@ -62,12 +62,22 @@ In your terminal, run the following command to scaffold a new MCP Server called
 
 ```bash
 arcade new my_server
-cd my_server
+cd my_server/src/my_server
 ```
 
-This generates a complete project with:
+This generates a Python module with the following structure:
 
-- **server.py** Main server file with MCPApp and example tools
+```bash
+my_server/
+├── src/
+│   └── my_server/
+│       ├── __init__.py
+│       ├── .env.example
+│       └── server.py
+└── pyproject.toml
+```
+
+- **server.py** Entrypoint file with MCPApp and example tools
 - **pyproject.toml** Dependencies and project configuration
 - **.env.example** Example `.env` file containing a secret required by one of the generated tools in `server.py`
 
@@ -85,13 +95,13 @@ Secrets are sensitive strings like passwords, api-keys, or other tokens that gra
 
 <Tabs items={["Environment Variable", "Terminal"]}>
 <Tabs.Tab>
-You can create a `.env` file in the root of your project and add your secret:
+You can create a `.env` file at the same directory as your entrypoint file and add your secret:
 
 ```env filename=".env"
 MY_SECRET_KEY="my-secret-value"
 ```
 
-The project includes a `.env.example` file with the secret key name and example value.
+The generated project includes a `.env.example` file with the secret key name and example value.
 You can rename it to `.env` to start using it.
 
 ```bash

app/en/home/deployment/on-prem-mcp/page.mdx

@@ -92,8 +92,8 @@ ARCADE_USER_ID=<your-user-id>
 Start your MCP server with HTTP transport:
 
 ```bash
-# Navigate to your server directory
-cd my_server
+# Navigate to your entrypoint file
+cd my_server/src/my_server
 
 # Run with HTTP transport (default)
 uv run server.py

app/en/references/mcp/python/sharing/page.mdx

@@ -21,8 +21,8 @@ By default, your MCP server runs locally on `localhost:8000`. To share it:
 First, start your MCP server with HTTP transport:
 
 ```bash
-# Navigate to your server directory
-cd my_server
+# Navigate to your entrypoint file
+cd my_server/src/my_server
 
 # Run with HTTP transport (default)
 uv run server.py

app/en/references/mcp/python/transports/page.mdx

@@ -95,7 +95,7 @@ app.run(transport="http", host="0.0.0.0", port=8080)
 
 When running in HTTP mode, the server provides:
 
-- `GET /health` - Health check endpoint
+- `GET /worker/health` - Health check endpoint
 - `GET /mcp` - SSE endpoint for MCP protocol
 - `GET /docs` - Swagger UI documentation (debug mode)
 - `GET /redoc` - ReDoc documentation (debug mode)