From 6ae3949f3d193f976c6907e787895b1e25c45abb Mon Sep 17 00:00:00 2001 From: Eric Gustin Date: Mon, 5 Jan 2026 10:08:01 -0800 Subject: [PATCH 1/4] Document improved env file discovery --- .../mcp-server-quickstart/page.mdx | 10 ++--- .../tool-basics/build-mcp-server/page.mdx | 12 +++--- .../tool-basics/create-tool-secrets/page.mdx | 8 ++-- .../deployment-hosting/arcade-deploy/page.mdx | 2 +- .../references/mcp/python/settings/page.mdx | 40 +++++++++++++++++++ 5 files changed, 57 insertions(+), 15 deletions(-) diff --git a/app/en/get-started/quickstarts/mcp-server-quickstart/page.mdx b/app/en/get-started/quickstarts/mcp-server-quickstart/page.mdx index e7589c8d0..624284748 100644 --- a/app/en/get-started/quickstarts/mcp-server-quickstart/page.mdx +++ b/app/en/get-started/quickstarts/mcp-server-quickstart/page.mdx @@ -80,17 +80,17 @@ This generates a Python module with the following structure: ```bash my_server/ +├── .env.example ├── 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` +- **.env.example** Example `.env` file at the project root containing a secret required by one of the generated tools in `server.py`. Arcade automatically discovers `.env` files by traversing upward from the current directory. `server.py` includes proper structure with command-line argument handling. It creates an `MCPApp` with three sample tools: @@ -106,17 +106,17 @@ Secrets are sensitive strings like passwords, API keys, or other tokens that gra -You can create a `.env` file at the same directory as your entrypoint file (`server.py`) and add your secret: +You can create a `.env` file at your project root directory and add your secret: ```env filename=".env" MY_SECRET_KEY="my-secret-value" ``` -The generated project includes a `.env.example` file with the secret key name and example value. +The generated project includes a `.env.example` file at the project root with the secret key name and example value. You can rename it to `.env` to start using it. ```bash -mv .env.example .env +mv ../../.env.example ../../.env ``` diff --git a/app/en/guides/create-tools/tool-basics/build-mcp-server/page.mdx b/app/en/guides/create-tools/tool-basics/build-mcp-server/page.mdx index b02555388..981ab61a2 100644 --- a/app/en/guides/create-tools/tool-basics/build-mcp-server/page.mdx +++ b/app/en/guides/create-tools/tool-basics/build-mcp-server/page.mdx @@ -76,17 +76,17 @@ This generates a Python module with the following structure: ```bash my_server/ +├── .env.example ├── src/ │ └── my_server/ │ ├── __init__.py -│ ├── .env.example │ └── server.py └── pyproject.toml ``` 1. **server.py** Main server file with MCPApp and example tools. It creates an `MCPApp`, defines tools with `@app.tool`, and will start the server with `app.run()` when the file is executed directly. 1. **pyproject.toml** Dependencies and project configuration -1. **.env.example** Example `.env` file containing a secret required by one of the generated tools in `server.py`. Environments are loaded on server start, so **if you update the `.env` file, you will need to restart your server.** +1. **.env.example** Example `.env` file at the project root containing a secret required by one of the generated tools in `server.py`. Arcade automatically discovers `.env` files by traversing upward from the current directory, so placing it at the project root makes it accessible from any subdirectory. Environments are loaded on server start, so **if you update the `.env` file, you will need to restart your server.** ```python filename="server.py" showLineNumbers #!/usr/bin/env python3 @@ -171,17 +171,19 @@ Secrets are sensitive strings like passwords, API keys, or other tokens that gra -You can create a `.env` file at the same directory as your entrypoint file (`server.py`) and add your secret: +You can create a `.env` file at your project root directory and add your secret: ```env filename=".env" MY_SECRET_KEY="my-secret-value" ``` -The generated project includes a `.env.example` file with the secret key name and example value. +Arcade automatically discovers `.env` files by traversing upward from the current directory through parent directories. This means you can place your `.env` file at the project root (`my_server/`), and it will be found even when running your server from a subdirectory like `src/my_server/`. + +The generated project includes a `.env.example` file at the project root with the secret key name and example value. You can rename it to `.env` to start using it. ```bash -mv .env.example .env +mv ../../.env.example ../../.env ``` diff --git a/app/en/guides/create-tools/tool-basics/create-tool-secrets/page.mdx b/app/en/guides/create-tools/tool-basics/create-tool-secrets/page.mdx index 9d0bb4902..a18fa88aa 100644 --- a/app/en/guides/create-tools/tool-basics/create-tool-secrets/page.mdx +++ b/app/en/guides/create-tools/tool-basics/create-tool-secrets/page.mdx @@ -68,13 +68,13 @@ Depending on where you're running your server, you can store your secret in a fe -You can create a `.env` file in the same directory as your entrypoint file (typically `server.py` by default) and add your secret: +You can create a `.env` file in your project root directory 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 project includes a `.env.example` file at the project root with the secret key name and example value. You can rename it to `.env` to start using it. ```bash @@ -206,7 +206,7 @@ When your tool is executed, it will return: `"Got SECRET_KEY of length..."`. In ## Key Concepts - **Secure Access:** Secrets are accessed through context, not imported directly -- **Environment Integration:** Works with both environment variables and .env files +- **Environment Integration:** Works with both environment variables and `.env` files - **Error Handling:** Always handle the case where a secret might be missing - **Masking:** Never expose full secret values in logs or return values - **Declaration:** Use `requires_secrets` to make dependencies explicit @@ -221,7 +221,7 @@ SECRET_KEY="supersecret" -For the code to work, you must define your environment variables locally or in a `.env` file. +For the code to work, you must define your environment variables locally or in a `.env` file. Arcade will automatically search upward from the current directory to find your `.env` file. diff --git a/app/en/guides/deployment-hosting/arcade-deploy/page.mdx b/app/en/guides/deployment-hosting/arcade-deploy/page.mdx index c05e679f7..91fc5c3a7 100644 --- a/app/en/guides/deployment-hosting/arcade-deploy/page.mdx +++ b/app/en/guides/deployment-hosting/arcade-deploy/page.mdx @@ -105,7 +105,7 @@ Validating user is logged in... Validating pyproject.toml exists in current directory... ✓ pyproject.toml found at /path/to/your/project/pyproject.toml -Loading .env file from current directory if it exists... +Searching for .env file... ✓ Loaded environment from /path/to/your/project/.env Validating server is healthy and extracting metadata before deploying... diff --git a/app/en/references/mcp/python/settings/page.mdx b/app/en/references/mcp/python/settings/page.mdx index 2fc2f9266..30aece80d 100644 --- a/app/en/references/mcp/python/settings/page.mdx +++ b/app/en/references/mcp/python/settings/page.mdx @@ -7,6 +7,42 @@ description: Global configuration and environment-driven settings for the Arcade Global configuration and environment-driven settings. +## find_env_file() + +```python +arcade_mcp_server.settings.find_env_file( + start_dir: Path | None = None, + stop_at: Path | None = None, + filename: str = ".env" +) -> Path | None +``` + +Find a `.env` file by traversing upward through parent directories. + +Starts at the specified directory (or current working directory) and traverses upward through parent directories until a `.env` file is found or the filesystem root (or `stop_at` directory) is reached. + +**Parameters:** +- `start_dir` - Directory to start searching from. Defaults to current working directory. +- `stop_at` - Directory to stop traversal at (inclusive). If specified, the search will not continue past this directory. The `stop_at` directory itself is still checked for the `.env` file. +- `filename` - Name of the env file to find. Defaults to `.env`. + +**Returns:** Path to the `.env` file if found, `None` otherwise. + +**Example:** + +```python +from arcade_mcp_server.settings import find_env_file + +# Find .env starting from current directory +env_path = find_env_file() + +# Find .env starting from a specific directory +env_path = find_env_file(start_dir=Path("/path/to/project/src")) + +# Find .env but don't search above project root +env_path = find_env_file(stop_at=Path("/path/to/project")) +``` + ## MCPSettings ```python @@ -25,6 +61,10 @@ from_env() classmethod Create settings from environment variables. +Automatically discovers and loads a `.env` file by traversing upward from the current directory through parent directories until a `.env` file is found or the filesystem root is reached. + +The `.env` file is loaded with `override=False`, meaning existing environment variables take precedence. Multiple calls are safe. + ### to_dict() ```python From 07bbe3d9b92f16c0081323a1b74367e3ff87736b Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 26 Feb 2026 07:28:15 +0000 Subject: [PATCH 2/4] Regenerate clean markdown files --- .../quickstarts/mcp-server-quickstart.md | 12 ++++++------ .../create-tools/tool-basics/build-mcp-server.md | 14 ++++++++------ .../tool-basics/create-tool-secrets.md | 10 +++++----- .../en/guides/deployment-hosting/arcade-deploy.md | 4 ++-- 4 files changed, 21 insertions(+), 19 deletions(-) diff --git a/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md b/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md index 9f4308c80..1abcf707a 100644 --- a/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md +++ b/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md @@ -57,17 +57,17 @@ This generates a Python module with the following structure: ```bash my_server/ +├── .env.example ├── src/ │ └── my_server/ │ ├── __init__.py -│ ├── .env.example │ └── server.py └── pyproject.toml ``` - **server.py** with MCPApp and example - **pyproject.toml** Dependencies and configuration -- **.env.example** Example `.env` file containing a secret required by one of the generated in `server.py` +- **.env.example** Example `.env` file at the root containing a secret required by one of the generated in `server.py`. Arcade automatically discovers `.env` files by traversing upward from the current directory. `server.py` includes proper structure with command-line argument handling. It creates an `MCPApp` with three sample : @@ -83,17 +83,17 @@ Secrets are sensitive strings like passwords, , or other tokens that grant acces ### .env file -You can create a `.env` file at the same directory as your (`server.py`) and add your secret: +You can create a `.env` file at your root directory and add your secret: ```bash # .env MY_SECRET_KEY="my-secret-value" ``` -The generated includes a `.env.example` file with the secret key name and example value. You can rename it to `.env` to start using it. +The generated includes a `.env.example` file at the project root with the secret key name and example value. You can rename it to `.env` to start using it. ```bash -mv .env.example .env +mv ../../.env.example ../../.env ``` ### Environment Variable @@ -216,7 +216,7 @@ Ensure you have set the environment variable in your terminal or `.env` file, an - **Learn how to deploy your server**: [Deploy your MCP server](/guides/deployment-hosting/arcade-deploy.md) -Last updated on January 30, 2026 +Last updated on February 10, 2026 [Call tools in IDE/MCP clients](/en/get-started/quickstarts/call-tool-client.md) [Overview](/en/get-started/agent-frameworks.md) diff --git a/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md b/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md index 08b73ba24..562d184ca 100644 --- a/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md +++ b/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md @@ -56,17 +56,17 @@ This generates a Python module with the following structure: ```bash my_server/ +├── .env.example ├── src/ │ └── my_server/ │ ├── __init__.py -│ ├── .env.example │ └── server.py └── pyproject.toml ``` 1. **server.py** Main server file with MCPApp and example . It creates an `MCPApp`, defines tools with `@app.tool`, and will start the server with `app.run()` when the file is executed directly. 2. **pyproject.toml** Dependencies and configuration -3. **.env.example** Example `.env` file containing a secret required by one of the generated in `server.py`. Environments are loaded on server start, so **if you update the `.env` file, you will need to restart your server.** +3. **.env.example** Example `.env` file at the root containing a secret required by one of the generated in `server.py`. Arcade automatically discovers `.env` files by traversing upward from the current directory, so placing it at the project root makes it accessible from any subdirectory. Environments are loaded on server start, so **if you update the `.env` file, you will need to restart your server.** ```python # server.py @@ -152,17 +152,19 @@ Secrets are sensitive strings like passwords, , or other tokens that grant acces ### .env file -You can create a `.env` file at the same directory as your (`server.py`) and add your secret: +You can create a `.env` file at your root directory and add your secret: ```bash # .env MY_SECRET_KEY="my-secret-value" ``` -The generated includes a `.env.example` file with the secret key name and example value. You can rename it to `.env` to start using it. +Arcade automatically discovers `.env` files by traversing upward from the current directory through parent directories. This means you can place your `.env` file at the root (`my_server/`), and it will be found even when running your server from a subdirectory like `src/my_server/`. + +The generated includes a `.env.example` file at the project root with the secret key name and example value. You can rename it to `.env` to start using it. ```bash -mv .env.example .env +mv ../../.env.example ../../.env ``` ### Environment Variable @@ -272,7 +274,7 @@ That’s it! Your server is running and connected to your AI assistant. - **Deploy your server**: [Learn how to deploy your MCP server](/guides/deployment-hosting/arcade-deploy.md) -Last updated on January 30, 2026 +Last updated on February 10, 2026 [Compare MCP server types](/en/guides/create-tools/tool-basics/compare-server-types.md) [Create a tool with auth](/en/guides/create-tools/tool-basics/create-tool-auth.md) diff --git a/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md b/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md index cbd49272b..8f63bf4bf 100644 --- a/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md +++ b/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md @@ -62,14 +62,14 @@ Depending on where you’re running your server, you can store your secret in a ### .env file -You can create a `.env` file in the same directory as your (typically `server.py` by default) and add your secret: +You can create a `.env` file in your root directory and add your secret: ```bash # .env MY_SECRET_KEY="my-secret-value" ``` -The includes a `.env.example` file with the secret key name and example value. You can rename it to `.env` to start using it. +The includes a `.env.example` file at the project root with the secret key name and example value. You can rename it to `.env` to start using it. ```bash mv .env.example .env @@ -179,7 +179,7 @@ When your is executed, it will return: `"Got SECRET_KEY of length..."`. In a re ## Key Concepts - **Secure Access:** Secrets are accessed through , not imported directly -- **Environment Integration:** Works with both environment variables and .env files +- **Environment Integration:** Works with both environment variables and `.env` files - **Error Handling:** Always handle the case where a secret might be missing - **Masking:** Never expose full secret values in logs or return values - **Declaration:** Use `requires_secrets` to make dependencies explicit @@ -193,7 +193,7 @@ When your is executed, it will return: `"Got SECRET_KEY of length..."`. In a re SECRET_KEY="supersecret" ``` -For the code to work, you must define your environment variables locally or in a `.env` file. +For the code to work, you must define your environment variables locally or in a `.env` file. Arcade will automatically search upward from the current directory to find your `.env` file. ```python # secrets.py @@ -249,7 +249,7 @@ For HTTP transport, view your server’s API docs at [http://127.0.0.1:8000/docs For security reasons, Local HTTP servers do not currently support tool-level authorization and secrets. If you need to use tool-level authorization or secrets locally, you should use the stdio transport and configure the Arcade API key and secrets in your connection settings. Otherwise, if you intend to expose your HTTP to the public internet with \-level authorization and secrets, please follow the [deploying to the cloud with Arcade Deploy](/guides/deployment-hosting/arcade-deploy.md) guide or the [on-prem MCP server](/guides/deployment-hosting/on-prem.md) guide for secure remote deployment. -Last updated on January 30, 2026 +Last updated on February 10, 2026 [Create a tool with auth](/en/guides/create-tools/tool-basics/create-tool-auth.md) [Access runtime data](/en/guides/create-tools/tool-basics/runtime-data-access.md) diff --git a/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md b/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md index 267c591d1..f3e4e7b2d 100644 --- a/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md +++ b/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md @@ -85,7 +85,7 @@ Validating user is logged in... Validating pyproject.toml exists in current directory... ✓ pyproject.toml found at /path/to/your/project/pyproject.toml -Loading .env file from current directory if it exists... +Searching for .env file... ✓ Loaded environment from /path/to/your/project/.env Validating server is healthy and extracting metadata before deploying... @@ -143,7 +143,7 @@ You can use any of the available [Arcade clients](/references.md) to call the to Your Server is now deployed and managed by Arcade, and ready to be used in your MCP clients! -Last updated on January 30, 2026 +Last updated on February 10, 2026 [Configure Arcade's engine](/en/guides/deployment-hosting/configure-engine.md) [Overview](/en/guides/security.md) From fc830afc63d00dbbaaca5a8a80f10822dfd83932 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 26 Feb 2026 07:32:57 +0000 Subject: [PATCH 3/4] Regenerate clean markdown files --- .../en/get-started/quickstarts/mcp-server-quickstart.md | 2 +- .../en/guides/create-tools/tool-basics/build-mcp-server.md | 2 +- .../en/guides/create-tools/tool-basics/create-tool-secrets.md | 2 +- public/_markdown/en/guides/deployment-hosting/arcade-deploy.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md b/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md index 1abcf707a..bed4a2b07 100644 --- a/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md +++ b/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md @@ -216,7 +216,7 @@ Ensure you have set the environment variable in your terminal or `.env` file, an - **Learn how to deploy your server**: [Deploy your MCP server](/guides/deployment-hosting/arcade-deploy.md) -Last updated on February 10, 2026 +Last updated on January 30, 2026 [Call tools in IDE/MCP clients](/en/get-started/quickstarts/call-tool-client.md) [Overview](/en/get-started/agent-frameworks.md) diff --git a/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md b/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md index 562d184ca..522ca3b35 100644 --- a/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md +++ b/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md @@ -274,7 +274,7 @@ That’s it! Your server is running and connected to your AI assistant. - **Deploy your server**: [Learn how to deploy your MCP server](/guides/deployment-hosting/arcade-deploy.md) -Last updated on February 10, 2026 +Last updated on January 30, 2026 [Compare MCP server types](/en/guides/create-tools/tool-basics/compare-server-types.md) [Create a tool with auth](/en/guides/create-tools/tool-basics/create-tool-auth.md) diff --git a/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md b/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md index 8f63bf4bf..553af9d23 100644 --- a/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md +++ b/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md @@ -249,7 +249,7 @@ For HTTP transport, view your server’s API docs at [http://127.0.0.1:8000/docs For security reasons, Local HTTP servers do not currently support tool-level authorization and secrets. If you need to use tool-level authorization or secrets locally, you should use the stdio transport and configure the Arcade API key and secrets in your connection settings. Otherwise, if you intend to expose your HTTP to the public internet with \-level authorization and secrets, please follow the [deploying to the cloud with Arcade Deploy](/guides/deployment-hosting/arcade-deploy.md) guide or the [on-prem MCP server](/guides/deployment-hosting/on-prem.md) guide for secure remote deployment. -Last updated on February 10, 2026 +Last updated on January 30, 2026 [Create a tool with auth](/en/guides/create-tools/tool-basics/create-tool-auth.md) [Access runtime data](/en/guides/create-tools/tool-basics/runtime-data-access.md) diff --git a/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md b/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md index f3e4e7b2d..eb4e10a68 100644 --- a/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md +++ b/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md @@ -143,7 +143,7 @@ You can use any of the available [Arcade clients](/references.md) to call the to Your Server is now deployed and managed by Arcade, and ready to be used in your MCP clients! -Last updated on February 10, 2026 +Last updated on January 30, 2026 [Configure Arcade's engine](/en/guides/deployment-hosting/configure-engine.md) [Overview](/en/guides/security.md) From 9ac8846fe5501ccb650db543780da99cd0d22b83 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 26 Feb 2026 07:37:27 +0000 Subject: [PATCH 4/4] Regenerate clean markdown files --- .../en/get-started/quickstarts/mcp-server-quickstart.md | 2 +- .../en/guides/create-tools/tool-basics/build-mcp-server.md | 2 +- .../en/guides/create-tools/tool-basics/create-tool-secrets.md | 2 +- public/_markdown/en/guides/deployment-hosting/arcade-deploy.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md b/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md index bed4a2b07..c6620269d 100644 --- a/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md +++ b/public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md @@ -216,7 +216,7 @@ Ensure you have set the environment variable in your terminal or `.env` file, an - **Learn how to deploy your server**: [Deploy your MCP server](/guides/deployment-hosting/arcade-deploy.md) -Last updated on January 30, 2026 +Last updated on January 5, 2026 [Call tools in IDE/MCP clients](/en/get-started/quickstarts/call-tool-client.md) [Overview](/en/get-started/agent-frameworks.md) diff --git a/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md b/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md index 522ca3b35..e4bbaebb1 100644 --- a/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md +++ b/public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md @@ -274,7 +274,7 @@ That’s it! Your server is running and connected to your AI assistant. - **Deploy your server**: [Learn how to deploy your MCP server](/guides/deployment-hosting/arcade-deploy.md) -Last updated on January 30, 2026 +Last updated on January 5, 2026 [Compare MCP server types](/en/guides/create-tools/tool-basics/compare-server-types.md) [Create a tool with auth](/en/guides/create-tools/tool-basics/create-tool-auth.md) diff --git a/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md b/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md index 553af9d23..1ed876131 100644 --- a/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md +++ b/public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md @@ -249,7 +249,7 @@ For HTTP transport, view your server’s API docs at [http://127.0.0.1:8000/docs For security reasons, Local HTTP servers do not currently support tool-level authorization and secrets. If you need to use tool-level authorization or secrets locally, you should use the stdio transport and configure the Arcade API key and secrets in your connection settings. Otherwise, if you intend to expose your HTTP to the public internet with \-level authorization and secrets, please follow the [deploying to the cloud with Arcade Deploy](/guides/deployment-hosting/arcade-deploy.md) guide or the [on-prem MCP server](/guides/deployment-hosting/on-prem.md) guide for secure remote deployment. -Last updated on January 30, 2026 +Last updated on January 5, 2026 [Create a tool with auth](/en/guides/create-tools/tool-basics/create-tool-auth.md) [Access runtime data](/en/guides/create-tools/tool-basics/runtime-data-access.md) diff --git a/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md b/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md index eb4e10a68..00f125fc5 100644 --- a/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md +++ b/public/_markdown/en/guides/deployment-hosting/arcade-deploy.md @@ -143,7 +143,7 @@ You can use any of the available [Arcade clients](/references.md) to call the to Your Server is now deployed and managed by Arcade, and ready to be used in your MCP clients! -Last updated on January 30, 2026 +Last updated on January 5, 2026 [Configure Arcade's engine](/en/guides/deployment-hosting/configure-engine.md) [Overview](/en/guides/security.md)