[AUTO] Adding MCP Servers docs update

Author: jottakka

public/llms.txt

@@ -149,8 +149,15 @@
       "description": "Check the health status of the Arcade Engine.\n\nUse this tool to verify if the Arcade Engine service is currently healthy and operational.",
       "parameters": [],
       "auth": null,
-      "secrets": [],
-      "secretsInfo": [],
+      "secrets": [
+        "ARCADE_API_KEY"
+      ],
+      "secretsInfo": [
+        {
+          "name": "ARCADE_API_KEY",
+          "type": "api_key"
+        }
+      ],
       "output": {
         "type": "json",
         "description": "Response from the API endpoint 'arcade-health'."
@@ -838,8 +845,15 @@
       "description": "Get the OpenAPI 3.0 specification in JSON format.\n\nUse this tool to retrieve the OpenAPI 3.0 specification for the Arcade Engine API, which provides detailed information about all available endpoints and their usage.",
       "parameters": [],
       "auth": null,
-      "secrets": [],
-      "secretsInfo": [],
+      "secrets": [
+        "ARCADE_API_KEY"
+      ],
+      "secretsInfo": [
+        {
+          "name": "ARCADE_API_KEY",
+          "type": "api_key"
+        }
+      ],
       "output": {
         "type": "json",
         "description": "Response from the API endpoint 'openapi' (returns OpenAPI 3.0 specification)."
@@ -1921,6 +1935,6 @@
   ],
   "subPages": [],
   "curationSourceHash": "b2095649876875b317d044eab589628ca462ac0d06f5251a5358db36c0360d0b",
-  "generatedAt": "2026-09-04T15:27:40.200Z",
-  "summary": "## Arcade Engine API Toolkit\n\nThis toolkit gives LLMs direct programmatic access to the Arcade Engine API, enabling agents to manage tools, workers, auth providers, secrets, projects, and tool executions without leaving the agent loop.\n\n## Capabilities\n\n- **Tool discovery & execution** — list, inspect, and retrieve specifications for tools across the engine; execute any tool by name with schema-aware argument construction; page through execution history with filtering by tool, toolkit, user, outcome, and time range; fetch full execution records including inputs/outputs (admin-audited).\n- **Worker lifecycle management** — create, retrieve, list, health-check, test connections for, authorize, and delete workers.\n- **Auth provider & user connection management** — list, retrieve, and delete auth providers; manage user/auth-provider connections; authorize users for specific tools; check and monitor authorization status.\n- **Project & MCP endpoint operations** — list accessible projects, retrieve project details, delete MCP (Streamable HTTP) endpoint configurations.\n- **Secrets & session management** — delete secrets by ID; update session verification settings for users or entities.\n- **Engine health & API introspection** — check engine health status; retrieve the full OpenAPI 3.0 specification for the Engine API.\n\n## Secrets\n\n`ARCADE_API_KEY` — Your Arcade API key, used to authenticate all requests made by this toolkit to the Arcade Engine. To obtain it, log in to the [Arcade dashboard](https://api.arcade.dev/dashboard/auth/secrets), navigate to the **API Keys** section, and generate or copy an existing key. This key must have sufficient permissions for the Engine API operations you intend to perform (full engine access is typically associated with an admin-level key for the relevant project).\n\nFor details on configuring secrets in Arcade, see the [tool secrets guide](https://docs.arcade.dev/en/guides/create-tools/tool-basics/create-tool-secrets). You can also manage secrets directly at [https://api.arcade.dev/dashboard/auth/secrets](https://api.arcade.dev/dashboard/auth/secrets)."
+  "generatedAt": "2026-09-22T11:14:14.860Z",
+  "summary": "## Arcade Engine API Toolkit\n\nProvides LLMs with direct programmatic access to the Arcade Engine API, enabling autonomous management of tools, workers, auth providers, secrets, projects, and tool executions.\n\n## Capabilities\n\n- **Tool discovery & execution**: List, inspect specifications for, and execute any tool registered in the engine; retrieve paginated tool lists filtered by toolkit; fetch OpenAPI and formatted specs.\n- **Worker lifecycle management**: Create, retrieve, list, test, authorize, monitor health of, and delete workers in the engine's worker pool.\n- **Auth provider & user connection management**: List, inspect, and delete auth providers; authorize users for specific tools; check ongoing auth status; manage and delete user/provider connections; update session verification settings.\n- **Secret management**: Delete secrets by ID via the API (secrets are configured separately — see Secrets section below).\n- **Tool execution history**: Page through execution records for a project with filtering by tool, toolkit, user, outcome, and time range; retrieve full detail for individual runs including optional inputs/outputs (requires project admin authority, is audited).\n- **Engine & project operations**: Check engine health, retrieve the OpenAPI 3.0 spec, list accessible projects, and fetch project details.\n\n## Secrets\n\n`ARCADE_API_KEY` — Your Arcade API key, used to authenticate all requests this toolkit makes to the Arcade Engine API. Obtain it from the [Arcade dashboard](https://api.arcade.dev/dashboard/auth/secrets) under **API Keys**. No external provider account is needed; the key is issued directly by Arcade and scoped to your Arcade account.\n\nFor guidance on configuring secrets in Arcade tools, see the [Arcade secrets documentation](https://docs.arcade.dev/en/guides/create-tools/tool-basics/create-tool-secrets). You can also manage secrets directly at https://api.arcade.dev/dashboard/auth/secrets."
 }