Update gendocs to add toolsmetadata and exclusion list (#819)

* feat: add exclusion list file reader utility

Made-with: Cursor

* feat: add utility to remove excluded toolkit output files

Made-with: Cursor

* chore: export exclusion list utilities from utils index

Made-with: Cursor

* feat: add --exclude-file option to generate command

Made-with: Cursor

* feat: add --exclude-file option to generate-all command

Made-with: Cursor

* docs: document --exclude-file option in README

Made-with: Cursor

* style: fix passive voice in README exclusion section

Made-with: Cursor

* Update docs gent to have toolkit metdata in json and exclusion list

* Merge branch 'main' into francisco/update-gendocs-to-add-toolsmetadata

* Regenerate clean markdown files

* chore: add .worktrees to gitignore

Made-with: Cursor

* adding ignore list logic

* Regenerate clean markdown files

* test: add failing CLI flow regression tests

Made-with: Cursor

* fix: add tested CLI flow helpers for skip and provider filtering

Made-with: Cursor

* fix: make excluded output cleanup resilient to missing directories

Made-with: Cursor

* fix: run exclusion cleanup when skip-unchanged finds no changes

Made-with: Cursor

* fix: compute toProcess from effective skip intersection

Made-with: Cursor

* fix: apply skip and ignore filters in providers mode

Made-with: Cursor

* fix: make ProviderEntry.version compatible with exactOptionalPropertyTypes

Made-with: Cursor

* Regenerate clean markdown files

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Author: jottakka

.github/workflows/generate-toolkit-docs.yml

@@ -59,6 +59,8 @@ jobs:
             --llm-api-key "$OPENAI_API_KEY" \
             --toolkit-concurrency 8 \
             --llm-concurrency 15 \
+            --exclude-file ./excluded-toolkits.txt \
+            --ignore-file ./ignored-toolkits.txt \
             --output data/toolkits
         working-directory: toolkit-docs-generator
         env:

.gitignore

@@ -28,3 +28,6 @@ toolkit-docs-generator-verification/logs/
 
 # Generated toolkit markdown (built at build time, not committed)
 public/toolkit-markdown/
+
+# Git worktrees
+.worktrees/

app/_components/toolkit-docs/types/index.ts

@@ -181,6 +181,28 @@ export type ToolCodeExample = {
   tabLabel?: string;
 };
 
+// ============================================================================
+// Tool Metadata Types
+// ============================================================================
+
+export type ToolMetadataClassification = {
+  serviceDomains: string[];
+};
+
+export type ToolMetadataBehavior = {
+  operations: string[];
+  readOnly?: boolean;
+  destructive?: boolean;
+  idempotent?: boolean;
+  openWorld?: boolean;
+};
+
+export type ToolMetadata = {
+  classification: ToolMetadataClassification;
+  behavior: ToolMetadataBehavior;
+  extras?: Record<string, unknown> | null;
+};
+
 // ============================================================================
 // Tool Definition Types
 // ============================================================================
@@ -207,6 +229,8 @@ export type ToolDefinition = {
   secretsInfo?: ToolSecret[];
   /** Tool output schema */
   output: ToolOutput | null;
+  /** Per-tool metadata from Engine API */
+  metadata?: ToolMetadata | null;
   /** Custom documentation chunks for this tool */
   documentationChunks: DocumentationChunk[];
   /** Generated code example configuration */

app/en/get-started/quickstarts/mcp-server-quickstart/page.mdx

@@ -115,18 +115,44 @@ MY_SECRET_KEY="my-secret-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.
 
+<Tabs items={["Bash/Zsh (macOS/Linux)", "PowerShell (Windows)"]}>
+<Tabs.Tab>
+
 ```bash
 mv ../../.env.example ../../.env
 ```
 
+</Tabs.Tab>
+<Tabs.Tab>
+
+```powershell
+Copy-Item .env.example .env
+```
+
+</Tabs.Tab>
+</Tabs>
+
 </Tabs.Tab>
 <Tabs.Tab>
 You can set the environment variable in your terminal directly with this command:
 
+<Tabs items={["Bash/Zsh (macOS/Linux)", "PowerShell (Windows)"]}>
+<Tabs.Tab>
+
 ```bash
 export MY_SECRET_KEY="my-secret-value"
 ```
 
+</Tabs.Tab>
+<Tabs.Tab>
+
+```powershell
+$env:MY_SECRET_KEY="my-secret-value"
+```
+
+</Tabs.Tab>
+</Tabs>
+
 </Tabs.Tab>
 </Tabs>
 

app/en/guides/create-tools/tool-basics/build-mcp-server/page.mdx

@@ -182,18 +182,44 @@ Arcade automatically discovers `.env` files by traversing upward from the curren
 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.
 
+<Tabs items={["Bash/Zsh (macOS/Linux)", "PowerShell (Windows)"]}>
+<Tabs.Tab>
+
 ```bash
 mv ../../.env.example ../../.env
 ```
 
+</Tabs.Tab>
+<Tabs.Tab>
+
+```powershell
+Copy-Item .env.example .env
+```
+
+</Tabs.Tab>
+</Tabs>
+
 </Tabs.Tab>
 <Tabs.Tab>
 You can set the environment variable in your terminal directly with this command:
 
+<Tabs items={["Bash/Zsh (macOS/Linux)", "PowerShell (Windows)"]}>
+<Tabs.Tab>
+
 ```bash
 export MY_SECRET_KEY="my-secret-value"
 ```
 
+</Tabs.Tab>
+<Tabs.Tab>
+
+```powershell
+$env:MY_SECRET_KEY="my-secret-value"
+```
+
+</Tabs.Tab>
+</Tabs>
+
 </Tabs.Tab>
 </Tabs>
 

app/en/guides/create-tools/tool-basics/create-tool-secrets/page.mdx

@@ -77,10 +77,23 @@ MY_SECRET_KEY="my-secret-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.
 
+<Tabs items={["Bash/Zsh (macOS/Linux)", "PowerShell (Windows)"]}>
+<Tabs.Tab>
+
 ```bash
 mv .env.example .env
 ```
 
+</Tabs.Tab>
+<Tabs.Tab>
+
+```powershell
+Copy-Item .env.example .env
+```
+
+</Tabs.Tab>
+</Tabs>
+
 <Callout type="info">
   Using a `.env` file is okay for local development, but you should use
   the Arcade Dashboard or Arcade CLI for production deployments.
@@ -117,10 +130,23 @@ arcade secret set MY_SECRET_KEY="my-secret-value"
 <Tabs.Tab>
 You can set the environment variable in your terminal directly with this command:
 
+<Tabs items={["Bash/Zsh (macOS/Linux)", "PowerShell (Windows)"]}>
+<Tabs.Tab>
+
 ```bash
 export MY_SECRET_KEY="my-secret-value"
 ```
 
+</Tabs.Tab>
+<Tabs.Tab>
+
+```powershell
+$env:MY_SECRET_KEY="my-secret-value"
+```
+
+</Tabs.Tab>
+</Tabs>
+
 <Callout type="info">
   Using environment variables is okay for local development, but you should use
   the Arcade Dashboard or Arcade CLI for production deployments.

public/_markdown/en/get-started/quickstarts/mcp-server-quickstart.md

@@ -92,18 +92,34 @@ MY_SECRET_KEY="my-secret-value"
 
 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/Zsh (macOS/Linux)
+
 ```bash
 mv ../../.env.example ../../.env
 ```
 
+### PowerShell (Windows)
+
+```bash
+Copy-Item .env.example .env
+```
+
 ### Environment Variable
 
 You can set the environment variable in your terminal directly with this command:
 
+### Bash/Zsh (macOS/Linux)
+
 ```bash
 export MY_SECRET_KEY="my-secret-value"
 ```
 
+### PowerShell (Windows)
+
+```bash
+$env:MY_SECRET_KEY="my-secret-value"
+```
+
 ## Connect to Arcade to unlock authorized tool calling
 
 Since the Reddit tool accesses information only available to your Reddit , you’ll need to authorize it. For this, you’ll need to create an Arcade account and connect from the terminal, run:
@@ -216,7 +232,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 5, 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)

public/_markdown/en/guides/create-tools/tool-basics/build-mcp-server.md

@@ -163,18 +163,34 @@ Arcade automatically discovers `.env` files by traversing upward from the curren
 
 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/Zsh (macOS/Linux)
+
 ```bash
 mv ../../.env.example ../../.env
 ```
 
+### PowerShell (Windows)
+
+```bash
+Copy-Item .env.example .env
+```
+
 ### Environment Variable
 
 You can set the environment variable in your terminal directly with this command:
 
+### Bash/Zsh (macOS/Linux)
+
 ```bash
 export MY_SECRET_KEY="my-secret-value"
 ```
 
+### PowerShell (Windows)
+
+```bash
+$env:MY_SECRET_KEY="my-secret-value"
+```
+
 ## Connect to Arcade to unlock authorized tool calling
 
 Since the Reddit tool accesses information only available to your Reddit , you’ll need to authorize it. For this, you’ll need to create an Arcade account and connect to it from the terminal, run:
@@ -274,7 +290,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 5, 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)

public/_markdown/en/guides/create-tools/tool-basics/create-tool-secrets.md

@@ -71,10 +71,18 @@ MY_SECRET_KEY="my-secret-value"
 
 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/Zsh (macOS/Linux)
+
 ```bash
 mv .env.example .env
 ```
 
+### PowerShell (Windows)
+
+```bash
+Copy-Item .env.example .env
+```
+
 Using a `.env` file is okay for local development, but you should use the Arcade Dashboard or Arcade CLI for production deployments.
 
 ### Arcade Dashboard
@@ -104,10 +112,18 @@ The Arcade CLI will make the secret available to your  server when it is deploye
 
 You can set the environment variable in your terminal directly with this command:
 
+### Bash/Zsh (macOS/Linux)
+
 ```bash
 export MY_SECRET_KEY="my-secret-value"
 ```
 
+### PowerShell (Windows)
+
+```bash
+$env:MY_SECRET_KEY="my-secret-value"
+```
+
 Using environment variables is okay for local development, but you should use the Arcade Dashboard or Arcade CLI for production deployments.
 
 ### Using secrets with stdio transport
@@ -249,7 +265,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 5, 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)

public/_markdown/en/references/mcp/telemetry.md

@@ -1,5 +1,5 @@
 ---
-title: "Arcade MCP Telemtry"
+title: "Arcade MCP Telemetry"
 description: "Learn about what data we track when using arcade-mcp"
 ---
 [Arcade MCP](/en/references/mcp/python.md)