From 2d093a2f838f7499ed5f87687c7e52c14293c299 Mon Sep 17 00:00:00 2001
From: Teal Larson <teal@arcade.dev>
Date: Wed, 29 Apr 2026 10:58:36 -0400
Subject: [PATCH 1/2] fix: resolve Ahrefs SEO audit issues (D-1 through D-3)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- D-1: Add 163 locale-less sibling redirect rules to next.config.ts so
  locale-less inbound URLs (e.g. /home/auth/X) resolve in one hop instead
  of two (middleware locale-detection + path-restructure rule)
- D-2: Rewrite internal MDX links to include /en/ locale prefix across
  111 pages, eliminating 3,700+ redirect hits Ahrefs attributed to docs
- D-3: Fix 383 broken-link rows — remove clickable Resources breadcrumb
  in toolkit pages (href="/en/resources" was 404), add redirect rules for
  13 removed/renamed pages (squareup→square, home/*, toolkit pages)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .../toolkit-docs/components/toolkit-page.tsx  |   4 +-
 app/en/get-started/about-arcade/page.mdx      |   6 +-
 .../ag2/use-arcade-tools/page.mdx             |   2 +-
 .../crewai/use-arcade-tools/page.mdx          |   2 +-
 .../google-adk/overview/page.mdx              |   4 +-
 .../google-adk/setup-python/page.mdx          |   2 +-
 .../google-adk/setup-typescript/page.mdx      |   4 +-
 .../langchain/auth-langchain-tools/page.mdx   |   2 +-
 .../langchain/overview/page.mdx               |   8 +-
 .../agent-frameworks/mastra/page.mdx          |  10 +-
 .../openai-agents/overview/page.mdx           |   6 +-
 .../openai-agents/setup-python/page.mdx       |   2 +-
 .../openai-agents/setup-typescript/page.mdx   |   6 +-
 .../page.mdx                                  |   8 +-
 .../agent-frameworks/springai/page.mdx        |   4 +-
 .../agent-frameworks/tanstack-ai/page.mdx     |   6 +-
 .../agent-frameworks/vercelai/page.mdx        |   6 +-
 .../mcp-clients/claude-code/page.mdx          |   4 +-
 .../mcp-clients/claude-desktop/page.mdx       |   4 +-
 .../mcp-clients/copilot-studio/page.mdx       |   4 +-
 .../get-started/mcp-clients/cursor/page.mdx   |   4 +-
 app/en/get-started/mcp-clients/page.mdx       |   2 +-
 .../mcp-clients/visual-studio-code/page.mdx   |   2 +-
 .../quickstarts/call-tool-agent/page.mdx      |   4 +-
 .../quickstarts/call-tool-client/page.mdx     |   8 +-
 .../mcp-server-quickstart/page.mdx            |  16 +-
 app/en/get-started/setup/api-keys/page.mdx    |   4 +-
 .../setup/connect-arcade-docs/page.mdx        |   6 +-
 .../setup/windows-environment/page.mdx        |   6 +-
 app/en/guides/audit-logs/page.mdx             |   2 +-
 .../contextual-access/build-your-own/page.mdx |  10 +-
 .../contextual-access/examples/page.mdx       |   6 +-
 .../contextual-access/how-hooks-work/page.mdx |   6 +-
 app/en/guides/contextual-access/page.mdx      |  10 +-
 .../useful-tool-errors/page.mdx               |   4 +-
 .../evaluate-tools/capture-mode/page.mdx      |   6 +-
 .../comparative-evaluations/page.mdx          |   8 +-
 .../create-evaluation-suite/page.mdx          |  10 +-
 .../evaluate-tools/run-evaluations/page.mdx   |   6 +-
 .../evaluate-tools/why-evaluate/page.mdx      |  14 +-
 .../improve/types-of-tools/page.mdx           |   4 +-
 .../create-tools/migrate-toolkits/page.mdx    |   6 +-
 .../create-tools/secure-your-server/page.mdx  |   4 +-
 .../secure-your-mcp-server/page.mdx           |  10 +-
 .../tool-basics/add-tool-metadata/page.mdx    |   8 +-
 .../tool-basics/build-mcp-server/page.mdx     |  18 +-
 .../tool-basics/call-tools-mcp/page.mdx       |   6 +-
 .../tool-basics/compare-server-types/page.mdx |   8 +-
 .../tool-basics/create-tool-auth/page.mdx     |  10 +-
 .../tool-basics/create-tool-secrets/page.mdx  |  12 +-
 .../tool-basics/organize-mcp-tools/page.mdx   |   2 +-
 .../tool-basics/runtime-data-access/page.mdx  |   4 +-
 .../deployment-hosting/arcade-cloud/page.mdx  |   8 +-
 .../deployment-hosting/arcade-deploy/page.mdx |  10 +-
 .../configure-engine/page.mdx                 |  20 +-
 .../deployment-hosting/on-prem/page.mdx       |  16 +-
 app/en/guides/deployment-hosting/page.mdx     |   6 +-
 .../logic-extensions/build-your-own/page.mdx  |  10 +-
 .../mcp-gateways/add-remote-servers/page.mdx  |   4 +-
 .../mcp-gateways/create-via-ai/page.mdx       |   6 +-
 .../create-via-dashboard/page.mdx             |   2 +-
 app/en/guides/mcp-gateways/page.mdx           |  12 +-
 .../call-third-party-apis/page.mdx            |   6 +-
 .../custom-apps/auth-tool-calling/page.mdx    |   4 +-
 .../tool-calling/error-handling/page.mdx      |   2 +-
 app/en/guides/tool-calling/page.mdx           |  14 +-
 .../secure-auth-production/page.mdx           |   2 +-
 .../server-level-vs-tool-level-auth/page.mdx  |  10 +-
 app/en/references/arcade-cli/page.mdx         |   4 +-
 .../auth-providers/airtable/page.mdx          |  16 +-
 .../references/auth-providers/asana/page.mdx  |  20 +-
 .../auth-providers/atlassian/page.mdx         |   8 +-
 .../references/auth-providers/attio/page.mdx  |  20 +-
 .../auth-providers/calendly/page.mdx          |  16 +-
 .../auth-providers/clickup/page.mdx           |   8 +-
 .../auth-providers/discord/page.mdx           |   8 +-
 .../auth-providers/dropbox/page.mdx           |   8 +-
 .../references/auth-providers/figma/page.mdx  |  18 +-
 .../references/auth-providers/github/page.mdx |  16 +-
 .../references/auth-providers/google/page.mdx |  14 +-
 .../auth-providers/hubspot/page.mdx           |  18 +-
 .../references/auth-providers/linear/page.mdx |  14 +-
 .../auth-providers/linkedin/page.mdx          |   6 +-
 .../auth-providers/mailchimp/page.mdx         |  16 +-
 .../auth-providers/microsoft/page.mdx         |  12 +-
 .../references/auth-providers/miro/page.mdx   |  16 +-
 .../references/auth-providers/notion/page.mdx |  10 +-
 .../references/auth-providers/oauth2/page.mdx |  16 +-
 app/en/references/auth-providers/page.mdx     |   6 +-
 .../auth-providers/pagerduty/page.mdx         |  16 +-
 .../references/auth-providers/reddit/page.mdx |   8 +-
 .../auth-providers/salesforce/page.mdx        |  24 +-
 .../references/auth-providers/slack/page.mdx  |  18 +-
 .../auth-providers/spotify/page.mdx           |   8 +-
 .../references/auth-providers/square/page.mdx |  16 +-
 .../auth-providers/ticktick/page.mdx          |  16 +-
 .../references/auth-providers/twitch/page.mdx |   8 +-
 app/en/references/auth-providers/x/page.mdx   |  14 +-
 .../auth-providers/zendesk/page.mdx           |  10 +-
 .../references/auth-providers/zoho/page.mdx   |  16 +-
 .../references/auth-providers/zoom/page.mdx   |   8 +-
 app/en/references/changelog/page.mdx          |  44 +-
 app/en/references/cli-cheat-sheet/page.mdx    |   2 +-
 app/en/references/mcp/python/page.mdx         |   8 +-
 app/en/references/mcp/python/server/page.mdx  |   2 +-
 app/en/references/mcp/telemetry/page.mdx      |   2 +-
 app/en/references/page.mdx                    |   4 +-
 app/en/resources/examples/page.mdx            |   4 +-
 app/en/resources/faq/page.mdx                 |   8 +-
 app/en/resources/glossary/page.mdx            |  26 +-
 .../integrations/search/tavily/page.mdx       |  10 +-
 .../resources/registry-early-access/page.mdx  |   2 +-
 app/en/resources/tools/page.mdx               |   6 +-
 next.config.ts                                | 944 ++++++++++++++++++
 114 files changed, 1444 insertions(+), 502 deletions(-)

diff --git a/app/_components/toolkit-docs/components/toolkit-page.tsx b/app/_components/toolkit-docs/components/toolkit-page.tsx
index ad55c6413..6e624b7d4 100644
--- a/app/_components/toolkit-docs/components/toolkit-page.tsx
+++ b/app/_components/toolkit-docs/components/toolkit-page.tsx
@@ -234,9 +234,7 @@ function BreadcrumbBar({
 }) {
   return (
     <nav className="mb-6 flex flex-wrap items-center gap-2 text-muted-foreground text-sm">
-      <a className="hover:text-brand-accent" href="/en/resources">
-        Resources
-      </a>
+      <span>Resources</span>
       <span className="text-muted-foreground/40">›</span>
       <a className="hover:text-brand-accent" href="/en/resources/integrations">
         Integrations
diff --git a/app/en/get-started/about-arcade/page.mdx b/app/en/get-started/about-arcade/page.mdx
index 44a049a7a..ef22dc376 100644
--- a/app/en/get-started/about-arcade/page.mdx
+++ b/app/en/get-started/about-arcade/page.mdx
@@ -43,7 +43,7 @@ With Arcade, developers can now create agents that can _act as the end users of
 
 ## Auth permissions and scopes
 
-Each tool in Arcade's MCP servers has a set of required permissions - or, more commonly referred to in OAuth 2.0, **scopes**. For example, the [`Gmail.SendEmail`](/resources/integrations/productivity/gmail#gmailsendemail) tool requires the [`https://www.googleapis.com/auth/gmail.send`](https://developers.google.com/identity/protocols/oauth2/scopes#gmail) scope.
+Each tool in Arcade's MCP servers has a set of required permissions - or, more commonly referred to in OAuth 2.0, **scopes**. For example, the [`Gmail.SendEmail`](/en/resources/integrations/productivity/gmail#gmailsendemail) tool requires the [`https://www.googleapis.com/auth/gmail.send`](https://developers.google.com/identity/protocols/oauth2/scopes#gmail) scope.
 
 A scope is what the user has authorized someone else (in this case, the AI agent) to do on their behalf. In any OAuth 2.0-compatible service, each kind of action requires a different set of permissions. This gives the user fine-grained control over what data third-party services can access and what actions they can take in their accounts.
 
@@ -51,11 +51,11 @@ When an agent calls a tool, if the user has not granted the required permissions
 
 ## How to implement OAuth 2.0-authorized tool calling
 
-To learn how Arcade authorizes actions (tools) through OAuth 2.0 and how to implement auth flow, check out [Authorized Tool Calling](/guides/tool-calling/custom-apps/auth-tool-calling).
+To learn how Arcade authorizes actions (tools) through OAuth 2.0 and how to implement auth flow, check out [Authorized Tool Calling](/en/guides/tool-calling/custom-apps/auth-tool-calling).
 
 ## Tools that don't require authorization
 
-Some tools, like [`GoogleSearch.Search`](/resources/integrations/search/google_search#googlesearchsearch), allow AI agents to retrieve information or perform actions without needing user-specific authorization.
+Some tools, like [`GoogleSearch.Search`](/en/resources/integrations/search/google_search#googlesearchsearch), allow AI agents to retrieve information or perform actions without needing user-specific authorization.
 
 <Tabs items={["Python", "JavaScript"]} storageKey="preferredLanguage">
 <Tabs.Tab>
diff --git a/app/en/get-started/agent-frameworks/ag2/use-arcade-tools/page.mdx b/app/en/get-started/agent-frameworks/ag2/use-arcade-tools/page.mdx
index eb7fec54c..93dadb255 100644
--- a/app/en/get-started/agent-frameworks/ag2/use-arcade-tools/page.mdx
+++ b/app/en/get-started/agent-frameworks/ag2/use-arcade-tools/page.mdx
@@ -19,7 +19,7 @@ You will build an AG2 agent that uses Arcade tools to help users with Gmail and
 <GuideOverview.Prerequisites>
 
 - <DashboardLink path="register" />
-- [Obtain an Arcade API key](/get-started/setup/api-keys)
+- [Obtain an Arcade API key](/en/get-started/setup/api-keys)
 - The [`uv` package manager](https://docs.astral.sh/uv/)
 
 </GuideOverview.Prerequisites>
diff --git a/app/en/get-started/agent-frameworks/crewai/use-arcade-tools/page.mdx b/app/en/get-started/agent-frameworks/crewai/use-arcade-tools/page.mdx
index 8455a60fd..d23ce675d 100644
--- a/app/en/get-started/agent-frameworks/crewai/use-arcade-tools/page.mdx
+++ b/app/en/get-started/agent-frameworks/crewai/use-arcade-tools/page.mdx
@@ -19,7 +19,7 @@ You will build a CrewAI agent that uses Arcade tools to help users with Gmail an
 <GuideOverview.Prerequisites>
 
 - <DashboardLink path="register" />
-- [Obtain an Arcade API key](/get-started/setup/api-keys)
+- [Obtain an Arcade API key](/en/get-started/setup/api-keys)
 - The [`uv` package manager](https://docs.astral.sh/uv/)
 
 </GuideOverview.Prerequisites>
diff --git a/app/en/get-started/agent-frameworks/google-adk/overview/page.mdx b/app/en/get-started/agent-frameworks/google-adk/overview/page.mdx
index 7c8f6ed71..f06de752b 100644
--- a/app/en/get-started/agent-frameworks/google-adk/overview/page.mdx
+++ b/app/en/get-started/agent-frameworks/google-adk/overview/page.mdx
@@ -12,7 +12,7 @@ description: "Integrate Arcade tools with Google ADK agents"
 Choose your language to set up Arcade with Google ADK:
 
 - **[Python setup](/en/get-started/agent-frameworks/google-adk/setup-python)** - Build an agent with Arcade tools using the `google-adk-arcade` package
-- **[TypeScript setup](/get-started/agent-frameworks/google-adk/setup-typescript)** - Build an agent with Arcade tools using `@arcadeai/arcadejs`
+- **[TypeScript setup](/en/get-started/agent-frameworks/google-adk/setup-typescript)** - Build an agent with Arcade tools using `@arcadeai/arcadejs`
 
 ## What you can build
 
@@ -24,4 +24,4 @@ With Arcade and Google ADK, your agents can:
 - Search the web and extract content
 - Access 7,000+ other integrations
 
-Browse the [full MCP server catalog](/resources/integrations) to see all available tools.
+Browse the [full MCP server catalog](/en/resources/integrations) to see all available tools.
diff --git a/app/en/get-started/agent-frameworks/google-adk/setup-python/page.mdx b/app/en/get-started/agent-frameworks/google-adk/setup-python/page.mdx
index 22dd27025..531bd80b5 100644
--- a/app/en/get-started/agent-frameworks/google-adk/setup-python/page.mdx
+++ b/app/en/get-started/agent-frameworks/google-adk/setup-python/page.mdx
@@ -77,7 +77,7 @@ uv add arcadepy google-adk
 
 Provide your Arcade and Google API keys. You can store it in environment variables or directly in your code:
 
-> Need an Arcade API key? Visit the [Get an API key](/get-started/setup/api-keys) page to create one.
+> Need an Arcade API key? Visit the [Get an API key](/en/get-started/setup/api-keys) page to create one.
 
 Create a new file called `.env` and add the following environment variables:
 
diff --git a/app/en/get-started/agent-frameworks/google-adk/setup-typescript/page.mdx b/app/en/get-started/agent-frameworks/google-adk/setup-typescript/page.mdx
index 8dd07b528..387636538 100644
--- a/app/en/get-started/agent-frameworks/google-adk/setup-typescript/page.mdx
+++ b/app/en/get-started/agent-frameworks/google-adk/setup-typescript/page.mdx
@@ -19,7 +19,7 @@ Build an agent that uses Arcade tools to help users with Gmail and Slack
 <GuideOverview.Prerequisites>
 
 - <DashboardLink path="register" />
-- [Obtain an Arcade API key](/get-started/setup/api-keys)
+- [Obtain an Arcade API key](/en/get-started/setup/api-keys)
 - [Node.js](https://nodejs.org/) 18+ (includes npm) or [Bun](https://bun.sh/)
 - A [Gemini API key](https://aistudio.google.com/apikey)
 
@@ -494,4 +494,4 @@ main().catch(console.error);
 
 - Add more tools by modifying `MCP_SERVERS` and `INDIVIDUAL_TOOLS`
 - Build multi-agent systems with different Arcade tools
-- Explore [creating custom tools](/guides/create-tools/tool-basics/build-mcp-server) with the Arcade Tool SDK
+- Explore [creating custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) with the Arcade Tool SDK
diff --git a/app/en/get-started/agent-frameworks/langchain/auth-langchain-tools/page.mdx b/app/en/get-started/agent-frameworks/langchain/auth-langchain-tools/page.mdx
index a552fb3e1..ad0f94277 100644
--- a/app/en/get-started/agent-frameworks/langchain/auth-langchain-tools/page.mdx
+++ b/app/en/get-started/agent-frameworks/langchain/auth-langchain-tools/page.mdx
@@ -13,7 +13,7 @@ In this guide, we'll show you how to authorize LangChain tools like the `GmailTo
 
 ### Prerequisites
 
-- [Obtain an Arcade API key](/get-started/setup/api-keys)
+- [Obtain an Arcade API key](/en/get-started/setup/api-keys)
 
 ### Install the required packages
 
diff --git a/app/en/get-started/agent-frameworks/langchain/overview/page.mdx b/app/en/get-started/agent-frameworks/langchain/overview/page.mdx
index fcd81cd90..3f07df424 100644
--- a/app/en/get-started/agent-frameworks/langchain/overview/page.mdx
+++ b/app/en/get-started/agent-frameworks/langchain/overview/page.mdx
@@ -11,8 +11,8 @@ description: "Integrate Arcade tools with LangChain agents"
 
 Choose your language to set up Arcade with LangChain:
 
-- **[Python setup](/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py)** - Build an agent with Arcade tools using `langchain-arcade`
-- **[TypeScript setup](/get-started/agent-frameworks/langchain/use-arcade-with-langchain-ts)** - Build an agent with Arcade tools using `@arcadeai/arcadejs`
+- **[Python setup](/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py)** - Build an agent with Arcade tools using `langchain-arcade`
+- **[TypeScript setup](/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-ts)** - Build an agent with Arcade tools using `@arcadeai/arcadejs`
 
 ## What you can build
 
@@ -24,8 +24,8 @@ With Arcade and LangChain, your agents can:
 - Search the web and extract content
 - Access 7,000+ other integrations
 
-Browse the [full MCP server catalog](/resources/integrations) to see all available tools.
+Browse the [full MCP server catalog](/en/resources/integrations) to see all available tools.
 
 ## Advanced topics
 
-- **[Authorizing existing tools](/get-started/agent-frameworks/langchain/auth-langchain-tools)** - Add Arcade authorization to your existing LangChain tools
+- **[Authorizing existing tools](/en/get-started/agent-frameworks/langchain/auth-langchain-tools)** - Add Arcade authorization to your existing LangChain tools
diff --git a/app/en/get-started/agent-frameworks/mastra/page.mdx b/app/en/get-started/agent-frameworks/mastra/page.mdx
index f094e32d0..2efdb25f8 100644
--- a/app/en/get-started/agent-frameworks/mastra/page.mdx
+++ b/app/en/get-started/agent-frameworks/mastra/page.mdx
@@ -230,7 +230,7 @@ You might select your tools individually for a few reasons:
 * **Cost** Each tool's schema consumes tokens. Loading all Gmail tools (~20 tools) uses more tokens than loading just the 3 you need. This matters for rate limits and cost.
 
 <Callout type="info">
-  Browse the [complete MCP server catalog](/resources/integrations) to see available servers and their tools.
+  Browse the [complete MCP server catalog](/en/resources/integrations) to see available servers and their tools.
 </Callout>
 
 ##### Arcade SDK functions
@@ -366,7 +366,7 @@ On first use, the agent will return an authorization URL. Visit the URL to conne
 
 </Steps>
 
-![Mastra Studio agent interaction](/images/screenshots/mastra-studio-agent-interaction.png)
+![Mastra Studio agent interaction](/en/images/screenshots/mastra-studio-agent-interaction.png)
 
 ## Build a workflow
 
@@ -613,7 +613,7 @@ export const mastra = new Mastra({
 
 </Steps>
 
-![Mastra Studio workflow run](/images/screenshots/mastra-studio-workflow-run.png)
+![Mastra Studio workflow run](/en/images/screenshots/mastra-studio-workflow-run.png)
 
 ## Key takeaways
 
@@ -625,12 +625,12 @@ export const mastra = new Mastra({
 
 ## Next steps
 
-- **Add more tools**: Browse the [tool catalog](/resources/integrations) and add tools for GitHub, Notion, Linear, and more.
+- **Add more tools**: Browse the [tool catalog](/en/resources/integrations) and add tools for GitHub, Notion, Linear, and more.
 - **Schedule your workflow**: Use a cron job or [Mastra's scheduling](https://mastra.ai/docs/workflows/scheduling) to run your email digest every morning.
 - **Deploy to production**: Follow Mastra's [deployment guides](https://mastra.ai/docs/deployment/overview) to deploy your agent and workflows.
 
 <Callout type="info">
-  **Building a multi-user app?** This tutorial uses a single `ARCADE_USER_ID` for simplicity. For production apps where each user needs their own OAuth tokens, see [Secure auth for production](/guides/user-facing-agents/secure-auth-production) to learn how to dynamically pass user IDs and handle per-user authorization.
+  **Building a multi-user app?** This tutorial uses a single `ARCADE_USER_ID` for simplicity. For production apps where each user needs their own OAuth tokens, see [Secure auth for production](/en/guides/user-facing-agents/secure-auth-production) to learn how to dynamically pass user IDs and handle per-user authorization.
 </Callout>
 
 ## Complete code
diff --git a/app/en/get-started/agent-frameworks/openai-agents/overview/page.mdx b/app/en/get-started/agent-frameworks/openai-agents/overview/page.mdx
index a88de02ef..1b78e994c 100644
--- a/app/en/get-started/agent-frameworks/openai-agents/overview/page.mdx
+++ b/app/en/get-started/agent-frameworks/openai-agents/overview/page.mdx
@@ -11,8 +11,8 @@ The [OpenAI Agents SDK](https://openai.github.io/openai-agents-python/) provides
 
 Choose your language to set up Arcade with OpenAI Agents:
 
-- **[Python setup](/get-started/agent-frameworks/openai-agents/setup-python)** - Build a CLI agent with Arcade tools using the `agents-arcade` package
-- **[TypeScript setup](/get-started/agent-frameworks/openai-agents/setup-typescript)** - Build an agent with Arcade tools using `@arcadeai/arcadejs`
+- **[Python setup](/en/get-started/agent-frameworks/openai-agents/setup-python)** - Build a CLI agent with Arcade tools using the `agents-arcade` package
+- **[TypeScript setup](/en/get-started/agent-frameworks/openai-agents/setup-typescript)** - Build an agent with Arcade tools using `@arcadeai/arcadejs`
 
 ## What you can build
 
@@ -24,4 +24,4 @@ With Arcade and OpenAI Agents, your agents can:
 - Search the web and extract content
 - Access 7,000+ other integrations
 
-Browse the [full MCP server catalog](/resources/integrations) to see all available tools.
+Browse the [full MCP server catalog](/en/resources/integrations) to see all available tools.
diff --git a/app/en/get-started/agent-frameworks/openai-agents/setup-python/page.mdx b/app/en/get-started/agent-frameworks/openai-agents/setup-python/page.mdx
index 2f5029e65..98c7437d6 100644
--- a/app/en/get-started/agent-frameworks/openai-agents/setup-python/page.mdx
+++ b/app/en/get-started/agent-frameworks/openai-agents/setup-python/page.mdx
@@ -21,7 +21,7 @@ You will implement a CLI agent that can use Arcade tools to help the user with t
 <GuideOverview.Prerequisites>
 
 - <DashboardLink path="register" />
-- [Obtain an Arcade API key](/get-started/setup/api-keys)
+- [Obtain an Arcade API key](/en/get-started/setup/api-keys)
 - The [`uv` package manager](https://docs.astral.sh/uv/)
 
 </GuideOverview.Prerequisites>
diff --git a/app/en/get-started/agent-frameworks/openai-agents/setup-typescript/page.mdx b/app/en/get-started/agent-frameworks/openai-agents/setup-typescript/page.mdx
index 03e4d2978..d65481263 100644
--- a/app/en/get-started/agent-frameworks/openai-agents/setup-typescript/page.mdx
+++ b/app/en/get-started/agent-frameworks/openai-agents/setup-typescript/page.mdx
@@ -19,7 +19,7 @@ Build an agent that uses Arcade tools to help users with Gmail and Slack
 <GuideOverview.Prerequisites>
 
 - <DashboardLink path="register" />
-- [Obtain an Arcade API key](/get-started/setup/api-keys)
+- [Obtain an Arcade API key](/en/get-started/setup/api-keys)
 - [Node.js](https://nodejs.org/) 18+ (includes npm) or [Bun](https://bun.sh/)
 
 </GuideOverview.Prerequisites>
@@ -395,5 +395,5 @@ main().catch(console.error);
 
 - Add more tools by modifying `MCP_SERVERS` and `INDIVIDUAL_TOOLS`
 - Build a web interface using frameworks like Next.js or Express
-- See the [Vercel AI SDK tutorial](/get-started/agent-frameworks/vercelai) or [TanStack AI tutorial](/get-started/agent-frameworks/tanstack-ai) for complete web chatbot examples
-- Explore [creating custom tools](/guides/create-tools/tool-basics/build-mcp-server) with the Arcade Tool SDK
+- See the [Vercel AI SDK tutorial](/en/get-started/agent-frameworks/vercelai) or [TanStack AI tutorial](/en/get-started/agent-frameworks/tanstack-ai) for complete web chatbot examples
+- Explore [creating custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) with the Arcade Tool SDK
diff --git a/app/en/get-started/agent-frameworks/setup-arcade-with-your-llm-python/page.mdx b/app/en/get-started/agent-frameworks/setup-arcade-with-your-llm-python/page.mdx
index 6365c3c38..5deb5b01e 100644
--- a/app/en/get-started/agent-frameworks/setup-arcade-with-your-llm-python/page.mdx
+++ b/app/en/get-started/agent-frameworks/setup-arcade-with-your-llm-python/page.mdx
@@ -20,7 +20,7 @@ Integrate Arcade's tool-calling capabilities into an application that uses an LL
 <GuideOverview.Prerequisites>
 
 - An <SignupLink linkLocation="docs:call-tools-directly">Arcade account</SignupLink>
-- An [Arcade API key](/get-started/setup/api-keys)
+- An [Arcade API key](/en/get-started/setup/api-keys)
 - An [OpenRouter API key](https://openrouter.ai/docs/guides/overview/auth/provisioning-api-keys)
 - The [`uv` package manager](https://docs.astral.sh/uv/getting-started/installation/)
 
@@ -106,7 +106,7 @@ OPENROUTER_MODEL=YOUR_OPENROUTER_MODEL
   The `ARCADE_USER_ID` is the email address you used to sign up for Arcade. When
   your app is ready for production, you can set this dynamically based on your
   app's auth system. Learn more about how to achieve secure auth in production
-  [here](/guides/user-facing-agents/secure-auth-production).
+  [here](/en/guides/user-facing-agents/secure-auth-production).
 </Callout>
 
 <Callout type="info">
@@ -329,8 +329,8 @@ With the selection of tools above, you should be able to get the agent to effect
 
 ## Next Steps
 
-- Learn more about using Arcade with a [framework](/get-started/agent-frameworks) or [MCP client](/get-started/mcp-clients).
-- Learn more about how to [build your own MCP Servers](/guides/create-tools/tool-basics/build-mcp-server).
+- Learn more about using Arcade with a [framework](/en/get-started/agent-frameworks) or [MCP client](/en/get-started/mcp-clients).
+- Learn more about how to [build your own MCP Servers](/en/guides/create-tools/tool-basics/build-mcp-server).
 
 ## Example code
 
diff --git a/app/en/get-started/agent-frameworks/springai/page.mdx b/app/en/get-started/agent-frameworks/springai/page.mdx
index 204e9547e..c67cace93 100644
--- a/app/en/get-started/agent-frameworks/springai/page.mdx
+++ b/app/en/get-started/agent-frameworks/springai/page.mdx
@@ -442,8 +442,8 @@ curl -X POST http://localhost:8080/api/chat \
 
 ## Next steps
 
-1. **Add more tools**: Browse the [MCP server catalog](/resources/integrations) and add `@Tool` methods for GitHub, Google Docs, Notion, and more.
-2. **Add user authentication**: In production, resolve `userId` from your authentication system instead of a static configuration property. See [Secure auth in production](/guides/user-facing-agents/secure-auth-production) for best practices.
+1. **Add more tools**: Browse the [MCP server catalog](/en/resources/integrations) and add `@Tool` methods for GitHub, Google Docs, Notion, and more.
+2. **Add user authentication**: In production, resolve `userId` from your authentication system instead of a static configuration property. See [Secure auth in production](/en/guides/user-facing-agents/secure-auth-production) for best practices.
 3. **Stream responses**: Replace `.call()` with `.stream()` on the `ChatClient` to stream responses using [Server-Sent Events](https://docs.spring.io/spring-ai/reference/api/chatclient.html#_streaming_responses).
 
 ## Complete code
diff --git a/app/en/get-started/agent-frameworks/tanstack-ai/page.mdx b/app/en/get-started/agent-frameworks/tanstack-ai/page.mdx
index 21eac6386..20804105f 100644
--- a/app/en/get-started/agent-frameworks/tanstack-ai/page.mdx
+++ b/app/en/get-started/agent-frameworks/tanstack-ai/page.mdx
@@ -355,7 +355,7 @@ export const Route = createFileRoute("/api/chat")({
 
 <Callout type="info">
   You can mix MCP servers (which give you all their tools) with individual
-  tools. Browse the [complete MCP server catalog](/resources/integrations) to
+  tools. Browse the [complete MCP server catalog](/en/resources/integrations) to
   see what's available.
 </Callout>
 
@@ -695,9 +695,9 @@ On first use, you'll see an authorization button. Click it to connect your Gmail
 
 ## Next steps
 
-1. **Add more tools**: Browse the [MCP server catalog](/resources/integrations) and add tools for GitHub, Notion, Linear, and more.
+1. **Add more tools**: Browse the [MCP server catalog](/en/resources/integrations) and add tools for GitHub, Notion, Linear, and more.
 2. **Try different providers**: Swap `@tanstack/ai-openai` for `@tanstack/ai-anthropic` or `@tanstack/ai-gemini` to use different AI models.
-3. **Add user authentication**: In production, get `userId` from your auth system instead of environment variables. See [Secure your server](/guides/create-tools/secure-your-server) for best practices.
+3. **Add user authentication**: In production, get `userId` from your auth system instead of environment variables. See [Secure your server](/en/guides/create-tools/secure-your-server) for best practices.
 4. **Deploy your chatbot**: TanStack Start supports deployment to Vercel, Netlify, Cloudflare, and Node.js servers.
 
 ## Complete code
diff --git a/app/en/get-started/agent-frameworks/vercelai/page.mdx b/app/en/get-started/agent-frameworks/vercelai/page.mdx
index 8cf3e8a77..870442e95 100644
--- a/app/en/get-started/agent-frameworks/vercelai/page.mdx
+++ b/app/en/get-started/agent-frameworks/vercelai/page.mdx
@@ -171,7 +171,7 @@ IMPORTANT: When calling tools, if an argument is optional, do not set it. Never
 
 <Callout type="info">
   You can mix MCP servers (which give you all their tools) with individual
-  tools. Browse the [complete MCP server catalog](/resources/integrations) to
+  tools. Browse the [complete MCP server catalog](/en/resources/integrations) to
   see what's available.
 </Callout>
 
@@ -596,8 +596,8 @@ On first use, you'll see an authorization button. Click it to connect your Gmail
 
 ## Next steps
 
-1. **Add more tools**: Browse the [MCP server catalog](/resources/integrations) and add tools for GitHub, Notion, Linear, and more.
-2. **Add user authentication**: In production, get `userId` from your auth system instead of environment variables. See [Secure your server](/guides/create-tools/secure-your-server) for best practices.
+1. **Add more tools**: Browse the [MCP server catalog](/en/resources/integrations) and add tools for GitHub, Notion, Linear, and more.
+2. **Add user authentication**: In production, get `userId` from your auth system instead of environment variables. See [Secure your server](/en/guides/create-tools/secure-your-server) for best practices.
 3. **Deploy to Vercel**: Push your chatbot to GitHub and [deploy to Vercel](https://vercel.com/docs/deployments/overview) with one click. Add your environment variables in the Vercel dashboard.
 
 ## Complete code
diff --git a/app/en/get-started/mcp-clients/claude-code/page.mdx b/app/en/get-started/mcp-clients/claude-code/page.mdx
index 0caee4c1e..4969ed3c0 100644
--- a/app/en/get-started/mcp-clients/claude-code/page.mdx
+++ b/app/en/get-started/mcp-clients/claude-code/page.mdx
@@ -13,8 +13,8 @@ Connect Claude Code to an Arcade MCP Gateway using the Arcade Headers authentica
 <GuideOverview.Prerequisites>
 
 1. Create an <SignupLink linkLocation="docs:claude-code-client">Arcade account</SignupLink>
-2. Get an [Arcade API key](/get-started/setup/api-keys)
-3. Create an [Arcade MCP Gateway](/guides/mcp-gateways) and select the tools you want to use
+2. Get an [Arcade API key](/en/get-started/setup/api-keys)
+3. Create an [Arcade MCP Gateway](/en/guides/mcp-gateways) and select the tools you want to use
 
 </GuideOverview.Prerequisites>
 </GuideOverview>
diff --git a/app/en/get-started/mcp-clients/claude-desktop/page.mdx b/app/en/get-started/mcp-clients/claude-desktop/page.mdx
index 9e67781c4..fe0da8db9 100644
--- a/app/en/get-started/mcp-clients/claude-desktop/page.mdx
+++ b/app/en/get-started/mcp-clients/claude-desktop/page.mdx
@@ -44,8 +44,8 @@ Connect Claude Desktop to an Arcade MCP Gateway.
 <GuideOverview.Prerequisites>
 
 1. Create an <SignupLink linkLocation="docs:claude-desktop-client">Arcade account</SignupLink>
-2. Get an [Arcade API key](/get-started/setup/api-keys)
-3. Create an [Arcade MCP Gateway](/guides/mcp-gateways) and select the tools you want to use
+2. Get an [Arcade API key](/en/get-started/setup/api-keys)
+3. Create an [Arcade MCP Gateway](/en/guides/mcp-gateways) and select the tools you want to use
 
 </GuideOverview.Prerequisites>
 
diff --git a/app/en/get-started/mcp-clients/copilot-studio/page.mdx b/app/en/get-started/mcp-clients/copilot-studio/page.mdx
index 01cfcc84f..0e8a85b5c 100644
--- a/app/en/get-started/mcp-clients/copilot-studio/page.mdx
+++ b/app/en/get-started/mcp-clients/copilot-studio/page.mdx
@@ -25,8 +25,8 @@ Connect Microsoft Copilot Studio to an Arcade MCP Gateway.
 
 1. A Microsoft 365 subscription with access to Copilot Studio
 2. Create an <SignupLink linkLocation="docs:copilot-studio-client">Arcade account</SignupLink>
-3. Get an [Arcade API key](/get-started/setup/api-keys)
-4. Create an [Arcade MCP Gateway](/guides/mcp-gateways) and select the tools you want to use
+3. Get an [Arcade API key](/en/get-started/setup/api-keys)
+4. Create an [Arcade MCP Gateway](/en/guides/mcp-gateways) and select the tools you want to use
 
 </GuideOverview.Prerequisites>
 
diff --git a/app/en/get-started/mcp-clients/cursor/page.mdx b/app/en/get-started/mcp-clients/cursor/page.mdx
index bf9cf04a2..46fdd47ef 100644
--- a/app/en/get-started/mcp-clients/cursor/page.mdx
+++ b/app/en/get-started/mcp-clients/cursor/page.mdx
@@ -13,8 +13,8 @@ Connect Cursor to an Arcade MCP Gateway.
 <GuideOverview.Prerequisites>
 
 1. Create an <SignupLink linkLocation="docs:claude-desktop-client">Arcade account</SignupLink>
-2. Get an [Arcade API key](/get-started/setup/api-keys)
-3. Create an [Arcade MCP Gateway](/guides/mcp-gateways) and select the tools you want to use
+2. Get an [Arcade API key](/en/get-started/setup/api-keys)
+3. Create an [Arcade MCP Gateway](/en/guides/mcp-gateways) and select the tools you want to use
 
 </GuideOverview.Prerequisites>
 
diff --git a/app/en/get-started/mcp-clients/page.mdx b/app/en/get-started/mcp-clients/page.mdx
index 12648a779..4dd359a40 100644
--- a/app/en/get-started/mcp-clients/page.mdx
+++ b/app/en/get-started/mcp-clients/page.mdx
@@ -7,6 +7,6 @@ import { MCPClientGrid } from "./mcp-client-grid";
 
 # Connect to MCP Clients
 
-You can connect [Arcade MCP servers](/resources/integrations) to MCP-compatible clients and development environments to unlock powerful flows for your agents.
+You can connect [Arcade MCP servers](/en/resources/integrations) to MCP-compatible clients and development environments to unlock powerful flows for your agents.
 
 <MCPClientGrid />
diff --git a/app/en/get-started/mcp-clients/visual-studio-code/page.mdx b/app/en/get-started/mcp-clients/visual-studio-code/page.mdx
index 811de3162..d9585f648 100644
--- a/app/en/get-started/mcp-clients/visual-studio-code/page.mdx
+++ b/app/en/get-started/mcp-clients/visual-studio-code/page.mdx
@@ -10,7 +10,7 @@ In this guide, you'll learn how to connect Visual Studio Code to an Arcade MCP G
 ### Prerequisites
 
 1. Create an <SignupLink linkLocation="docs:claude-desktop-client">Arcade account</SignupLink>
-2. Create an [Arcade MCP Gateway](/guides/mcp-gateways) and select the tools you want to use
+2. Create an [Arcade MCP Gateway](/en/guides/mcp-gateways) and select the tools you want to use
 
 ### Set up Visual Studio Code
 
diff --git a/app/en/get-started/quickstarts/call-tool-agent/page.mdx b/app/en/get-started/quickstarts/call-tool-agent/page.mdx
index 0c56a689c..5f524e67b 100644
--- a/app/en/get-started/quickstarts/call-tool-agent/page.mdx
+++ b/app/en/get-started/quickstarts/call-tool-agent/page.mdx
@@ -21,7 +21,7 @@ Install and use the Arcade client to call Arcade Hosted Tools.
 <GuideOverview.Prerequisites>
 
 - An <SignupLink linkLocation="docs:call-tools-directly" utmCampaign="docs-quickstart-call-tool-agent">Arcade account</SignupLink>
-- An [Arcade API key](/get-started/setup/api-keys)
+- An [Arcade API key](/en/get-started/setup/api-keys)
 - The [`uv` package manager](https://docs.astral.sh/uv/getting-started/installation/) if you are using Python
 - The [`bun` runtime](https://bun.com/) if you are using TypeScript
 - [Apache Maven](https://maven.apache.org/) or [Gradle](https://gradle.org/) if you are using Java
@@ -539,7 +539,7 @@ logger.info(
 
 ## Next Steps
 
-In this example, we call the tool methods directly. In your real applications and agents, you'll likely be letting the LLM decide which tools to call. Learn more about using Arcade with Frameworks in the [Frameworks](/get-started/agent-frameworks) section, or [how to build your own tools](/guides/create-tools/tool-basics/build-mcp-server).
+In this example, we call the tool methods directly. In your real applications and agents, you'll likely be letting the LLM decide which tools to call. Learn more about using Arcade with Frameworks in the [Frameworks](/en/get-started/agent-frameworks) section, or [how to build your own tools](/en/guides/create-tools/tool-basics/build-mcp-server).
 
 <AgentFrameworkTabs />
 
diff --git a/app/en/get-started/quickstarts/call-tool-client/page.mdx b/app/en/get-started/quickstarts/call-tool-client/page.mdx
index c4e01616f..0c6d84a53 100644
--- a/app/en/get-started/quickstarts/call-tool-client/page.mdx
+++ b/app/en/get-started/quickstarts/call-tool-client/page.mdx
@@ -147,8 +147,8 @@ As you interact with the agent, it will call the tools from the MCP Gateway. You
 
 ## Next Steps
 
-- Learn more about [MCP Gateways](/guides/mcp-gateways).
+- Learn more about [MCP Gateways](/en/guides/mcp-gateways).
 - Learn how to use MCP Gateways with:
-  - [Cursor](/get-started/mcp-clients/cursor)
-  - [Visual Studio Code](/get-started/mcp-clients/visual-studio-code)
-- Build your own MCP servers with [arcade-mcp](/get-started/quickstarts/mcp-server-quickstart).
+  - [Cursor](/en/get-started/mcp-clients/cursor)
+  - [Visual Studio Code](/en/get-started/mcp-clients/visual-studio-code)
+- Build your own MCP servers with [arcade-mcp](/en/get-started/quickstarts/mcp-server-quickstart).
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 52e7e6811..77fe83cfe 100644
--- a/app/en/get-started/quickstarts/mcp-server-quickstart/page.mdx
+++ b/app/en/get-started/quickstarts/mcp-server-quickstart/page.mdx
@@ -186,7 +186,7 @@ uv run server.py stdio
   a subprocess. Because of this, the server may run in a different environment
   and not have access to secrets defined in your local `.env` file. Please refer
   to the [create a tool with
-  secrets](/guides/create-tools/tool-basics/create-tool-secrets) guide for more
+  secrets](/en/guides/create-tools/tool-basics/create-tool-secrets) guide for more
   information.
 </Callout>
 
@@ -206,8 +206,8 @@ For HTTP transport, view your server's API docs at [http://127.0.0.1:8000/docs](
   API key and secrets in your MCP connection settings. Otherwise, if you intend
   to expose your HTTP MCP server to the public internet with tool-level
   authorization and secrets, please follow the [deploying to the cloud with
-  Arcade Deploy](/guides/deployment-hosting/arcade-deploy) guide or the [on-prem
-  MCP server](/guides/deployment-hosting/on-prem) guide for secure remote
+  Arcade Deploy](/en/guides/deployment-hosting/arcade-deploy) guide or the [on-prem
+  MCP server](/en/guides/deployment-hosting/on-prem) guide for secure remote
   deployment.
 </Callout>
 
@@ -294,8 +294,8 @@ Ensure you have set the environment variable in your terminal or `.env` file, an
 
 ## Next Steps
 
-- **Learn how to write a tool with auth**: [Create a tool with auth](/guides/create-tools/tool-basics/create-tool-auth)
-- **Learn how to write a tool with secrets**: [Create a tool with secrets](/guides/create-tools/tool-basics/create-tool-secrets)
-- **Learn more about the Context object**: [Tools and Context](/guides/create-tools/tool-basics/runtime-data-access)
-- **Learn how to write tool evaluations**: [Create an evaluation suite](/guides/create-tools/evaluate-tools/create-evaluation-suite) to optimize them for LLM usage
-- **Learn how to deploy your MCP server**: [Deploy your MCP server](/guides/deployment-hosting/arcade-deploy)
+- **Learn how to write a tool with auth**: [Create a tool with auth](/en/guides/create-tools/tool-basics/create-tool-auth)
+- **Learn how to write a tool with secrets**: [Create a tool with secrets](/en/guides/create-tools/tool-basics/create-tool-secrets)
+- **Learn more about the Context object**: [Tools and Context](/en/guides/create-tools/tool-basics/runtime-data-access)
+- **Learn how to write tool evaluations**: [Create an evaluation suite](/en/guides/create-tools/evaluate-tools/create-evaluation-suite) to optimize them for LLM usage
+- **Learn how to deploy your MCP server**: [Deploy your MCP server](/en/guides/deployment-hosting/arcade-deploy)
diff --git a/app/en/get-started/setup/api-keys/page.mdx b/app/en/get-started/setup/api-keys/page.mdx
index c995e9dd6..0ba55b3e7 100644
--- a/app/en/get-started/setup/api-keys/page.mdx
+++ b/app/en/get-started/setup/api-keys/page.mdx
@@ -106,5 +106,5 @@ The CLI will automatically:
 
 Once you have your API key, you can:
 
-- [Start using tools](/get-started/quickstarts/call-tool-agent)
-- [Create custom tools](/guides/create-tools/tool-basics/build-mcp-server)
+- [Start using tools](/en/get-started/quickstarts/call-tool-agent)
+- [Create custom tools](/en/guides/create-tools/tool-basics/build-mcp-server)
diff --git a/app/en/get-started/setup/connect-arcade-docs/page.mdx b/app/en/get-started/setup/connect-arcade-docs/page.mdx
index 3fa170e18..191fa09de 100644
--- a/app/en/get-started/setup/connect-arcade-docs/page.mdx
+++ b/app/en/get-started/setup/connect-arcade-docs/page.mdx
@@ -16,12 +16,12 @@ For example, you can tell your agent to visit `docs.arcade.dev/get-started/quick
 
 ## LLMs.txt
 
-Give your AI IDE access to Arcade.dev's documentation using the [llms.txt](/llms.txt) file. This allows Claude Code, Cursor, and other AI IDEs to access the documentation and help you write code.
+Give your AI IDE access to Arcade.dev's documentation using the [llms.txt](/en/llms.txt) file. This allows Claude Code, Cursor, and other AI IDEs to access the documentation and help you write code.
 
 LLMs.txt is a file format that allows you to give your AI IDE access to Arcade.dev's documentation in a format that the LLM can parse. All you need to do is paste in the content of the file into your IDE's settings, or reference the docs, for example via [Cursor's `@docs` annotation](https://cursor.com/docs/context/symbols#docs).
 
-The LLMs.txt files are available at [`/llms.txt`](/llms.txt).
+The LLMs.txt files are available at [`/llms.txt`](/en/llms.txt).
 
-![LLMs.txt example](/images/agentic-development/cursor-llms-txt.png)
+![LLMs.txt example](/en/images/agentic-development/cursor-llms-txt.png)
 
 Learn more about the LLMs.txt file format [here](https://llmstxt.org/).
diff --git a/app/en/get-started/setup/windows-environment/page.mdx b/app/en/get-started/setup/windows-environment/page.mdx
index 620774346..ddf783ee0 100644
--- a/app/en/get-started/setup/windows-environment/page.mdx
+++ b/app/en/get-started/setup/windows-environment/page.mdx
@@ -289,6 +289,6 @@ are using WSL or Git Bash with Homebrew.
 
 ## Next steps
 
-- [Get an API key](/get-started/setup/api-keys)
-- [Run the MCP server quickstart](/get-started/quickstarts/mcp-server-quickstart)
-- [Browse the Arcade CLI reference](/references/arcade-cli)
+- [Get an API key](/en/get-started/setup/api-keys)
+- [Run the MCP server quickstart](/en/get-started/quickstarts/mcp-server-quickstart)
+- [Browse the Arcade CLI reference](/en/references/arcade-cli)
diff --git a/app/en/guides/audit-logs/page.mdx b/app/en/guides/audit-logs/page.mdx
index 681e56721..edff0b276 100644
--- a/app/en/guides/audit-logs/page.mdx
+++ b/app/en/guides/audit-logs/page.mdx
@@ -7,7 +7,7 @@ description: "Arcade.dev now captures every administrative action across the pla
 
 TL;DR: Arcade.dev captures every administrative action across the runtime automatically — who did it, how, what changed, and when. There's nothing to enable. Audit logs are on by default, with a filterable dashboard and a REST API for pulling data into your own systems.
 
-![Audit Log Dashboard](/images/screenshots/audit-log.png)
+![Audit Log Dashboard](/en/images/screenshots/audit-log.png)
 
 If you want audit events outside the dashboard, there's a REST API. You can pull logs programmatically to feed into your existing SIEM, compliance tooling, or internal reporting.
 
diff --git a/app/en/guides/contextual-access/build-your-own/page.mdx b/app/en/guides/contextual-access/build-your-own/page.mdx
index b9a88f989..e2622319f 100644
--- a/app/en/guides/contextual-access/build-your-own/page.mdx
+++ b/app/en/guides/contextual-access/build-your-own/page.mdx
@@ -13,7 +13,7 @@ The canonical contract is maintained in the [ArcadeAI/schemas](https://github.co
 
 - **OpenAPI 3.0 spec:** [logic_extensions/http/1.0/schema.yaml](https://github.com/ArcadeAI/schemas/blob/main/logic_extensions/http/1.0/schema.yaml)
 
-You can browse it interactively on the [API Reference](/references/contextual-access-webhook-api) page.
+You can browse it interactively on the [API Reference](/en/references/contextual-access-webhook-api) page.
 
 ## Generate server stubs
 
@@ -120,7 +120,7 @@ Tools can include an optional `metadata` field with classification, behavioral,
 
 All metadata fields are optional and omitted from the JSON when empty, so existing webhook servers continue to work without changes.
 
-For the full list of valid `service_domains` and `operations` values, see [Add Tool Metadata](/guides/create-tools/tool-basics/add-tool-metadata).
+For the full list of valid `service_domains` and `operations` values, see [Add Tool Metadata](/en/guides/create-tools/tool-basics/add-tool-metadata).
 
 ### Structure
 
@@ -232,6 +232,6 @@ Configure the auth method when creating your extension in the Dashboard.
 
 ## Next steps
 
-- [API Reference](/references/contextual-access-webhook-api) — Interactive Swagger documentation for the full schema
-- [Run an extension](/guides/contextual-access/examples) — Try the open-source example servers as reference
-- [How Hooks Work](/guides/contextual-access/how-hooks-work) — Understand execution order, phases, and failure modes
+- [API Reference](/en/references/contextual-access-webhook-api) — Interactive Swagger documentation for the full schema
+- [Run an extension](/en/guides/contextual-access/examples) — Try the open-source example servers as reference
+- [How Hooks Work](/en/guides/contextual-access/how-hooks-work) — Understand execution order, phases, and failure modes
diff --git a/app/en/guides/contextual-access/examples/page.mdx b/app/en/guides/contextual-access/examples/page.mdx
index cde0fe0b6..58e5df6f7 100644
--- a/app/en/guides/contextual-access/examples/page.mdx
+++ b/app/en/guides/contextual-access/examples/page.mdx
@@ -75,9 +75,9 @@ Once your server is running:
 2. Click **Create Extension** and enter your server's base URL and endpoint paths
 4. Create **hook configurations** to attach the extension to the hook points you want
 
-See [How Hooks Work](/guides/contextual-access/how-hooks-work) for details on configuring extensions and hook points.
+See [How Hooks Work](/en/guides/contextual-access/how-hooks-work) for details on configuring extensions and hook points.
 
 ## Next steps
 
-- [Build your own](/guides/contextual-access/build-your-own) — Implement the webhook contract in any language
-- [API Reference](/references/contextual-access-webhook-api) — Interactive schema documentation for the webhook contract
+- [Build your own](/en/guides/contextual-access/build-your-own) — Implement the webhook contract in any language
+- [API Reference](/en/references/contextual-access-webhook-api) — Interactive schema documentation for the webhook contract
diff --git a/app/en/guides/contextual-access/how-hooks-work/page.mdx b/app/en/guides/contextual-access/how-hooks-work/page.mdx
index 414217f43..d413f5e13 100644
--- a/app/en/guides/contextual-access/how-hooks-work/page.mdx
+++ b/app/en/guides/contextual-access/how-hooks-work/page.mdx
@@ -87,6 +87,6 @@ You configure extensions and hook points from the **Arcade Dashboard**:
 
 ## Next steps
 
-- [Run an extension](/guides/contextual-access/examples) — Try the open-source example servers
-- [Build your own](/guides/contextual-access/build-your-own) — Implement the webhook contract from the OpenAPI spec
-- [API Reference](/references/contextual-access-webhook-api) — Interactive schema documentation for the webhook contract
+- [Run an extension](/en/guides/contextual-access/examples) — Try the open-source example servers
+- [Build your own](/en/guides/contextual-access/build-your-own) — Implement the webhook contract from the OpenAPI spec
+- [API Reference](/en/references/contextual-access-webhook-api) — Interactive schema documentation for the webhook contract
diff --git a/app/en/guides/contextual-access/page.mdx b/app/en/guides/contextual-access/page.mdx
index 229542906..f515c4be7 100644
--- a/app/en/guides/contextual-access/page.mdx
+++ b/app/en/guides/contextual-access/page.mdx
@@ -22,7 +22,7 @@ You connect your own access-control, compliance, or transformation logic to the
 
 Contextual access is powered by **Logic Extensions**, a framework that allows you to hook in and add logic directly to Arcade's execution flow. Arcade calls your server at three predefined hook points in the tool lifecycle:
 
-![Contextual Access Flow Diagram](/images/logic-extensions/flow_diagram.png)
+![Contextual Access Flow Diagram](/en/images/logic-extensions/flow_diagram.png)
 
 | Hook point | When it runs | What it can do |
 | --- | --- | --- |
@@ -37,18 +37,18 @@ You only implement the hooks you need. Configure everything through the Dashboar
 <Cards>
   <Cards.Card
     title="How Hooks Work"
-    href="/guides/contextual-access/how-hooks-work"
+    href="/en/guides/contextual-access/how-hooks-work"
   />
   <Cards.Card
     title="Run an Extension"
-    href="/guides/contextual-access/examples"
+    href="/en/guides/contextual-access/examples"
   />
   <Cards.Card
     title="Build Your Own"
-    href="/guides/contextual-access/build-your-own"
+    href="/en/guides/contextual-access/build-your-own"
   />
   <Cards.Card
     title="API Reference"
-    href="/references/contextual-access-webhook-api"
+    href="/en/references/contextual-access-webhook-api"
   />
 </Cards>
diff --git a/app/en/guides/create-tools/error-handling/useful-tool-errors/page.mdx b/app/en/guides/create-tools/error-handling/useful-tool-errors/page.mdx
index 3f433cbcb..c78b44e7a 100644
--- a/app/en/guides/create-tools/error-handling/useful-tool-errors/page.mdx
+++ b/app/en/guides/create-tools/error-handling/useful-tool-errors/page.mdx
@@ -102,7 +102,7 @@ def search_posts(
     # ... rest of implementation
 ```
 
-Learn more about [RetryableToolError](/guides/create-tools/error-handling/retry-tools).
+Learn more about [RetryableToolError](/en/guides/create-tools/error-handling/retry-tools).
 
 ### ContextRequiredToolError
 
@@ -234,4 +234,4 @@ This will raise a `ToolOutputError` because the return type doesn't match the an
 
 ## Handling tool errors in agents
 
-To learn more about how to handle tool errors in your Agent, see the [Use Tools](/guides/tool-calling/error-handling) section.
+To learn more about how to handle tool errors in your Agent, see the [Use Tools](/en/guides/tool-calling/error-handling) section.
diff --git a/app/en/guides/create-tools/evaluate-tools/capture-mode/page.mdx b/app/en/guides/create-tools/evaluate-tools/capture-mode/page.mdx
index 7f48a4912..219156c03 100644
--- a/app/en/guides/create-tools/evaluate-tools/capture-mode/page.mdx
+++ b/app/en/guides/create-tools/evaluate-tools/capture-mode/page.mdx
@@ -383,7 +383,7 @@ ExpectedMCPToolCall("GetWeather", {"location": "Tokyo", "units": "celsius"})
 
 ### Step 3: Add critics
 
-Add critics to validate parameters. See [Critics](/guides/create-tools/evaluate-tools/create-evaluation-suite#critics) for options.
+Add critics to validate parameters. See [Critics](/en/guides/create-tools/evaluate-tools/create-evaluation-suite#critics) for options.
 
 ### Step 4: Run evaluations
 
@@ -441,5 +441,5 @@ suite = EvalSuite(
 
 ## Next steps
 
-- Learn about [comparative evaluations](/guides/create-tools/evaluate-tools/comparative-evaluations) to compare tool sources
-- [Create evaluation suites](/guides/create-tools/evaluate-tools/create-evaluation-suite) with expectations
+- Learn about [comparative evaluations](/en/guides/create-tools/evaluate-tools/comparative-evaluations) to compare tool sources
+- [Create evaluation suites](/en/guides/create-tools/evaluate-tools/create-evaluation-suite) with expectations
diff --git a/app/en/guides/create-tools/evaluate-tools/comparative-evaluations/page.mdx b/app/en/guides/create-tools/evaluate-tools/comparative-evaluations/page.mdx
index 43df3d504..9c093d560 100644
--- a/app/en/guides/create-tools/evaluate-tools/comparative-evaluations/page.mdx
+++ b/app/en/guides/create-tools/evaluate-tools/comparative-evaluations/page.mdx
@@ -522,7 +522,7 @@ Combine comparative tracks with multiple models:
 arcade evals . -p openai:gpt-4o,gpt-4o-mini -p anthropic:claude-sonnet-4-5-20250929
 ```
 
-Multi-run flags (`--num-runs`, `--seed`, `--multi-run-pass-rule`) also work with comparative tracks. See [Run evaluations](/guides/create-tools/evaluate-tools/run-evaluations).
+Multi-run flags (`--num-runs`, `--seed`, `--multi-run-pass-rule`) also work with comparative tracks. See [Run evaluations](/en/guides/create-tools/evaluate-tools/run-evaluations).
 
 Results show:
 
@@ -752,6 +752,6 @@ suite.add_tool_catalog(catalog_v2, track="Python v2")
 
 ## Next steps
 
-- [Create an evaluation suite](/guides/create-tools/evaluate-tools/create-evaluation-suite) with tracks
-- Use [capture mode](/guides/create-tools/evaluate-tools/capture-mode) to discover track-specific tool calls
-- [Run evaluations](/guides/create-tools/evaluate-tools/run-evaluations) with multiple models and tracks
+- [Create an evaluation suite](/en/guides/create-tools/evaluate-tools/create-evaluation-suite) with tracks
+- Use [capture mode](/en/guides/create-tools/evaluate-tools/capture-mode) to discover track-specific tool calls
+- [Run evaluations](/en/guides/create-tools/evaluate-tools/run-evaluations) with multiple models and tracks
diff --git a/app/en/guides/create-tools/evaluate-tools/create-evaluation-suite/page.mdx b/app/en/guides/create-tools/evaluate-tools/create-evaluation-suite/page.mdx
index 3a4ab66fd..7180ad68e 100644
--- a/app/en/guides/create-tools/evaluate-tools/create-evaluation-suite/page.mdx
+++ b/app/en/guides/create-tools/evaluate-tools/create-evaluation-suite/page.mdx
@@ -13,7 +13,7 @@ import { Steps, Tabs, Callout } from "nextra/components";
 
 ### Prerequisites
 
-- [Create an MCP Server](/guides/create-tools/tool-basics/build-mcp-server)
+- [Create an MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server)
 - Install the evaluation dependencies:
 
 <Tabs items={["uv", "pip"]} storageKey="packageManager">
@@ -164,7 +164,7 @@ arcade evals . --num-runs 3 --seed random --multi-run-pass-rule majority
   </Tabs.Tab>
 </Tabs>
 
-See [Run evaluations](/guides/create-tools/evaluate-tools/run-evaluations) for all available options.
+See [Run evaluations](/en/guides/create-tools/evaluate-tools/run-evaluations) for all available options.
 
 ### Understand the results
 
@@ -380,6 +380,6 @@ If you want stricter suites, increase thresholds (for example `fail_threshold=0.
 
 ## Next steps
 
-- Learn how to [run evaluations with different providers](/guides/create-tools/evaluate-tools/run-evaluations)
-- Explore [capture mode](/guides/create-tools/evaluate-tools/capture-mode) to record tool calls
-- Compare tool sources with [comparative evaluations](/guides/create-tools/evaluate-tools/comparative-evaluations)
+- Learn how to [run evaluations with different providers](/en/guides/create-tools/evaluate-tools/run-evaluations)
+- Explore [capture mode](/en/guides/create-tools/evaluate-tools/capture-mode) to record tool calls
+- Compare tool sources with [comparative evaluations](/en/guides/create-tools/evaluate-tools/comparative-evaluations)
diff --git a/app/en/guides/create-tools/evaluate-tools/run-evaluations/page.mdx b/app/en/guides/create-tools/evaluate-tools/run-evaluations/page.mdx
index 4826c7d27..cc6f4a1b8 100644
--- a/app/en/guides/create-tools/evaluate-tools/run-evaluations/page.mdx
+++ b/app/en/guides/create-tools/evaluate-tools/run-evaluations/page.mdx
@@ -151,7 +151,7 @@ Capture mode is useful for:
 - Debugging model behavior
 - Understanding tool call patterns
 
-See [Capture mode](/guides/create-tools/evaluate-tools/capture-mode) for details.
+See [Capture mode](/en/guides/create-tools/evaluate-tools/capture-mode) for details.
 
 ## Output formats
 
@@ -497,5 +497,5 @@ Ensure your evaluation files:
 
 ## Next steps
 
-- Explore [capture mode](/guides/create-tools/evaluate-tools/capture-mode) for recording tool calls
-- Learn about [comparative evaluations](/guides/create-tools/evaluate-tools/comparative-evaluations) for comparing tool sources
\ No newline at end of file
+- Explore [capture mode](/en/guides/create-tools/evaluate-tools/capture-mode) for recording tool calls
+- Learn about [comparative evaluations](/en/guides/create-tools/evaluate-tools/comparative-evaluations) for comparing tool sources
\ No newline at end of file
diff --git a/app/en/guides/create-tools/evaluate-tools/why-evaluate/page.mdx b/app/en/guides/create-tools/evaluate-tools/why-evaluate/page.mdx
index b1a2fc506..297dc32ec 100644
--- a/app/en/guides/create-tools/evaluate-tools/why-evaluate/page.mdx
+++ b/app/en/guides/create-tools/evaluate-tools/why-evaluate/page.mdx
@@ -65,10 +65,10 @@ FAILED Wrong tool selected -- Score: 50.00%
 
 ## Next steps
 
-- [Create an evaluation suite](/guides/create-tools/evaluate-tools/create-evaluation-suite) to start testing your tools
-- [Run evaluations](/guides/create-tools/evaluate-tools/run-evaluations) with multiple providers
-- Explore [capture mode](/guides/create-tools/evaluate-tools/capture-mode) to bootstrap test expectations
-- Compare tool sources with [comparative evaluations](/guides/create-tools/evaluate-tools/comparative-evaluations)
+- [Create an evaluation suite](/en/guides/create-tools/evaluate-tools/create-evaluation-suite) to start testing your tools
+- [Run evaluations](/en/guides/create-tools/evaluate-tools/run-evaluations) with multiple providers
+- Explore [capture mode](/en/guides/create-tools/evaluate-tools/capture-mode) to bootstrap test expectations
+- Compare tool sources with [comparative evaluations](/en/guides/create-tools/evaluate-tools/comparative-evaluations)
 
 ## Advanced features
 
@@ -76,12 +76,12 @@ Once you're comfortable with basic evaluations, explore these advanced capabilit
 
 ### Capture mode
 
-Record tool calls without scoring to discover what models actually call. Useful for bootstrapping test expectations and debugging. [Learn more →](/guides/create-tools/evaluate-tools/capture-mode)
+Record tool calls without scoring to discover what models actually call. Useful for bootstrapping test expectations and debugging. [Learn more →](/en/guides/create-tools/evaluate-tools/capture-mode)
 
 ### Comparative evaluations
 
-Test the same cases against different tool sources (tracks) with isolated registries. Compare how models perform with different tool implementations. [Learn more →](/guides/create-tools/evaluate-tools/comparative-evaluations)
+Test the same cases against different tool sources (tracks) with isolated registries. Compare how models perform with different tool implementations. [Learn more →](/en/guides/create-tools/evaluate-tools/comparative-evaluations)
 
 ### Output formats
 
-Save results in multiple formats (txt, md, html, json) for reporting and analysis. Specify output files with extensions or use no extension for all formats. [Learn more →](/guides/create-tools/evaluate-tools/run-evaluations#output-formats)
+Save results in multiple formats (txt, md, html, json) for reporting and analysis. Specify output files with extensions or use no extension for all formats. [Learn more →](/en/guides/create-tools/evaluate-tools/run-evaluations#output-formats)
diff --git a/app/en/guides/create-tools/improve/types-of-tools/page.mdx b/app/en/guides/create-tools/improve/types-of-tools/page.mdx
index bf3270e5e..72df74f01 100644
--- a/app/en/guides/create-tools/improve/types-of-tools/page.mdx
+++ b/app/en/guides/create-tools/improve/types-of-tools/page.mdx
@@ -10,7 +10,7 @@ Arcade offers two types of tools:
 - Unoptimized tools
 - Optimized tools
 
-The distinction is merely a matter of how Arcade designs them. Both types of tools can be used seamlessly in the same way. No difference exists in their interfaces, the way they are called, or how you interact with them through the Arcade [Dashboard](https://api.arcade.dev/dashboard/) or the Arcade [SDK clients](/references).
+The distinction is merely a matter of how Arcade designs them. Both types of tools can be used seamlessly in the same way. No difference exists in their interfaces, the way they are called, or how you interact with them through the Arcade [Dashboard](https://api.arcade.dev/dashboard/) or the Arcade [SDK clients](/en/references).
 
 Before we understand the two types, let's first understand the background for why we need to differentiate between them.
 
@@ -44,7 +44,7 @@ Even the most powerful LLMs usually perform poorly when they need to reason such
 
 Arcade's Optimized MCP Servers are designed to match the typical data models expected in AI-powered chat interfaces and are subject to evaluation suites to ensure LLMs can safely use them.
 
-Following the example above, our Slack MCP Server offers the [`Slack.SendMessage`](/resources/integrations/social/slack#slacksendmessage) tool, which accepts a `username` as argument, matching exactly both the action and argument value expected to be present in the LLM context window.
+Following the example above, our Slack MCP Server offers the [`Slack.SendMessage`](/en/resources/integrations/social/slack#slacksendmessage) tool, which accepts a `username` as argument, matching exactly both the action and argument value expected to be present in the LLM context window.
 
 When a user says "Send a DM to John asking about a project update", the LLM can directly call the `Slack.SendMessage` tool with the `username` argument, and the tool will take care of the rest.
 
diff --git a/app/en/guides/create-tools/migrate-toolkits/page.mdx b/app/en/guides/create-tools/migrate-toolkits/page.mdx
index e138cc410..16ba1ff57 100644
--- a/app/en/guides/create-tools/migrate-toolkits/page.mdx
+++ b/app/en/guides/create-tools/migrate-toolkits/page.mdx
@@ -11,12 +11,12 @@ This guide helps you migrate your existing Arcade toolkit to the new MCP Server
 
 <Callout type="info">
   If you're building a new MCP server from scratch, check out the [Create an MCP
-  Server](/guides/create-tools/tool-basics/build-mcp-server) guide instead.
+  Server](/en/guides/create-tools/tool-basics/build-mcp-server) guide instead.
 </Callout>
 <Callout type="info">
   If you're migrating an existing toolkit to a new MCP server, it may be useful
   to read through our quickstart guide to get a sense of the new MCP Server
-  framework: [Create an MCP Server](/guides/create-tools/tool-basics/build-mcp-server)
+  framework: [Create an MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server)
 </Callout>
 
 ## Understanding the changes
@@ -298,4 +298,4 @@ After migrating your toolkit to an MCP server:
 - **Test your server**: Run your server locally and verify all tools work correctly
 - **Update your CI/CD**: Update any automated workflows to use the new CLI and commands
 - **Deploy your server**: Use `arcade deploy` to deploy your MCP server
-- **Configure MCP clients**: Connect your server to [MCP clients](/guides/create-tools/tool-basics/call-tools-mcp) like Claude Desktop, Cursor, or VS Code
+- **Configure MCP clients**: Connect your server to [MCP clients](/en/guides/create-tools/tool-basics/call-tools-mcp) like Claude Desktop, Cursor, or VS Code
diff --git a/app/en/guides/create-tools/secure-your-server/page.mdx b/app/en/guides/create-tools/secure-your-server/page.mdx
index ab5362705..098b4fb14 100644
--- a/app/en/guides/create-tools/secure-your-server/page.mdx
+++ b/app/en/guides/create-tools/secure-your-server/page.mdx
@@ -9,7 +9,7 @@ When you `arcade deploy` your MCP server, it will be secured behind the Arcade p
 
 Under the hood, we disable the MCP routes provided by `arcade-mcp`, and use the Arcade Engine as a gateway for your MCP server, which has a number of additional features. Arcade will create a randomized secure secret for your MCP server (via the `ARCADE_WORKER_SECRET` environment variable) so that your server is protected from unauthorized access, as well as being isolated from direct access from outside of the Arcade platform. Servers managed by Arcade (servers that are `arcade deploy`ed) serve `/worker` endpoints that are protected by this secret. The worker endpoints are `worker/health`, `/worker/tools`, and `/worker/tools/invoke`. The health endpoint is not protected by this secret, but the listing tools and tool invocations are.  You can explore this behavior locally by setting the same environment variable in your local environment.
 
-Learn more about how to deploy your MCP server to Arcade [here](/guides/deployment-hosting/arcade-deploy).
+Learn more about how to deploy your MCP server to Arcade [here](/en/guides/deployment-hosting/arcade-deploy).
 
 ## OAuth Resource Server Auth
 
@@ -21,4 +21,4 @@ This approach is ideal when:
 
 Resource Server auth works alongside tool-level authorization. Resource Server auth secures access to the MCP server itself, while tool-level auth enables your tools to access third-party APIs on behalf of the authenticated user.
 
-Learn more about adding front-door OAuth to your MCP server [here](/guides/create-tools/secure-your-server/secure-your-mcp-server).
+Learn more about adding front-door OAuth to your MCP server [here](/en/guides/create-tools/secure-your-server/secure-your-mcp-server).
diff --git a/app/en/guides/create-tools/secure-your-server/secure-your-mcp-server/page.mdx b/app/en/guides/create-tools/secure-your-server/secure-your-mcp-server/page.mdx
index 5fbc4a94e..a091971a6 100644
--- a/app/en/guides/create-tools/secure-your-server/secure-your-mcp-server/page.mdx
+++ b/app/en/guides/create-tools/secure-your-server/secure-your-mcp-server/page.mdx
@@ -10,7 +10,7 @@ import { Steps, Tabs, Callout } from "nextra/components";
 You've built an MCP server with tools that require authorization or secrets. Now you want to deploy it over HTTP so others can use it. But how do you secure it so only authorized users can access your tools?
 
 <Callout type="info">
-**Want Arcade to handle this for you?** Use [`arcade deploy`](/guides/deployment-hosting/arcade-deploy) to deploy your MCP server to Arcade. We'll secure it automatically with no OAuth configuration on your end required. This guide is for self-hosted deployments where you manage your own authorization server.
+**Want Arcade to handle this for you?** Use [`arcade deploy`](/en/guides/deployment-hosting/arcade-deploy) to deploy your MCP server to Arcade. We'll secure it automatically with no OAuth configuration on your end required. This guide is for self-hosted deployments where you manage your own authorization server.
 </Callout>
 
 Resource Server auth enables your HTTP MCP server to act as an OAuth 2.1 Protected Resource (compliant with [MCP's specification for Authorization](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization)), validating Bearer tokens on every request. This unlocks support for tool-level authorization and secrets on HTTP servers, allowing you to host secure MCP servers anywhere (local, on-premise, or third-party hosted).
@@ -24,7 +24,7 @@ Add [MCP compliant OAuth 2.1 front-door authentication](https://modelcontextprot
 
 <GuideOverview.Prerequisites>
 
-- An existing MCP server created with `arcade new` (see [Create an MCP Server](/guides/create-tools/tool-basics/build-mcp-server))
+- An existing MCP server created with `arcade new` (see [Create an MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server))
 - Understanding of [MCP Authorization](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization)
 - An OAuth 2.1 compliant authorization server (e.g., WorkOS AuthKit, Auth0, Descope, etc.)
 - Authorization server's JWKS endpoint URL
@@ -480,6 +480,6 @@ AuthorizationServerEntry(
 
 ## Next Steps
 
-- **Let Arcade secure your server instead**: [Learn about `arcade deploy`](/guides/deployment-hosting/arcade-deploy)
-- **Build tools with authorization**: [Create tools that use OAuth](/guides/create-tools/tool-basics/create-tool-auth)
-- **Use secrets securely**: [Create tools with secrets](/guides/create-tools/tool-basics/create-tool-secrets)
+- **Let Arcade secure your server instead**: [Learn about `arcade deploy`](/en/guides/deployment-hosting/arcade-deploy)
+- **Build tools with authorization**: [Create tools that use OAuth](/en/guides/create-tools/tool-basics/create-tool-auth)
+- **Use secrets securely**: [Create tools with secrets](/en/guides/create-tools/tool-basics/create-tool-secrets)
diff --git a/app/en/guides/create-tools/tool-basics/add-tool-metadata/page.mdx b/app/en/guides/create-tools/tool-basics/add-tool-metadata/page.mdx
index 19725e770..98a794fb7 100644
--- a/app/en/guides/create-tools/tool-basics/add-tool-metadata/page.mdx
+++ b/app/en/guides/create-tools/tool-basics/add-tool-metadata/page.mdx
@@ -16,7 +16,7 @@ Annotate your tools with structured metadata so that MCP clients, policy engines
 
 <GuideOverview.Prerequisites>
 
-- [An MCP Server](/guides/create-tools/tool-basics/build-mcp-server)
+- [An MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server)
 
 </GuideOverview.Prerequisites>
 
@@ -230,6 +230,6 @@ Only set `strict=False` when you understand and accept the apparent contradictio
 
 ## Next steps
 
-- [Organize your MCP server and tools](/guides/create-tools/tool-basics/organize-mcp-tools) -- Structure your project as it grows
-- [Evaluate your tools](/guides/create-tools/evaluate-tools) -- Test tool reliability and performance
-- [Handle errors](/guides/create-tools/error-handling) -- Return useful errors from your tools
+- [Organize your MCP server and tools](/en/guides/create-tools/tool-basics/organize-mcp-tools) -- Structure your project as it grows
+- [Evaluate your tools](/en/guides/create-tools/evaluate-tools) -- Test tool reliability and performance
+- [Handle errors](/en/guides/create-tools/error-handling) -- Return useful errors from your tools
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 ba25bb178..4da33315c 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
@@ -24,7 +24,7 @@ Build and run a secure MCP server with tools that you define.
 
 <GuideOverview.YouWillLearn>
 
-- How to run MCP servers with Arcade tools using the [`arcade_mcp_server`](/references/mcp/python) package
+- How to run MCP servers with Arcade tools using the [`arcade_mcp_server`](/en/references/mcp/python) package
 - How to use `arcade new` from the `arcade-mcp` CLI to create your server project with all necessary files and dependencies.
 - How to run your local MCP Server with the Arcade CLI and register it with the Arcade Engine so that your agent can find and use your tool.
 
@@ -253,7 +253,7 @@ uv run server.py stdio
   a subprocess. Because of this, the server may run in a different environment
   and not have access to secrets defined in your local `.env` file. Please refer
   to the [create a tool with
-  secrets](/guides/create-tools/tool-basics/create-tool-secrets) guide for more
+  secrets](/en/guides/create-tools/tool-basics/create-tool-secrets) guide for more
   information.
 </Callout>
 
@@ -273,8 +273,8 @@ For HTTP transport, view your server's API docs at [http://127.0.0.1:8000/docs](
   API key and secrets in your MCP connection settings. Otherwise, if you intend
   to expose your HTTP MCP server to the public internet with tool-level
   authorization and secrets, please follow the [deploying to the cloud with
-  Arcade Deploy](/guides/deployment-hosting/arcade-deploy) guide or the [on-prem MCP
-  server](/guides/deployment-hosting/on-prem) guide for secure remote deployment.
+  Arcade Deploy](/en/guides/deployment-hosting/arcade-deploy) guide or the [on-prem MCP
+  server](/en/guides/deployment-hosting/on-prem) guide for secure remote deployment.
 </Callout>
 
 </Tabs.Tab>
@@ -347,8 +347,8 @@ That's it! Your MCP server is running and connected to your AI assistant.
 
 ### Next steps
 
-- **Create custom tools that use auth**: [Learn how to create tools with authorization](/guides/create-tools/tool-basics/create-tool-auth)
-- **Create custom tools that use secrets**: [Learn how to create tools with secrets](/guides/create-tools/tool-basics/create-tool-secrets)
-- **Learn the capabilities of the `Context` object**: [Understanding the Context object](/guides/create-tools/tool-basics/runtime-data-access)
-- **Evaluate your tools**: [Explore how to evaluate tool performance](/guides/create-tools/evaluate-tools/why-evaluate)
-- **Deploy your MCP server**: [Learn how to deploy your MCP server](/guides/deployment-hosting/arcade-deploy)
+- **Create custom tools that use auth**: [Learn how to create tools with authorization](/en/guides/create-tools/tool-basics/create-tool-auth)
+- **Create custom tools that use secrets**: [Learn how to create tools with secrets](/en/guides/create-tools/tool-basics/create-tool-secrets)
+- **Learn the capabilities of the `Context` object**: [Understanding the Context object](/en/guides/create-tools/tool-basics/runtime-data-access)
+- **Evaluate your tools**: [Explore how to evaluate tool performance](/en/guides/create-tools/evaluate-tools/why-evaluate)
+- **Deploy your MCP server**: [Learn how to deploy your MCP server](/en/guides/deployment-hosting/arcade-deploy)
diff --git a/app/en/guides/create-tools/tool-basics/call-tools-mcp/page.mdx b/app/en/guides/create-tools/tool-basics/call-tools-mcp/page.mdx
index dc0fdbe09..6fc45c998 100644
--- a/app/en/guides/create-tools/tool-basics/call-tools-mcp/page.mdx
+++ b/app/en/guides/create-tools/tool-basics/call-tools-mcp/page.mdx
@@ -17,8 +17,8 @@ Configure your MCP clients to call tools from your MCP server.
 <GuideOverview.Prerequisites>
 
 - <DashboardLink path="register" />
-- [Arcade CLI](/references/arcade-cli)
-- [An MCP Server](/guides/create-tools/tool-basics/build-mcp-server)
+- [Arcade CLI](/en/references/arcade-cli)
+- [An MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server)
 - [uv package manager](https://docs.astral.sh/uv/getting-started/installation/)
 
 </GuideOverview.Prerequisites>
@@ -329,7 +329,7 @@ Then, your MCP client's configuration file should look like this:
   should use the stdio transport and configure the Arcade API key and secrets in
   your MCP connection settings. If you intend to expose your HTTP MCP server to
   the public internet, please follow the [on-prem MCP
-  server](/guides/deployment-hosting/on-prem) guide for secure remote deployment.
+  server](/en/guides/deployment-hosting/on-prem) guide for secure remote deployment.
 </Callout>
 
 </Tabs.Tab>
diff --git a/app/en/guides/create-tools/tool-basics/compare-server-types/page.mdx b/app/en/guides/create-tools/tool-basics/compare-server-types/page.mdx
index bcae4e934..e4d24e5d8 100644
--- a/app/en/guides/create-tools/tool-basics/compare-server-types/page.mdx
+++ b/app/en/guides/create-tools/tool-basics/compare-server-types/page.mdx
@@ -10,8 +10,8 @@ Depending on the transport you use and where you want to run your MCP server, Ar
 | Transport | Deployment                                                                   | Tools without requirements | Tools with secrets | Tools with auth (single-user) | Tools with auth (multi-user) |
 | --------- | ---------------------------------------------------------------------------- | :------------------------: | :----------------: | :---------------------------: | :--------------------------: |
 | stdio     | local                                                                        |             ✅             |         ✅         |              ✅               |              ❌              |
-| http      | local ([unprotected](/resources/glossary#unprotected-mcp-servers))           |             ✅             |         ❌         |              ❌               |              ❌              |
-| http      | remote ([unprotected](/resources/glossary#unprotected-mcp-servers))          |             ✅             |         ❌         |              ❌               |              ❌              |
-| http      | local ([protected](/resources/glossary#protected-mcp-servers))               |             ✅             |         ✅         |              ✅               |              ✅              |
-| http      | remote ([protected](/resources/glossary#protected-mcp-servers))              |             ✅             |         ✅         |              ✅               |              ✅              |
+| http      | local ([unprotected](/en/resources/glossary#unprotected-mcp-servers))           |             ✅             |         ❌         |              ❌               |              ❌              |
+| http      | remote ([unprotected](/en/resources/glossary#unprotected-mcp-servers))          |             ✅             |         ❌         |              ❌               |              ❌              |
+| http      | local ([protected](/en/resources/glossary#protected-mcp-servers))               |             ✅             |         ✅         |              ✅               |              ✅              |
+| http      | remote ([protected](/en/resources/glossary#protected-mcp-servers))              |             ✅             |         ✅         |              ✅               |              ✅              |
 | http      | Arcade Cloud                                                                 |             ✅             |         ✅         |              ✅               |              ✅              |
diff --git a/app/en/guides/create-tools/tool-basics/create-tool-auth/page.mdx b/app/en/guides/create-tools/tool-basics/create-tool-auth/page.mdx
index 995919d2d..c8fea8e48 100644
--- a/app/en/guides/create-tools/tool-basics/create-tool-auth/page.mdx
+++ b/app/en/guides/create-tools/tool-basics/create-tool-auth/page.mdx
@@ -18,7 +18,7 @@ Create and use an MCP tool that requires OAuth to access Reddit, prompting users
 
 - <DashboardLink path="register" />
 - [uv package manager](https://docs.astral.sh/uv/getting-started/installation/)
-- [Create an MCP Server](/guides/create-tools/tool-basics/build-mcp-server)
+- [Create an MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server)
 
 </GuideOverview.Prerequisites>
 
@@ -42,7 +42,7 @@ When you create a tool with `requires_auth`, you specify which provider to use.
 2. If the tool's requirements are not met, Arcade initiates the provider-specific OAuth flow for the requested scopes.
     > 2a). The user is presented with a URL to complete the OAuth challenge. The user will need to visit this URL and log in and explicitly grant consent for the action to be performed on their behalf. This is the "OAuth challenge".
 
-    > 2b). The provider issues the token, and Arcade will securely inject it into the tool's [`Context`](/guides/create-tools/tool-basics/runtime-data-access) on its next invocation. The client and the LLM will never see the token.
+    > 2b). The provider issues the token, and Arcade will securely inject it into the tool's [`Context`](/en/guides/create-tools/tool-basics/runtime-data-access) on its next invocation. The client and the LLM will never see the token.
 
     > 2c). The tool needs to be re-invoked - this time its requirements will be met.
 3. The tool is executed, and uses the token injected into its `Context` to call the provider's API (e.g., `https://oauth.reddit.com`), without the LLM or client ever seeing the token.
@@ -76,7 +76,7 @@ app = MCPApp(name="auth_example", version="1.0.0", log_level="DEBUG")
 
 ### Define your MCP tool
 
-Now, define your tool using the `@app.tool` decorator and specify the required authorization, in this case, by using [Arcade's Reddit auth provider](/references/auth-providers/reddit).
+Now, define your tool using the `@app.tool` decorator and specify the required authorization, in this case, by using [Arcade's Reddit auth provider](/en/references/auth-providers/reddit).
 
 Specifying the `requires_auth` parameter in the `@app.tool` decorator indicates that the tool needs user authorization. In this example, we're using the `Reddit` auth provider with the `read` scope:
 
@@ -124,7 +124,7 @@ arcade login
 
 </Callout>
 
-Arcade offers a number of [built-in auth providers](/references/auth-providers), including Slack, Google, and GitHub. You can also require authorization with a custom auth provider, using the `OAuth2` class, a subclass of the `ToolAuthorization` class:
+Arcade offers a number of [built-in auth providers](/en/references/auth-providers), including Slack, Google, and GitHub. You can also require authorization with a custom auth provider, using the `OAuth2` class, a subclass of the `ToolAuthorization` class:
 
 ```python
 @app.tool(
@@ -274,7 +274,7 @@ async with httpx.AsyncClient() as client:
 
 - Try adding more authorized tools
 - Explore how to handle different authorization providers and scopes
-- Learn how to [build a tool with secrets](/guides/create-tools/tool-basics/create-tool-secrets)
+- Learn how to [build a tool with secrets](/en/guides/create-tools/tool-basics/create-tool-secrets)
 
 ## Example Code
 
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 337ff0a2b..4d92cbc29 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
@@ -17,8 +17,8 @@ Build an MCP tool that can read a secret from Context and return a masked confir
 <GuideOverview.Prerequisites>
 
 - <DashboardLink path="register" />
-- [Arcade CLI](/get-started/quickstarts/call-tool-agent)
-- [An MCP Server](/guides/create-tools/tool-basics/build-mcp-server)
+- [Arcade CLI](/en/get-started/quickstarts/call-tool-agent)
+- [An MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server)
 - [uv package manager](https://docs.astral.sh/uv/getting-started/installation/)
 
 </GuideOverview.Prerequisites>
@@ -160,7 +160,7 @@ $env:MY_SECRET_KEY="my-secret-value"
 When using the stdio transport, MCP clients typically launch the MCP server as a subprocess. Because of this, the server may run in a different environment and not have access to secrets defined in your local `.env` file or your terminal environment variables.
 
 To ensure your stdio MCP server has access to the secrets, you can either
-1. Utilize the [`arcade configure` CLI command](/references/arcade-cli) to configure your MCP client to pass the secrets to your MCP server, or
+1. Utilize the [`arcade configure` CLI command](/en/references/arcade-cli) to configure your MCP client to pass the secrets to your MCP server, or
 2. Manually configure your MCP client to pass the secrets to your MCP server. For example, if you are using Cursor IDE, you can add the following to your `mcp.json` file:
 
     ```json
@@ -195,7 +195,7 @@ Note that the specific key name may vary depending on the MCP client you are usi
   credentials, etc, and not to simply print a confirmation string.
 </Callout>
 
-In your [MCP Server](/guides/create-tools/tool-basics/build-mcp-server), create a new tool that uses the secret:
+In your [MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server), create a new tool that uses the secret:
 
 - Use the `requires_secrets` parameter to declare which secrets your tool needs (`"SECRET_KEY"` in this example).
 - The tool's Context object has a `get_secret` method that you can use to access the secret value.
@@ -312,8 +312,8 @@ For HTTP transport, view your server's API docs at [http://127.0.0.1:8000/docs](
   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 MCP connection settings. Otherwise, if you intend to expose your HTTP MCP server to
-  the public internet with tool-level authorization and secrets, please follow the [deploying to the cloud with Arcade Deploy](/guides/deployment-hosting/arcade-deploy) guide or the [on-prem MCP
-  server](/guides/deployment-hosting/on-prem) guide for secure remote deployment.
+  the public internet with tool-level authorization and secrets, please follow the [deploying to the cloud with Arcade Deploy](/en/guides/deployment-hosting/arcade-deploy) guide or the [on-prem MCP
+  server](/en/guides/deployment-hosting/on-prem) guide for secure remote deployment.
 </Callout>
 
 </Tabs.Tab>
diff --git a/app/en/guides/create-tools/tool-basics/organize-mcp-tools/page.mdx b/app/en/guides/create-tools/tool-basics/organize-mcp-tools/page.mdx
index 8eef9d1a8..9d3dd1d2b 100644
--- a/app/en/guides/create-tools/tool-basics/organize-mcp-tools/page.mdx
+++ b/app/en/guides/create-tools/tool-basics/organize-mcp-tools/page.mdx
@@ -17,7 +17,7 @@ Learn best practices for organizing your MCP server and tools, how to import too
 <GuideOverview.Prerequisites>
 
 - <DashboardLink path="register" />
-- [An MCP Server](/guides/create-tools/tool-basics/build-mcp-server)
+- [An MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server)
 - [uv package manager](https://docs.astral.sh/uv/getting-started/installation/)
 
 </GuideOverview.Prerequisites>
diff --git a/app/en/guides/create-tools/tool-basics/runtime-data-access/page.mdx b/app/en/guides/create-tools/tool-basics/runtime-data-access/page.mdx
index 61d1e01f8..79ecf92ae 100644
--- a/app/en/guides/create-tools/tool-basics/runtime-data-access/page.mdx
+++ b/app/en/guides/create-tools/tool-basics/runtime-data-access/page.mdx
@@ -292,5 +292,5 @@ For HTTP transport, view your server's API docs at [http://127.0.0.1:8000/docs](
 
 ### Next Steps
 
-- [Build a custom tool that requires user authorization](/guides/create-tools/tool-basics/create-tool-auth)
-- [Build a custom tool with secrets](/guides/create-tools/tool-basics/create-tool-secrets)
+- [Build a custom tool that requires user authorization](/en/guides/create-tools/tool-basics/create-tool-auth)
+- [Build a custom tool with secrets](/en/guides/create-tools/tool-basics/create-tool-secrets)
diff --git a/app/en/guides/deployment-hosting/arcade-cloud/page.mdx b/app/en/guides/deployment-hosting/arcade-cloud/page.mdx
index 8d883a58f..b333e0d3e 100644
--- a/app/en/guides/deployment-hosting/arcade-cloud/page.mdx
+++ b/app/en/guides/deployment-hosting/arcade-cloud/page.mdx
@@ -10,7 +10,7 @@ import { Callout } from "nextra/components";
 Arcade Cloud is Arcade's fully-managed SaaS platform: Arcade handles hosting, scaling, and operations so you can focus on building. This page covers the infrastructure behind Arcade Cloud, including networking, data storage, data protection, and sovereignty options.
 
 <Callout type="info">
-This page applies to **Arcade Cloud** only. If you self-host Arcade, you control your own infrastructure and data residency. See [on-premises deployment](/guides/deployment-hosting#on-premise-deployments) for details.
+This page applies to **Arcade Cloud** only. If you self-host Arcade, you control your own infrastructure and data residency. See [on-premises deployment](/en/guides/deployment-hosting#on-premise-deployments) for details.
 </Callout>
 
 ## Sovereignty
@@ -35,7 +35,7 @@ Traffic from Arcade Cloud exits from the following IP addresses:
 
 ## VPC peering
 
-VPC peering is available for enterprise customers upon request. If you want VPC peering, [contact Arcade](/resources/contact-us).
+VPC peering is available for enterprise customers upon request. If you want VPC peering, [contact Arcade](/en/resources/contact-us).
 
 ## Data storage
 
@@ -122,8 +122,8 @@ Training data is retained for up to 5 years, which is sufficient for model devel
 
 ### Regulated Customers
 
-If your organization has strict data residency requirements—for example, in financial services, healthcare, or government—or you operate within a legal regime that requires data storage in a specific country, you can deploy Arcade on-premises or in your preferred cloud region using a [self-hosted deployment](/guides/deployment-hosting#on-premise-deployments). This keeps all sensitive data within your own infrastructure.
+If your organization has strict data residency requirements—for example, in financial services, healthcare, or government—or you operate within a legal regime that requires data storage in a specific country, you can deploy Arcade on-premises or in your preferred cloud region using a [self-hosted deployment](/en/guides/deployment-hosting#on-premise-deployments). This keeps all sensitive data within your own infrastructure.
 
 ## Questions
 
-For compliance inquiries or data protection questions, [contact us](/resources/contact-us).
+For compliance inquiries or data protection questions, [contact us](/en/resources/contact-us).
diff --git a/app/en/guides/deployment-hosting/arcade-deploy/page.mdx b/app/en/guides/deployment-hosting/arcade-deploy/page.mdx
index 137a437c6..e1c5d7c47 100644
--- a/app/en/guides/deployment-hosting/arcade-deploy/page.mdx
+++ b/app/en/guides/deployment-hosting/arcade-deploy/page.mdx
@@ -21,7 +21,7 @@ This guide shows you how to deploy your MCP Server with Arcade Deploy.
 
 - <DashboardLink path="register" />
 - [uv package manager](https://docs.astral.sh/uv/getting-started/installation/)
-- [Create an MCP Server](/guides/create-tools/tool-basics/build-mcp-server)
+- [Create an MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server)
 
 </GuideOverview.Prerequisites>
 
@@ -60,7 +60,7 @@ This guide shows you how to deploy your MCP Server with Arcade Deploy.
 
 ## Create an MCP server using Arcade MCP
 
-If you have not created an MCP server yet, then follow the steps outlined in [this guide](/guides/create-tools/tool-basics/build-mcp-server) before deploying.
+If you have not created an MCP server yet, then follow the steps outlined in [this guide](/en/guides/create-tools/tool-basics/build-mcp-server) before deploying.
 
 ## Deploy your MCP Server
 
@@ -148,17 +148,17 @@ Navigate to the [Servers](https://api.arcade.dev/dashboard/servers) page in your
 - Test and execute all the tools
 - Manage users connected to the Auth providers
 - Manage the secrets for the server
-- Create [MCP Gateways](/guides/mcp-gateways)
+- Create [MCP Gateways](/en/guides/mcp-gateways)
 
 ## Create an MCP Gateway to call the tools in your MCP Server
 
-Once the MCP server is deployed to Arcade, all the tools in the server will be available in the [tool catalog](https://api.arcade.dev/dashboard/tools) page in your Arcade dashboard. To call the tools from an MCP client, you first need to [create an MCP Gateway](/guides/mcp-gateways) to pick and choose which tools you want to use in your MCP clients.
+Once the MCP server is deployed to Arcade, all the tools in the server will be available in the [tool catalog](https://api.arcade.dev/dashboard/tools) page in your Arcade dashboard. To call the tools from an MCP client, you first need to [create an MCP Gateway](/en/guides/mcp-gateways) to pick and choose which tools you want to use in your MCP clients.
 
 When creating an MCP gateway, you can select the tools you want to include in the Gateway from any MCP Servers available to the project, including the one you just deployed.
 
 ## Use Arcade clients to call the tools in your MCP Server
 
-You can use any of the available [Arcade clients](/references) to call the tools in your MCP Server. When using the clients, you are not required to create an MCP Gateway, as the client will handle the connection to all tools in your Arcade project directly.
+You can use any of the available [Arcade clients](/en/references) to call the tools in your MCP Server. When using the clients, you are not required to create an MCP Gateway, as the client will handle the connection to all tools in your Arcade project directly.
 
 </Steps>
 
diff --git a/app/en/guides/deployment-hosting/configure-engine/page.mdx b/app/en/guides/deployment-hosting/configure-engine/page.mdx
index a9d38cbba..ea1dcb8ff 100644
--- a/app/en/guides/deployment-hosting/configure-engine/page.mdx
+++ b/app/en/guides/deployment-hosting/configure-engine/page.mdx
@@ -77,12 +77,12 @@ export PATH=$PATH:/path/to/your/binary
   docker run -d -p 9099:9099 -v ./engine.yaml:/bin/engine.yaml ghcr.io/arcadeai/engine:latest
   ```
 
-  where config.yaml is the path to the [configuration file](/guides/deployment-hosting/configure-engine).
+  where config.yaml is the path to the [configuration file](/en/guides/deployment-hosting/configure-engine).
   </Tabs.Tab>
 </Tabs>
 
 The Homebrew tab is macOS-only. For native Windows environments, use Docker for
-Arcade Engine. For Arcade CLI setup on Windows, see [Windows environment setup](/get-started/setup/windows-environment).
+Arcade Engine. For Arcade CLI setup on Windows, see [Windows environment setup](/en/get-started/setup/windows-environment).
 
 Arcade uses configuration files to manage engine settings and default values. When you install the Arcade Engine, two files are created:
 - The `engine.yaml` file for engine configuration.
@@ -91,7 +91,7 @@ Let's explore each file to understand their purpose and how to locate them.
 
 ## Engine configuration file
 
-The `engine.yaml` file controls Arcade Engine settings. It supports variable expansion so you can integrate secrets and environment values seamlessly. You can customize this file to suit your setup. For more details, check the [Engine Configuration](/guides/deployment-hosting/configure-engine) page.
+The `engine.yaml` file controls Arcade Engine settings. It supports variable expansion so you can integrate secrets and environment values seamlessly. You can customize this file to suit your setup. For more details, check the [Engine Configuration](/en/guides/deployment-hosting/configure-engine) page.
 
 Choose your installation method to view the default location of `engine.yaml`:
 
@@ -110,7 +110,7 @@ Choose your installation method to view the default location of `engine.yaml`:
   ```bash
   $HOME/.arcade/engine.yaml
   ```
-  <Callout type="info">To manually download the engine.yaml, you can get an example from the [Configuration Templates](/guides/deployment-hosting/configure-engine#engineyaml) and add it to `$HOME/.arcade/engine.yaml`.</Callout>
+  <Callout type="info">To manually download the engine.yaml, you can get an example from the [Configuration Templates](/en/guides/deployment-hosting/configure-engine#engineyaml) and add it to `$HOME/.arcade/engine.yaml`.</Callout>
   </Tabs.Tab>
 </Tabs>
 
@@ -135,7 +135,7 @@ Select your installation method below to see the default path for `engine.env`:
   ```bash
   $HOME/.arcade/engine.env
   ```
-  <Callout type="info">To manually download the `engine.env`, refer to the [Configuration Templates](/guides/deployment-hosting/configure-engine#engineenv).</Callout>
+  <Callout type="info">To manually download the `engine.env`, refer to the [Configuration Templates](/en/guides/deployment-hosting/configure-engine#engineenv).</Callout>
   </Tabs.Tab>
 </Tabs>
 
@@ -237,11 +237,11 @@ For local development, set `api.development = true`.
 
 ## Auth configuration
 
-Arcade Engine manages auth for [AI tools](/guides/tool-calling/custom-apps/auth-tool-calling) and [direct API calls](/guides/tool-calling/call-third-party-apis). It supports many built-in [auth providers](/references/auth-providers), and can also connect to any [OAuth 2.0](/references/auth-providers/oauth2) authorization server.
+Arcade Engine manages auth for [AI tools](/en/guides/tool-calling/custom-apps/auth-tool-calling) and [direct API calls](/en/guides/tool-calling/call-third-party-apis). It supports many built-in [auth providers](/en/references/auth-providers), and can also connect to any [OAuth 2.0](/en/references/auth-providers/oauth2) authorization server.
 
 The `auth.providers` section defines the providers that users can authorize with. Each provider must have a unique `id` in the array. There are two ways to configure a provider:
 
-For [built-in providers](/references/auth-providers), use the `provider_id` field to reference the pre-built configuration. For example:
+For [built-in providers](/en/references/auth-providers), use the `provider_id` field to reference the pre-built configuration. For example:
 
 ```yaml
 auth:
@@ -255,7 +255,7 @@ auth:
       client_secret: ${env:GITHUB_CLIENT_SECRET}
 ```
 
-For custom OAuth 2.0 providers, specify the full connection details in the `oauth2` sub-section. For full documentation on the custom provider configuration, see the [OAuth 2.0 provider configuration](/references/auth-providers/oauth2) page.
+For custom OAuth 2.0 providers, specify the full connection details in the `oauth2` sub-section. For full documentation on the custom provider configuration, see the [OAuth 2.0 provider configuration](/en/references/auth-providers/oauth2) page.
 
 You can specify a mix of built-in and custom providers.
 
@@ -311,7 +311,7 @@ openssl rand -base64 32
 
 ### Default root key
 
-When you [install Arcade Engine locally](/guides/deployment-hosting/configure-engine), an `engine.env` file is created with a default root key:
+When you [install Arcade Engine locally](/en/guides/deployment-hosting/configure-engine), an `engine.env` file is created with a default root key:
 
 ```bash
 # Encryption keys (change this when deploying to production)
@@ -387,7 +387,7 @@ telemetry:
 
 ## Tools configuration
 
-Arcade Engine orchestrates [tools](/guides/tool-calling) that AI models can use.
+Arcade Engine orchestrates [tools](/en/guides/tool-calling) that AI models can use.
 
 The `tools.directors` section configures the mcp servers that are available to service tool calls:
 
diff --git a/app/en/guides/deployment-hosting/on-prem/page.mdx b/app/en/guides/deployment-hosting/on-prem/page.mdx
index 88bacd08d..a1950cf74 100644
--- a/app/en/guides/deployment-hosting/on-prem/page.mdx
+++ b/app/en/guides/deployment-hosting/on-prem/page.mdx
@@ -17,7 +17,7 @@ An on-premises MCP server deployment allows you to execute tools in your own env
 <GuideOverview.Prerequisites>
 
 - <DashboardLink path="register" />
-- [Arcade CLI](/get-started/quickstarts/call-tool-agent)
+- [Arcade CLI](/en/get-started/quickstarts/call-tool-agent)
 - [uv package manager](https://docs.astral.sh/uv/getting-started/installation/)
 
 </GuideOverview.Prerequisites>
@@ -56,7 +56,7 @@ The on-premises MCP server model uses a bidirectional connection between your lo
 
 ### Setup your MCP Servers
 
-Follow the [Creating a MCP Server](/guides/create-tools/tool-basics/build-mcp-server) guide to create your MCP Server.
+Follow the [Creating a MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server) guide to create your MCP Server.
 
 ### Start your local MCP Server
 
@@ -304,9 +304,9 @@ You can now test your MCP Server by making requests using the Playground, or an
 <Tabs.Tab>
 
 1. Use an app that supports MCP clients, like AI assistants and IDEs:
-   - [Visual Studio Code](/get-started/mcp-clients/visual-studio-code)
-   - [Claude Desktop](/get-started/mcp-clients/claude-desktop)
-   - [Cursor](/get-started/mcp-clients/cursor)
+   - [Visual Studio Code](/en/get-started/mcp-clients/visual-studio-code)
+   - [Claude Desktop](/en/get-started/mcp-clients/claude-desktop)
+   - [Cursor](/en/get-started/mcp-clients/cursor)
 1. Enable your MCP Server from the list of available MCP Servers
 1. Verify that the response is correct and you see request logs in your MCP Server
 
@@ -335,6 +335,6 @@ You can now test your MCP Server by making requests using the Playground, or an
 
 ## Next steps
 
-- [Create custom tools](/guides/create-tools/tool-basics/build-mcp-server) for your MCP Server
-- [Set up authentication](/guides/create-tools/tool-basics/create-tool-auth) for secure access to resources
-- [Configure secrets](/guides/create-tools/tool-basics/create-tool-secrets) for your MCP Server
+- [Create custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) for your MCP Server
+- [Set up authentication](/en/guides/create-tools/tool-basics/create-tool-auth) for secure access to resources
+- [Configure secrets](/en/guides/create-tools/tool-basics/create-tool-secrets) for your MCP Server
diff --git a/app/en/guides/deployment-hosting/page.mdx b/app/en/guides/deployment-hosting/page.mdx
index 014a9f491..65266462e 100644
--- a/app/en/guides/deployment-hosting/page.mdx
+++ b/app/en/guides/deployment-hosting/page.mdx
@@ -27,14 +27,14 @@ Connect on-premises MCP servers to Arcade Cloud for a hybrid deployment:
 - **Custom Dependencies**: Use specific runtime requirements or configurations
 - **Compliance**: Meet regulatory requirements while using Arcade's capabilities
 
-See [On-premise MCP Servers](/guides/deployment-hosting/on-prem) for more information about how to use your own MCP servers running anywhere, and see [Arcade Deploy](/guides/deployment-hosting/arcade-deploy) to learn how to deploy to Arcade Cloud.
+See [On-premise MCP Servers](/en/guides/deployment-hosting/on-prem) for more information about how to use your own MCP servers running anywhere, and see [Arcade Deploy](/en/guides/deployment-hosting/arcade-deploy) to learn how to deploy to Arcade Cloud.
 
 ### Customizing Auth
 
 You don't have to self-host Arcade to customize your auth experiences. Arcade Cloud supports a number of auth providers out of the box, and you can provide your own OAuth app credentials to brand your end-user experience. We recommend doing this for all production use cases, so that you can have isolated rate limits with the OAuth service provider and you can give your users a consistent experience when they go through an auth flow.
 You can still use the same tools when you customize your auth, no code changes are required.
 
-See [Customizing Auth](/references/auth-providers) for more information.
+See [Customizing Auth](/en/references/auth-providers) for more information.
 
 ### Arcade Cloud Pricing
 
@@ -47,7 +47,7 @@ Visit [https://api.arcade.dev](https://api.arcade.dev) for current pricing detai
 
 ## On-Premise Deployments
 
-Fully on-premise deployments of the Arcade platform are available! Arcade can be deployed on Kubernetes via our Helm chart and Docker images as part of our enterprise offering. [Contact us to learn more](/resources/contact-us).
+Fully on-premise deployments of the Arcade platform are available! Arcade can be deployed on Kubernetes via our Helm chart and Docker images as part of our enterprise offering. [Contact us to learn more](/en/resources/contact-us).
 
 The requirements for deploying Arcade on-premise are:
 
diff --git a/app/en/guides/logic-extensions/build-your-own/page.mdx b/app/en/guides/logic-extensions/build-your-own/page.mdx
index c906f8cfa..51091f30f 100644
--- a/app/en/guides/logic-extensions/build-your-own/page.mdx
+++ b/app/en/guides/logic-extensions/build-your-own/page.mdx
@@ -13,7 +13,7 @@ The canonical contract is maintained in the [ArcadeAI/schemas](https://github.co
 
 - **OpenAPI 3.0 spec:** [logic_extensions/http/1.0/schema.yaml](https://github.com/ArcadeAI/schemas/blob/main/logic_extensions/http/1.0/schema.yaml)
 
-You can browse it interactively on the [API Reference](/references/contextual-access-webhook-api) page.
+You can browse it interactively on the [API Reference](/en/references/contextual-access-webhook-api) page.
 
 ## Generate server stubs
 
@@ -120,7 +120,7 @@ Tools can include an optional `metadata` field with classification, behavioral,
 
 All metadata fields are optional and omitted from the JSON when empty, so existing webhook servers continue to work without changes.
 
-For the full list of valid `service_domains` and `operations` values, see [Add Tool Metadata](/guides/create-tools/tool-basics/add-tool-metadata).
+For the full list of valid `service_domains` and `operations` values, see [Add Tool Metadata](/en/guides/create-tools/tool-basics/add-tool-metadata).
 
 ### Structure
 
@@ -232,6 +232,6 @@ Configure the auth method when creating your extension in the Dashboard.
 
 ## Next steps
 
-- [API Reference](/references/contextual-access-webhook-api) — Interactive Swagger documentation for the full schema
-- [Run an extension](/guides/contextual-access/examples) — Try the open-source example servers as reference
-- [How Hooks Work](/guides/contextual-access/how-hooks-work) — Understand execution order, phases, and failure modes
+- [API Reference](/en/references/contextual-access-webhook-api) — Interactive Swagger documentation for the full schema
+- [Run an extension](/en/guides/contextual-access/examples) — Try the open-source example servers as reference
+- [How Hooks Work](/en/guides/contextual-access/how-hooks-work) — Understand execution order, phases, and failure modes
diff --git a/app/en/guides/mcp-gateways/add-remote-servers/page.mdx b/app/en/guides/mcp-gateways/add-remote-servers/page.mdx
index 12e28b8a6..f40c040fe 100644
--- a/app/en/guides/mcp-gateways/add-remote-servers/page.mdx
+++ b/app/en/guides/mcp-gateways/add-remote-servers/page.mdx
@@ -152,5 +152,5 @@ console.log(result);
 
 ## Next steps
 
-- [Create an MCP Gateway](/guides/mcp-gateways/create-via-dashboard)
-- [Connect to MCP clients](/get-started/mcp-clients)
+- [Create an MCP Gateway](/en/guides/mcp-gateways/create-via-dashboard)
+- [Connect to MCP clients](/en/get-started/mcp-clients)
diff --git a/app/en/guides/mcp-gateways/create-via-ai/page.mdx b/app/en/guides/mcp-gateways/create-via-ai/page.mdx
index 1f990486f..2fb51aa8b 100644
--- a/app/en/guides/mcp-gateways/create-via-ai/page.mdx
+++ b/app/en/guides/mcp-gateways/create-via-ai/page.mdx
@@ -18,7 +18,7 @@ Create and manage MCP gateways directly from your chat interface using natural l
 <GuideOverview.Prerequisites>
 
 1. Create an <SignupLink linkLocation="docs:gateway-assistant">Arcade account</SignupLink>
-2. An MCP-compatible chat client ([Cursor](/get-started/mcp-clients/cursor), [Claude Desktop](/get-started/mcp-clients/claude-desktop), [VS Code](/get-started/mcp-clients/visual-studio-code), etc.)
+2. An MCP-compatible chat client ([Cursor](/en/get-started/mcp-clients/cursor), [Claude Desktop](/en/get-started/mcp-clients/claude-desktop), [VS Code](/en/get-started/mcp-clients/visual-studio-code), etc.)
 
 </GuideOverview.Prerequisites>
 
@@ -40,7 +40,7 @@ https://ctl.arcade.dev/mcp
 The Gateway Assistant uses **Arcade Auth**. This means you'll authenticate with your Arcade account to access the assistant.
 </Callout>
 
-Each MCP client has a different setup process. See [Connect to MCP clients](/get-started/mcp-clients) for detailed instructions for adding the Gateway Assistant to Cursor, Claude Desktop, VS Code, and other supported clients with Arcade Auth.
+Each MCP client has a different setup process. See [Connect to MCP clients](/en/get-started/mcp-clients) for detailed instructions for adding the Gateway Assistant to Cursor, Claude Desktop, VS Code, and other supported clients with Arcade Auth.
 
 ### Authenticate
 
@@ -70,7 +70,7 @@ The assistant will select the appropriate tools from Arcade's catalog and create
 
 Once you've created a gateway, you'll need to add it to your chat client as a separate MCP server. The assistant will provide your new gateway's MCP URL (for example, `https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>`).
 
-Follow the same process you used to add the Gateway Assistant - see [Connect to MCP clients](/get-started/mcp-clients) for setup instructions specific to your client.
+Follow the same process you used to add the Gateway Assistant - see [Connect to MCP clients](/en/get-started/mcp-clients) for setup instructions specific to your client.
 
 <Callout type="info">
 The Gateway Assistant creates gateways that use **Arcade Auth** by default. This means you'll authenticate with your Arcade account to access the gateway. For production use cases with end users who don't have Arcade accounts, you can modify the gateway's authentication settings in the [dashboard](https://api.arcade.dev/dashboard/mcp-gateways).
diff --git a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx
index ad16b7198..7cf0d446a 100644
--- a/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx
+++ b/app/en/guides/mcp-gateways/create-via-dashboard/page.mdx
@@ -67,4 +67,4 @@ The options available when configuring an MCP Gateway are:
 
 Once you've created a gateway, you'll need to add it to your chat client. The assistant will provide the MCP URL (for example, `https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>`).
 
-See [Connect to MCP clients](/get-started/mcp-clients) for setup instructions specific to your client.
+See [Connect to MCP clients](/en/get-started/mcp-clients) for setup instructions specific to your client.
diff --git a/app/en/guides/mcp-gateways/page.mdx b/app/en/guides/mcp-gateways/page.mdx
index 39ad8408f..f21bf5858 100644
--- a/app/en/guides/mcp-gateways/page.mdx
+++ b/app/en/guides/mcp-gateways/page.mdx
@@ -25,11 +25,11 @@ You can create an MCP Gateway in two ways:
 <Cards>
   <Cards.Card
     title="Create via Dashboard"
-    href="/guides/mcp-gateways/create-via-dashboard"
+    href="/en/guides/mcp-gateways/create-via-dashboard"
   />
   <Cards.Card
     title="Create via AI Assistant"
-    href="/guides/mcp-gateways/create-via-ai"
+    href="/en/guides/mcp-gateways/create-via-ai"
   />
 </Cards>
 
@@ -45,7 +45,7 @@ Use remote MCP servers when your tools live outside Arcade. Register the server
 <Cards>
   <Cards.Card
     title="Add remote MCP servers"
-    href="/guides/mcp-gateways/add-remote-servers"
+    href="/en/guides/mcp-gateways/add-remote-servers"
   />
 </Cards>
 
@@ -57,7 +57,7 @@ Any MCP client that supports the Streamable HTTP transport can use an Arcade MCP
 https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
 ```
 
-Learn how to [connect MCP Gateways to your preferred client](/get-started/mcp-clients).
+Learn how to [connect MCP Gateways to your preferred client](/en/get-started/mcp-clients).
 
 ## Authentication
 
@@ -68,9 +68,9 @@ MCP Gateways support two authentication modes:
 | **Arcade Auth (Recommended)** | Development, testing, internal use | Users authenticate with their Arcade account via OAuth |
 | **Arcade Headers** | Production when end-users shouldn't authenticate via Arcade | Pass `Authorization: Bearer {your_api_key}` header and `Arcade-User-ID` header with the end-user identifier |
 
-See [Create via Dashboard](/guides/mcp-gateways/create-via-dashboard) for detailed authentication configuration.
+See [Create via Dashboard](/en/guides/mcp-gateways/create-via-dashboard) for detailed authentication configuration.
 
 ## Next Steps
 
 - <SignupLink linkLocation="docs:mcp-gateways">Create an Arcade account</SignupLink> if you haven't already
-- [Browse available integrations](/resources/integrations) to see what tools you can add to your gateway
+- [Browse available integrations](/en/resources/integrations) to see what tools you can add to your gateway
diff --git a/app/en/guides/tool-calling/call-third-party-apis/page.mdx b/app/en/guides/tool-calling/call-third-party-apis/page.mdx
index cbf5e92b5..03dcf3938 100644
--- a/app/en/guides/tool-calling/call-third-party-apis/page.mdx
+++ b/app/en/guides/tool-calling/call-third-party-apis/page.mdx
@@ -21,7 +21,7 @@ This can be useful when you need to manage authorization flows in your applicati
 ### Prerequisites
 
 - Sign up for an <SignupLink linkLocation="docs:call-third-party-apis-directly">Arcade account</SignupLink> if you haven't already
-- Generate an [Arcade API key](/get-started/setup/api-keys) and take note of it
+- Generate an [Arcade API key](/en/get-started/setup/api-keys) and take note of it
 
 ### Install required libraries
 
@@ -320,7 +320,7 @@ For each item in the list/array, you could use the [`users.messages.get`](https:
 
 </Steps>
 
-<Callout type="info">Consider using the [Arcade Gmail MCP Server](/resources/integrations/productivity/gmail), which simplifies the process for retrieving email messages even further! The pattern described here is useful if you need to directly get a token to use with Google in other parts of your codebase.</Callout>
+<Callout type="info">Consider using the [Arcade Gmail MCP Server](/en/resources/integrations/productivity/gmail), which simplifies the process for retrieving email messages even further! The pattern described here is useful if you need to directly get a token to use with Google in other parts of your codebase.</Callout>
 
 ### How it works
 
@@ -330,4 +330,4 @@ Arcade handles the authorization challenges and tokens, simplifying the process
 
 ### Next steps
 
-Integrate this authorization flow into your application, and explore how you can manage different [auth providers](/references/auth-providers) and scopes.
+Integrate this authorization flow into your application, and explore how you can manage different [auth providers](/en/references/auth-providers) and scopes.
diff --git a/app/en/guides/tool-calling/custom-apps/auth-tool-calling/page.mdx b/app/en/guides/tool-calling/custom-apps/auth-tool-calling/page.mdx
index feb6dfb7c..6dae667bb 100644
--- a/app/en/guides/tool-calling/custom-apps/auth-tool-calling/page.mdx
+++ b/app/en/guides/tool-calling/custom-apps/auth-tool-calling/page.mdx
@@ -158,6 +158,6 @@ These APIs give you programmatic control over tool calling.
 
 ### Next steps
 
-Arcade also allows you to [build your own tools](/guides/create-tools/tool-basics/build-mcp-server) to integrate any custom functionality or API to your Agent or AI workflows.
+Arcade also allows you to [build your own tools](/en/guides/create-tools/tool-basics/build-mcp-server) to integrate any custom functionality or API to your Agent or AI workflows.
 
-Your tools can use the [service providers supported by Arcade](/references/auth-providers) or you can integrate with any [OAuth2-compatible service](/references/auth-providers/oauth2).
+Your tools can use the [service providers supported by Arcade](/en/references/auth-providers) or you can integrate with any [OAuth2-compatible service](/en/references/auth-providers/oauth2).
diff --git a/app/en/guides/tool-calling/error-handling/page.mdx b/app/en/guides/tool-calling/error-handling/page.mdx
index 2faf975c2..b726024b2 100644
--- a/app/en/guides/tool-calling/error-handling/page.mdx
+++ b/app/en/guides/tool-calling/error-handling/page.mdx
@@ -279,4 +279,4 @@ As of now, MCP Clients do not return structured error information, only an error
 
 ## Building tools with error handling
 
-To learn more about how to build tools with error handling, see the [Build Tools](/guides/create-tools/error-handling/useful-tool-errors) section.
+To learn more about how to build tools with error handling, see the [Build Tools](/en/guides/create-tools/error-handling/useful-tool-errors) section.
diff --git a/app/en/guides/tool-calling/page.mdx b/app/en/guides/tool-calling/page.mdx
index 9e349fb11..5bf9baa35 100644
--- a/app/en/guides/tool-calling/page.mdx
+++ b/app/en/guides/tool-calling/page.mdx
@@ -13,11 +13,11 @@ To solve this, many AI models support tool calling (sometimes referred to as 'fu
 
 Say a colleague shares a document with you on Google Drive, and you'd like an LLM to help you analyze it.
 
-You could go to your Drive/Docs, open the document, copy its contents, and paste it into your chat. But what if the LLM could do this for you? The Arcade Google Docs MCP Server provides a [`SearchAndRetrieveDocuments`](/resources/integrations/productivity/googledocs#googledocssearchandretrievedocuments) tool. By calling it, the LLM can find and read the document without you having to do anything.
+You could go to your Drive/Docs, open the document, copy its contents, and paste it into your chat. But what if the LLM could do this for you? The Arcade Google Docs MCP Server provides a [`SearchAndRetrieveDocuments`](/en/resources/integrations/productivity/googledocs#googledocssearchandretrievedocuments) tool. By calling it, the LLM can find and read the document without you having to do anything.
 
-After analyzing the document, you decide that a meeting is needed with your colleague. You can ask the LLM to schedule a meeting and it will use the [Google Calendar MCP Server](/resources/integrations/productivity/googlecalendar) to do it without you needing to leave the chat.
+After analyzing the document, you decide that a meeting is needed with your colleague. You can ask the LLM to schedule a meeting and it will use the [Google Calendar MCP Server](/en/resources/integrations/productivity/googlecalendar) to do it without you needing to leave the chat.
 
-Or you could ask the LLM to send a summary of the analysis to your colleague by email and it would use the [Gmail MCP Server](/resources/integrations/productivity/gmail) for that.
+Or you could ask the LLM to send a summary of the analysis to your colleague by email and it would use the [Gmail MCP Server](/en/resources/integrations/productivity/gmail) for that.
 
 ## Possibilities for Application and AI Agent developers
 
@@ -40,9 +40,9 @@ In the example above, when the user asks: "_help me analyze the 'Project XYZ' Go
 
 One challenge to make all that happen is authorization. How do you give the LLM permission to access someone's Google Docs and Gmail in a secure and convenient way?
 
-Arcade solves this problem by providing a standardized [interface for authorization](/get-started/about-arcade), as well as pre-built auth providers for [popular services](/references/auth-providers) such as Google, Dropbox, GitHub, Notion, and many more.
+Arcade solves this problem by providing a standardized [interface for authorization](/en/get-started/about-arcade), as well as pre-built auth providers for [popular services](/en/references/auth-providers) such as Google, Dropbox, GitHub, Notion, and many more.
 
-Our SDK also [allows you to integrate](/references/auth-providers/oauth2) LLMs with any OAuth 2.0-compliant API.
+Our SDK also [allows you to integrate](/en/references/auth-providers/oauth2) LLMs with any OAuth 2.0-compliant API.
 
 ## Tool Augmented Generation (TAG)
 
@@ -93,5 +93,5 @@ This process shows the general outline of the Tool Augmented Generation (TAG) pr
 
 ### Next steps
 
-- Explore the [MCP Servers](/resources/integrations) available on Arcade
-- Build your own [custom MCP Server](/guides/create-tools/tool-basics/build-mcp-server)
+- Explore the [MCP Servers](/en/resources/integrations) available on Arcade
+- Build your own [custom MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server)
diff --git a/app/en/guides/user-facing-agents/secure-auth-production/page.mdx b/app/en/guides/user-facing-agents/secure-auth-production/page.mdx
index 6ec6dbec2..f7d50c39b 100644
--- a/app/en/guides/user-facing-agents/secure-auth-production/page.mdx
+++ b/app/en/guides/user-facing-agents/secure-auth-production/page.mdx
@@ -36,7 +36,7 @@ The Arcade.dev user verifier helps keep your auth flows secure while you are bui
   If you are building a multi-user production app, you must obtain your own
   OAuth app credentials and add them to Arcade. For example, see our docs on
   [configuring Google auth in the Arcade
-  Dashboard](/references/auth-providers/google#access-the-arcade-dashboard).
+  Dashboard](/en/references/auth-providers/google#access-the-arcade-dashboard).
 </Callout>
 
 ## Build a custom user verifier
diff --git a/app/en/learn/server-level-vs-tool-level-auth/page.mdx b/app/en/learn/server-level-vs-tool-level-auth/page.mdx
index ebbbff919..831a675a0 100644
--- a/app/en/learn/server-level-vs-tool-level-auth/page.mdx
+++ b/app/en/learn/server-level-vs-tool-level-auth/page.mdx
@@ -11,13 +11,13 @@ Arcade MCP servers support two distinct layers of authorization that work togeth
 
 <Callout type="info">
   **Using `arcade deploy`?** If you deploy your MCP server with [`arcade
-  deploy`](/guides/deployment-hosting/arcade-deploy), Arcade handles
+  deploy`](/en/guides/deployment-hosting/arcade-deploy), Arcade handles
   server-level security for you automatically.
 </Callout>
 
 ## Quick Comparison
 
-| Aspect                | [Resource Server Auth (Front-Door)](/guides/create-tools/secure-your-server/secure-your-mcp-server) | [Tool-Level Authorization](/guides/create-tools/tool-basics/create-tool-auth) |
+| Aspect                | [Resource Server Auth (Front-Door)](/en/guides/create-tools/secure-your-server/secure-your-mcp-server) | [Tool-Level Authorization](/en/guides/create-tools/tool-basics/create-tool-auth) |
 | --------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
 | **What it secures**   | Access to your MCP server                                                    | Access to third-party APIs                                                    |
 | **Who authenticates** | The user calling your server                                                 | The user's access to external services                                        |
@@ -36,7 +36,7 @@ Resource Server auth ensures every request identifies the caller. It blocks unau
 
 ✅ **You need Resource Server auth if:**
 
-- You've determined that [arcade deploy](/guides/deployment-hosting/arcade-deploy) is not a good fit for your use case
+- You've determined that [arcade deploy](/en/guides/deployment-hosting/arcade-deploy) is not a good fit for your use case
 - You're running an HTTP MCP server in production
 - Your server has tools that require authorization or secrets
 - You need to identify which user is calling your server
@@ -44,7 +44,7 @@ Resource Server auth ensures every request identifies the caller. It blocks unau
 
 ❌ **You don't need it if:**
 
-- You're using [arcade deploy](/guides/deployment-hosting/arcade-deploy) to secure your server
+- You're using [arcade deploy](/en/guides/deployment-hosting/arcade-deploy) to secure your server
 - You're using stdio transport
 - Your server only has public tools (no auth/secrets required)
 - You're doing local development only
@@ -208,7 +208,7 @@ if __name__ == "__main__":
 
 ### Q: Can I use tool-level auth without Resource Server auth?
 
-**A:** Yes, but only for stdio transport or when using [arcade deploy](/guides/deployment-hosting/arcade-deploy) (Arcade will protect your MCP server for you).
+**A:** Yes, but only for stdio transport or when using [arcade deploy](/en/guides/deployment-hosting/arcade-deploy) (Arcade will protect your MCP server for you).
 
 ### Q: Do I need Resource Server auth for local development?
 
diff --git a/app/en/references/arcade-cli/page.mdx b/app/en/references/arcade-cli/page.mdx
index 7e848ff4b..e79ecbd44 100644
--- a/app/en/references/arcade-cli/page.mdx
+++ b/app/en/references/arcade-cli/page.mdx
@@ -36,7 +36,7 @@ In your terminal, run the following command to install the published `arcade-mcp
 </Tabs>
 
 <Callout type="info">
-  Using Windows and PowerShell? Follow the [Windows environment setup](/get-started/setup/windows-environment) guide for install options with and without `uv`.
+  Using Windows and PowerShell? Follow the [Windows environment setup](/en/get-started/setup/windows-environment) guide for install options with and without `uv`.
 </Callout>
 
 ## Upgrade the Arcade CLI
@@ -68,7 +68,7 @@ arcade --version
 ```
 
 <Callout type="info">
-If you previously had the `arcade-ai` package installed, you should uninstall it first. The old `arcade-ai` CLI has been replaced by `arcade-mcp`. See the [migration guide](/guides/create-tools/migrate-toolkits) for details on migrating from legacy toolkits.
+If you previously had the `arcade-ai` package installed, you should uninstall it first. The old `arcade-ai` CLI has been replaced by `arcade-mcp`. See the [migration guide](/en/guides/create-tools/migrate-toolkits) for details on migrating from legacy toolkits.
 </Callout>
 
 ### Re-authenticate after upgrading
diff --git a/app/en/references/auth-providers/airtable/page.mdx b/app/en/references/auth-providers/airtable/page.mdx
index c87d2452e..a3668062f 100644
--- a/app/en/references/auth-providers/airtable/page.mdx
+++ b/app/en/references/auth-providers/airtable/page.mdx
@@ -7,7 +7,7 @@ The Airtable auth provider enables tools and agents to call [Airtable APIs](http
 <Callout>
   Want to quickly get started with Airtable in your agent or AI app? The
   pre-built [Arcade Airtable MCP
-  Server](/resources/integrations/productivity/airtableapi) is what you want!
+  Server](/en/resources/integrations/productivity/airtableapi) is what you want!
 </Callout>
 
 ### What's documented here
@@ -16,7 +16,7 @@ This page describes how to use and configure Airtable auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Airtable MCP Server](/resources/integrations/productivity/airtableapi), which provides pre-built tools for interacting with Airtable
+- The [Arcade Airtable MCP Server](/en/resources/integrations/productivity/airtableapi), which provides pre-built tools for interacting with Airtable
 - Your [app code](#using-airtable-auth-in-app-code) that needs to call the Airtable API
 - Or, your [custom tools](#using-airtable-auth-in-custom-tools) that need to call the Airtable API
 
@@ -25,7 +25,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -115,7 +115,7 @@ Hit the **Create** button and the provider will be ready to be used.
 
 <Callout type="info">
   This method is only available when you are [self-hosting the
-  engine](/guides/deployment-hosting/on-prem)
+  engine](/en/guides/deployment-hosting/on-prem)
 </Callout>
 
 <Steps>
@@ -176,11 +176,11 @@ auth:
 </Tabs.Tab>
 </Tabs>
 
-When you use tools that require Airtable auth using your Arcade account credentials, Arcade will automatically use this Airtable OAuth provider. If you have multiple Airtable providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Airtable auth using your Arcade account credentials, Arcade will automatically use this Airtable OAuth provider. If you have multiple Airtable providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 ## Using Airtable auth in app code
 
-Use the Airtable auth provider in your own agents and AI apps to get a user token for the Airtable API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Airtable auth provider in your own agents and AI apps to get a user token for the Airtable API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Airtable API:
 
@@ -248,9 +248,9 @@ const token = authResponse.context.token;
 
 ## Using Airtable auth in custom tools
 
-You can use the pre-built [Arcade Airtable MCP Server](/resources/integrations/productivity/airtableapi) to quickly build agents and AI apps that interact with Airtable.
+You can use the pre-built [Arcade Airtable MCP Server](/en/resources/integrations/productivity/airtableapi) to quickly build agents and AI apps that interact with Airtable.
 
-If the pre-built tools in the Airtable MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Airtable API.
+If the pre-built tools in the Airtable MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Airtable API.
 
 Use the `OAuth2()` auth class to specify that a tool requires authorization with Airtable. The `context.authorization.token` field will be automatically populated with the user's Airtable token:
 
diff --git a/app/en/references/auth-providers/asana/page.mdx b/app/en/references/auth-providers/asana/page.mdx
index 80754dc88..600edcca3 100644
--- a/app/en/references/auth-providers/asana/page.mdx
+++ b/app/en/references/auth-providers/asana/page.mdx
@@ -6,7 +6,7 @@ The Asana auth provider enables tools and agents to call Asana APIs on behalf of
 
 <Callout>
   Want to quickly get started with Asana services in your agent or AI app? The
-  pre-built [Arcade Asana MCP Server](/resources/integrations/productivity/asana) is what you
+  pre-built [Arcade Asana MCP Server](/en/resources/integrations/productivity/asana) is what you
   want!
 </Callout>
 
@@ -16,7 +16,7 @@ This page describes how to use and configure Asana auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Asana MCP Server](/resources/integrations/productivity/asana), which provides pre-built tools for interacting with Asana
+- The [Arcade Asana MCP Server](/en/resources/integrations/productivity/asana), which provides pre-built tools for interacting with Asana
 - Your [app code](#using-asana-auth-in-app-code) that needs to call Asana APIs
 - Or, your [custom tools](#using-asana-auth-in-custom-tools) that need to call Asana APIs
 
@@ -24,14 +24,14 @@ This auth provider is used by:
 
 Arcade offers a default Asana auth provider that you can use in the Arcade Cloud Platform. In this case, your users will see `Arcade` as the name of the application that's requesting permission.
 
-If you choose to use Arcade's Asana auth, you don't need to configure anything. Follow the [Asana MCP Server examples](/resources/integrations/productivity/asana) to get started calling Asana tools.
+If you choose to use Arcade's Asana auth, you don't need to configure anything. Follow the [Asana MCP Server examples](/en/resources/integrations/productivity/asana) to get started calling Asana tools.
 
 ## Use Your Own Asana App Credentials
 
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -99,20 +99,20 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Asana auth using your Arcade account credentials, Arcade will automatically use this Asana OAuth provider. If you have multiple Asana providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Asana auth using your Arcade account credentials, Arcade will automatically use this Asana OAuth provider. If you have multiple Asana providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using the Arcade Asana MCP Servers
 
-The [Arcade Asana MCP Server](/resources/integrations/productivity/asana) provides tools to interact with various Asana objects, such as tasks, projects, teams, and users.
+The [Arcade Asana MCP Server](/en/resources/integrations/productivity/asana) provides tools to interact with various Asana objects, such as tasks, projects, teams, and users.
 
-Refer to the [MCP Server documentation and examples](/resources/integrations/productivity/asana) to learn how to use the MCP Server to build agents and AI apps that interact with Asana services.
+Refer to the [MCP Server documentation and examples](/en/resources/integrations/productivity/asana) to learn how to use the MCP Server to build agents and AI apps that interact with Asana services.
 
 ## Using Asana auth in app code
 
-Use the Asana auth provider in your own agents and AI apps to get a user-scoped token for the Asana API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Asana auth provider in your own agents and AI apps to get a user-scoped token for the Asana API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Asana API:
 
@@ -187,9 +187,9 @@ You can use the auth token to call the [Get multiple tasks endpoint](https://dev
 
 ## Using Asana auth in custom tools
 
-You can use the pre-built [Arcade Asana MCP Server](/resources/integrations/productivity/asana) to quickly build agents and AI apps that interact with Asana.
+You can use the pre-built [Arcade Asana MCP Server](/en/resources/integrations/productivity/asana) to quickly build agents and AI apps that interact with Asana.
 
-If the pre-built tools in the Asana MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with Asana API.
+If the pre-built tools in the Asana MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with Asana API.
 
 Use the `Asana()` auth class to specify that a tool requires authorization with Asana. The authentication token needed to call the Asana API is available in the tool context through the `context.get_auth_token_or_empty()` method.
 
diff --git a/app/en/references/auth-providers/atlassian/page.mdx b/app/en/references/auth-providers/atlassian/page.mdx
index 8114dbeab..f6eddc21a 100644
--- a/app/en/references/auth-providers/atlassian/page.mdx
+++ b/app/en/references/auth-providers/atlassian/page.mdx
@@ -24,7 +24,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -74,13 +74,13 @@ To access the Arcade Cloud dashboard, go to [api.arcade.dev/dashboard](https://a
 Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
-When you use tools that require Atlassian auth using your Arcade account credentials, Arcade will automatically use this Atlassian OAuth provider. If you have multiple Atlassian providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Atlassian auth using your Arcade account credentials, Arcade will automatically use this Atlassian OAuth provider. If you have multiple Atlassian providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 ## Using Atlassian auth in app code
 
-Use the Atlassian auth provider in your own agents and AI apps to get a user token for the Atlassian API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Atlassian auth provider in your own agents and AI apps to get a user token for the Atlassian API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Atlassian API:
 
@@ -146,7 +146,7 @@ const token = authResponse.context.token;
 
 ## Using Atlassian auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Atlassian API.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Atlassian API.
 
 Use the `Atlassian()` auth class to specify that a tool requires authorization with Atlassian. The `context.authorization.token` field will be automatically populated with the user's Atlassian token:
 
diff --git a/app/en/references/auth-providers/attio/page.mdx b/app/en/references/auth-providers/attio/page.mdx
index 1bf9078d9..b0bd815af 100644
--- a/app/en/references/auth-providers/attio/page.mdx
+++ b/app/en/references/auth-providers/attio/page.mdx
@@ -6,7 +6,7 @@ The Attio auth provider enables tools and agents to call [Attio APIs](https://do
 
 <Callout>
   Want to quickly get started with Attio in your agent or AI app? The pre-built
-  [Arcade Attio MCP server](/resources/integrations/sales/attio) is what you
+  [Arcade Attio MCP server](/en/resources/integrations/sales/attio) is what you
   want.
 </Callout>
 
@@ -16,7 +16,7 @@ This page describes how to use and configure Attio auth with Arcade.
 
 Use this auth provider with:
 
-- The [Arcade Attio MCP server](/resources/integrations/sales/attio), which provides pre-built tools for interacting with Attio
+- The [Arcade Attio MCP server](/en/resources/integrations/sales/attio), which provides pre-built tools for interacting with Attio
 - Your [app code](#using-attio-auth-in-app-code) that needs to call Attio APIs
 - Or, your [custom tools](#using-attio-auth-in-custom-tools) that need to call Attio APIs
 
@@ -24,14 +24,14 @@ Use this auth provider with:
 
 Arcade offers a default Attio auth provider that you can use in the Arcade Cloud Platform. In this case, your users will see `Arcade` as the name of the application requesting permission.
 
-If you choose to use Arcade's Attio auth, you don't need to configure anything. Follow the [Attio MCP server examples](/resources/integrations/sales/attio) to get started calling Attio tools.
+If you choose to use Arcade's Attio auth, you don't need to configure anything. Follow the [Attio MCP server examples](/en/resources/integrations/sales/attio) to get started calling Attio tools.
 
 ## Use your own Attio app credentials
 
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -52,7 +52,7 @@ Before showing how to configure your Attio app credentials, we'll go through the
 - In your app's settings, navigate to the **OAuth** tab
 - Toggle **Enable OAuth 2.0** at the top of the page
 - Under **Redirect URIs**, add the redirect URL generated by Arcade (see below)
-- Under **Scopes**, enable the scopes your app needs. If you plan to use the [Arcade Attio MCP server](/resources/integrations/sales/attio), enable:
+- Under **Scopes**, enable the scopes your app needs. If you plan to use the [Arcade Attio MCP server](/en/resources/integrations/sales/attio), enable:
   - `call_recording:read`
   - `list_configuration:read-write`
   - `list_entry:read-write`
@@ -103,20 +103,20 @@ Hit the **Create** button and the provider will be ready for use.
 
 </Steps>
 
-When you use tools that require Attio auth using your Arcade account credentials, Arcade will automatically use this Attio OAuth provider. If you have multiple Attio providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Attio auth using your Arcade account credentials, Arcade will automatically use this Attio OAuth provider. If you have multiple Attio providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using the Arcade Attio MCP server
 
-The [Arcade Attio MCP server](/resources/integrations/sales/attio) provides tools to interact with Attio CRM objects, such as records, notes, tasks, lists, and meetings.
+The [Arcade Attio MCP server](/en/resources/integrations/sales/attio) provides tools to interact with Attio CRM objects, such as records, notes, tasks, lists, and meetings.
 
-Refer to the [MCP server documentation and examples](/resources/integrations/sales/attio) to learn how to use the MCP server to build agents and AI apps that interact with Attio.
+Refer to the [MCP server documentation and examples](/en/resources/integrations/sales/attio) to learn how to use the MCP server to build agents and AI apps that interact with Attio.
 
 ## Using Attio auth in app code
 
-Use the Attio auth provider in your own agents and AI apps to get a user-scoped token for the Attio API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Attio auth provider in your own agents and AI apps to get a user-scoped token for the Attio API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Attio API:
 
@@ -184,7 +184,7 @@ const token = authResponse.context.token;
 
 ## Using Attio auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Attio API.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Attio API.
 
 Use the `Attio()` auth class to specify that a tool requires authorization with Attio. The authentication token needed to call the Attio API is available in the tool context through the `context.get_auth_token_or_empty()` method.
 
diff --git a/app/en/references/auth-providers/calendly/page.mdx b/app/en/references/auth-providers/calendly/page.mdx
index f3214058e..12911629c 100644
--- a/app/en/references/auth-providers/calendly/page.mdx
+++ b/app/en/references/auth-providers/calendly/page.mdx
@@ -7,7 +7,7 @@ The Calendly auth provider enables tools and agents to call [Calendly APIs](http
 <Callout>
   Want to quickly get started with Calendly in your agent or AI app? The
   pre-built [Arcade Calendly MCP
-  Server](/resources/integrations/productivity/calendlyapi) is what you want!
+  Server](/en/resources/integrations/productivity/calendlyapi) is what you want!
 </Callout>
 
 ### What's documented here
@@ -16,7 +16,7 @@ This page describes how to use and configure Calendly auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Calendly MCP Server](/resources/integrations/productivity/calendlyapi), which provides pre-built tools for interacting with Calendly
+- The [Arcade Calendly MCP Server](/en/resources/integrations/productivity/calendlyapi), which provides pre-built tools for interacting with Calendly
 - Your [app code](#using-calendly-auth-in-app-code) that needs to call the Calendly API
 - Or, your [custom tools](#using-calendly-auth-in-custom-tools) that need to call the Calendly API
 
@@ -25,7 +25,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -111,7 +111,7 @@ Hit the **Create** button and the provider will be ready to be used.
 
 <Callout type="info">
   This method is only available when you are [self-hosting the
-  engine](/guides/deployment-hosting/on-prem)
+  engine](/en/guides/deployment-hosting/on-prem)
 </Callout>
 
 <Steps>
@@ -168,11 +168,11 @@ auth:
 </Tabs.Tab>
 </Tabs>
 
-When you use tools that require Calendly auth using your Arcade account credentials, Arcade will automatically use this Calendly OAuth provider. If you have multiple Calendly providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Calendly auth using your Arcade account credentials, Arcade will automatically use this Calendly OAuth provider. If you have multiple Calendly providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 ## Using Calendly auth in app code
 
-Use the Calendly auth provider in your own agents and AI apps to get a user token for the Calendly API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Calendly auth provider in your own agents and AI apps to get a user token for the Calendly API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Calendly API:
 
@@ -235,9 +235,9 @@ const token = authResponse.context.token;
 
 ## Using Calendly auth in custom tools
 
-You can use the pre-built [Arcade Calendly MCP Server](/resources/integrations/productivity/calendlyapi) to quickly build agents and AI apps that interact with Calendly.
+You can use the pre-built [Arcade Calendly MCP Server](/en/resources/integrations/productivity/calendlyapi) to quickly build agents and AI apps that interact with Calendly.
 
-If the pre-built tools in the Calendly MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Calendly API.
+If the pre-built tools in the Calendly MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Calendly API.
 
 Use the `OAuth2()` auth class to specify that a tool requires authorization with Calendly. The `context.authorization.token` field will be automatically populated with the user's Calendly token:
 
diff --git a/app/en/references/auth-providers/clickup/page.mdx b/app/en/references/auth-providers/clickup/page.mdx
index 8b76159a4..79f5e23c2 100644
--- a/app/en/references/auth-providers/clickup/page.mdx
+++ b/app/en/references/auth-providers/clickup/page.mdx
@@ -18,7 +18,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -68,14 +68,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require ClickUp auth using your Arcade account credentials, Arcade will automatically use this ClickUp OAuth provider. If you have multiple ClickUp providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require ClickUp auth using your Arcade account credentials, Arcade will automatically use this ClickUp OAuth provider. If you have multiple ClickUp providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using ClickUp auth in app code
 
-Use the ClickUp auth provider in your own agents and AI apps to get a user-scoped token for the ClickUp API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the ClickUp auth provider in your own agents and AI apps to get a user-scoped token for the ClickUp API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the ClickUp API:
 
@@ -132,7 +132,7 @@ const { token } = auth.context;
 
 ## Using ClickUp auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the ClickUp API.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the ClickUp API.
 
 Use the `ClickUp()` auth class to specify that a tool requires authorization with ClickUp. The `context.authorization.token` field will be automatically populated with the user's ClickUp token:
 
diff --git a/app/en/references/auth-providers/discord/page.mdx b/app/en/references/auth-providers/discord/page.mdx
index 74d2bebf1..025aabc5d 100644
--- a/app/en/references/auth-providers/discord/page.mdx
+++ b/app/en/references/auth-providers/discord/page.mdx
@@ -24,7 +24,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -74,14 +74,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Discord auth using your Arcade account credentials, Arcade will automatically use this Discord OAuth provider. If you have multiple Discord providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Discord auth using your Arcade account credentials, Arcade will automatically use this Discord OAuth provider. If you have multiple Discord providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Discord auth in app code
 
-Use the Discord auth provider in your own agents and AI apps to get a user token for the Discord API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Discord auth provider in your own agents and AI apps to get a user token for the Discord API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Discord API:
 
@@ -147,7 +147,7 @@ const token = authResponse.context.token;
 
 ## Using Discord auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Discord API.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Discord API.
 
 Use the `Discord()` auth class to specify that a tool requires authorization with Discord. The `context.authorization.token` field will be automatically populated with the user's Discord token:
 
diff --git a/app/en/references/auth-providers/dropbox/page.mdx b/app/en/references/auth-providers/dropbox/page.mdx
index 7d0821e43..b750ed20c 100644
--- a/app/en/references/auth-providers/dropbox/page.mdx
+++ b/app/en/references/auth-providers/dropbox/page.mdx
@@ -24,7 +24,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -76,14 +76,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Dropbox auth using your Arcade account credentials, Arcade will automatically use this Dropbox OAuth provider. If you have multiple Dropbox providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Dropbox auth using your Arcade account credentials, Arcade will automatically use this Dropbox OAuth provider. If you have multiple Dropbox providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Dropbox auth in app code
 
-Use the Dropbox auth provider in your own agents and AI apps to get a user-scoped token for the Dropbox API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Dropbox auth provider in your own agents and AI apps to get a user-scoped token for the Dropbox API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Dropbox API:
 
@@ -149,7 +149,7 @@ const token = authResponse.context.token;
 
 ## Using Dropbox auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Dropbox API.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Dropbox API.
 
 Use the `Dropbox()` auth class to specify that a tool requires authorization with Dropbox. The `context.authorization.token` field will be automatically populated with the user's Dropbox token:
 
diff --git a/app/en/references/auth-providers/figma/page.mdx b/app/en/references/auth-providers/figma/page.mdx
index 1bc6d233d..81744cb06 100644
--- a/app/en/references/auth-providers/figma/page.mdx
+++ b/app/en/references/auth-providers/figma/page.mdx
@@ -6,7 +6,7 @@ The Figma auth provider enables tools and agents to call [Figma APIs](https://de
 
 <Callout>
   Want to quickly get started with Figma in your agent or AI app? The pre-built
-  [Arcade Figma MCP Server](/resources/integrations/development/figma) is what you
+  [Arcade Figma MCP Server](/en/resources/integrations/development/figma) is what you
   want!
 </Callout>
 
@@ -16,13 +16,13 @@ This page describes how to use and configure Figma auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Figma MCP Server](/resources/integrations/development/figma), which provides pre-built tools for interacting with Figma
+- The [Arcade Figma MCP Server](/en/resources/integrations/development/figma), which provides pre-built tools for interacting with Figma
 - Your [app code](#using-figma-auth-in-app-code) that needs to call the Figma API
 - Or, your [custom tools](#using-figma-auth-in-custom-tools) that need to call the Figma API
 
 ### Required scopes for the Figma MCP Server
 
-If you're using the [Arcade Figma MCP Server](/resources/integrations/development/figma), you'll need to configure these scopes based on which tools you plan to use:
+If you're using the [Arcade Figma MCP Server](/en/resources/integrations/development/figma), you'll need to configure these scopes based on which tools you plan to use:
 
 - `file_content:read` - File structure, pages, nodes, and image exports
 - `library_content:read` - Published components, styles, and component sets from files
@@ -45,7 +45,7 @@ For detailed descriptions of all available Figma OAuth scopes, refer to the [Fig
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -140,7 +140,7 @@ Hit the **Create** button and the provider will be ready to be used.
 
 <Callout type="info">
   This method is only available when you are [self-hosting the
-  engine](/guides/deployment-hosting/on-prem
+  engine](/en/guides/deployment-hosting/on-prem
 </Callout>
 
 <Steps>
@@ -217,11 +217,11 @@ auth:
 </Tabs.Tab>
 </Tabs>
 
-When you use tools that require Figma auth using your Arcade account credentials, Arcade will automatically use this Figma OAuth provider. If you have multiple Figma providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Figma auth using your Arcade account credentials, Arcade will automatically use this Figma OAuth provider. If you have multiple Figma providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 ## Using Figma auth in app code
 
-Use the Figma auth provider in your own agents and AI apps to get a user token for the Figma API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Figma auth provider in your own agents and AI apps to get a user token for the Figma API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Figma API:
 
@@ -288,9 +288,9 @@ const token = authResponse.context.token;
 
 ## Using Figma auth in custom tools
 
-You can use the pre-built [Arcade Figma MCP Server](/resources/integrations/development/figma) to quickly build agents and AI apps that interact with Figma.
+You can use the pre-built [Arcade Figma MCP Server](/en/resources/integrations/development/figma) to quickly build agents and AI apps that interact with Figma.
 
-If the pre-built tools in the Figma MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Figma API.
+If the pre-built tools in the Figma MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Figma API.
 
 Use the `Figma()` auth class to specify that a tool requires authorization with Figma. The `context.authorization.token` field will be automatically populated with the user's Figma token:
 
diff --git a/app/en/references/auth-providers/github/page.mdx b/app/en/references/auth-providers/github/page.mdx
index a5353090d..7188d3c88 100644
--- a/app/en/references/auth-providers/github/page.mdx
+++ b/app/en/references/auth-providers/github/page.mdx
@@ -6,7 +6,7 @@ The GitHub auth provider enables tools and agents to call [GitHub APIs](https://
 
 <Callout>
   Want to quickly get started with GitHub in your agent or AI app? The pre-built
-  [Arcade GitHub MCP Server](/resources/integrations/development/github) is what you want!
+  [Arcade GitHub MCP Server](/en/resources/integrations/development/github) is what you want!
 </Callout>
 
 ## What's documented here
@@ -15,7 +15,7 @@ This page describes how to use and configure GitHub auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade GitHub MCP Server](/resources/integrations/development/github), which provides pre-built tools for interacting with GitHub
+- The [Arcade GitHub MCP Server](/en/resources/integrations/development/github), which provides pre-built tools for interacting with GitHub
 - Your [app code](#using-github-auth-in-app-code) that needs to call the GitHub API
 - Or, your [custom tools](#using-github-auth-in-custom-tools) that need to call the GitHub API
 
@@ -436,7 +436,7 @@ When an admin uninstalls an app:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -474,7 +474,7 @@ Click **Create** button. The provider is now ready to use.
 </Steps>
 
 When you use tools requiring GitHub auth with your Arcade account, Arcade automatically uses this provider.
-For multiple providers, see [using multiple auth providers](/references/auth-providers#using-multiple-providers-of-the-same-type).
+For multiple providers, see [using multiple auth providers](/en/references/auth-providers#using-multiple-providers-of-the-same-type).
 
 </Tabs.Tab>
 </Tabs>
@@ -657,7 +657,7 @@ Unlike github.com's fixed rate limits, GHES administrators can configure custom
 
 ## Using GitHub Auth in App Code
 
-Use the GitHub auth provider to get a user token for the GitHub API. See [authorizing agents with Arcade](/get-started/about-arcade) for details.
+Use the GitHub auth provider to get a user token for the GitHub API. See [authorizing agents with Arcade](/en/get-started/about-arcade) for details.
 
 Use `client.auth.start()` to get a user token:
 
@@ -772,7 +772,7 @@ console.log(data.stargazers_count);
 
 ## Using GitHub Auth in Custom Tools
 
-Use the pre-built [Arcade GitHub MCP Server](/resources/integrations/development/github) for quick GitHub integration.
+Use the pre-built [Arcade GitHub MCP Server](/en/resources/integrations/development/github) for quick GitHub integration.
 
 For custom tools, use the `GitHub()` auth class. The `context.authorization.token` field will be automatically populated:
 
@@ -1206,8 +1206,8 @@ Use this checklist to ensure proper setup:
 
 ### Arcade Resources
 
-- [Arcade GitHub MCP Server](/resources/integrations/development/github)
-- [Arcade Authorization Guide](/get-started/about-arcade)
+- [Arcade GitHub MCP Server](/en/resources/integrations/development/github)
+- [Arcade Authorization Guide](/en/get-started/about-arcade)
 - [Video Tutorial: GitHub App Setup](https://www.youtube.com/watch?v=KcO2SruCdt0)
 
 ---
diff --git a/app/en/references/auth-providers/google/page.mdx b/app/en/references/auth-providers/google/page.mdx
index d0be7584a..42ae366e8 100644
--- a/app/en/references/auth-providers/google/page.mdx
+++ b/app/en/references/auth-providers/google/page.mdx
@@ -6,7 +6,7 @@ The Google auth provider enables tools and agents to call Google/Google Workspac
 
 <Callout>
   Want to quickly get started with Google services in your agent or AI app? The
-  pre-built [Arcade Gmail MCP Server](/resources/integrations/productivity/gmail) is what you
+  pre-built [Arcade Gmail MCP Server](/en/resources/integrations/productivity/gmail) is what you
   want!
 </Callout>
 
@@ -16,7 +16,7 @@ This page describes how to use and configure Google auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Gmail MCP Server](/resources/integrations/productivity/gmail), which provides pre-built tools for interacting with Google services
+- The [Arcade Gmail MCP Server](/en/resources/integrations/productivity/gmail), which provides pre-built tools for interacting with Google services
 - Your [app code](#using-google-auth-in-app-code) that needs to call Google APIs
 - Or, your [custom tools](#using-google-auth-in-custom-tools) that need to call Google APIs
 
@@ -76,7 +76,7 @@ The default provider has some limitations:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -133,14 +133,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Google auth using your Arcade account credentials, Arcade will automatically use this Google OAuth provider. If you have multiple Google providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Google auth using your Arcade account credentials, Arcade will automatically use this Google OAuth provider. If you have multiple Google providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Google auth in app code
 
-Use the Google auth provider in your own agents and AI apps to get a user token for Google APIs. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Google auth provider in your own agents and AI apps to get a user token for Google APIs. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for Google APIs:
 
@@ -266,9 +266,9 @@ console.log(emailMessages);
 
 ## Using Google auth in custom tools
 
-You can use the pre-built Arcade Google MCP Servers, like [Arcade Gmail MCP Server](/resources/integrations/productivity/gmail), to quickly build agents and AI apps that interact with Google services like Gmail, Calendar, Drive, and more.
+You can use the pre-built Arcade Google MCP Servers, like [Arcade Gmail MCP Server](/en/resources/integrations/productivity/gmail), to quickly build agents and AI apps that interact with Google services like Gmail, Calendar, Drive, and more.
 
-If the pre-built tools in the Google MCP Servers don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with Google APIs.
+If the pre-built tools in the Google MCP Servers don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with Google APIs.
 
 Use the `Google()` auth class to specify that a tool requires authorization with Google. The `context.authorization.token` field will be automatically populated with the user's Google token:
 
diff --git a/app/en/references/auth-providers/hubspot/page.mdx b/app/en/references/auth-providers/hubspot/page.mdx
index 980a71e6a..296a54f42 100644
--- a/app/en/references/auth-providers/hubspot/page.mdx
+++ b/app/en/references/auth-providers/hubspot/page.mdx
@@ -6,7 +6,7 @@ The Hubspot auth provider enables tools and agents to call Hubspot APIs on behal
 
 <Callout>
   Want to quickly get started with Hubspot services in your agent or AI app? The
-  pre-built [Arcade Hubspot MCP Server](/resources/integrations/sales/hubspot) is what you
+  pre-built [Arcade Hubspot MCP Server](/en/resources/integrations/sales/hubspot) is what you
   want!
 </Callout>
 
@@ -16,7 +16,7 @@ This page describes how to use and configure Hubspot auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Hubspot MCP Server](/resources/integrations/sales/hubspot), which provides pre-built tools for interacting with Hubspot
+- The [Arcade Hubspot MCP Server](/en/resources/integrations/sales/hubspot), which provides pre-built tools for interacting with Hubspot
 - Your [app code](#using-hubspot-auth-in-app-code) that needs to call Hubspot APIs
 - Or, your [custom tools](#using-hubspot-auth-in-custom-tools) that need to call Hubspot APIs
 
@@ -24,14 +24,14 @@ This auth provider is used by:
 
 Arcade offers a default Hubspot auth provider that you can use in the Arcade Cloud Platform. In this case, your users will see `Arcade` as the name of the application that's requesting permission.
 
-If you choose to use Arcade's Hubspot auth, you don't need to configure anything. Follow the [Hubspot MCP Server examples](/resources/integrations/sales/hubspot) to get started calling Hubspot tools.
+If you choose to use Arcade's Hubspot auth, you don't need to configure anything. Follow the [Hubspot MCP Server examples](/en/resources/integrations/sales/hubspot) to get started calling Hubspot tools.
 
 ## Use Your Own Hubspot App Credentials
 
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -111,20 +111,20 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Hubspot auth using your Arcade account credentials, Arcade will automatically use this Hubspot OAuth provider. If you have multiple Hubspot providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Hubspot auth using your Arcade account credentials, Arcade will automatically use this Hubspot OAuth provider. If you have multiple Hubspot providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using the Arcade Hubspot MCP Servers
 
-The [Arcade Hubspot MCP Server](/resources/integrations/sales/hubspot) provides tools to interact with various Hubspot objects, such as companies, contacts, deals, and email messages.
+The [Arcade Hubspot MCP Server](/en/resources/integrations/sales/hubspot) provides tools to interact with various Hubspot objects, such as companies, contacts, deals, and email messages.
 
-Refer to the [MCP Server documentation and examples](/resources/integrations/sales/hubspot) to learn how to use the MCP Server to build agents and AI apps that interact with Hubspot services.
+Refer to the [MCP Server documentation and examples](/en/resources/integrations/sales/hubspot) to learn how to use the MCP Server to build agents and AI apps that interact with Hubspot services.
 
 ## Using Hubspot auth in app code
 
-Use the Hubspot auth provider in your own agents and AI apps to get a user-scoped token for the Hubspot API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Hubspot auth provider in your own agents and AI apps to get a user-scoped token for the Hubspot API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Hubspot API:
 
@@ -194,7 +194,7 @@ The scopes supported by the Arcade Hubspot auth provider are the ones [listed ab
 
 ## Using Hubspot auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Hubspot API.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Hubspot API.
 
 Use the `Hubspot()` auth class to specify that a tool requires authorization with Hubspot. The authentication token needed to call the Hubspot API is available in the tool context through the `context.get_auth_token_or_empty()` method.
 
diff --git a/app/en/references/auth-providers/linear/page.mdx b/app/en/references/auth-providers/linear/page.mdx
index c7c1ef926..32ef1e9dc 100644
--- a/app/en/references/auth-providers/linear/page.mdx
+++ b/app/en/references/auth-providers/linear/page.mdx
@@ -6,7 +6,7 @@ The Linear auth provider enables tools and agents to call [Linear APIs](https://
 
 <Callout>
   Want to quickly get started with Linear in your agent or AI app? The pre-built
-  [Arcade Linear MCP Server](/resources/integrations/productivity/linear) is what you want!
+  [Arcade Linear MCP Server](/en/resources/integrations/productivity/linear) is what you want!
 </Callout>
 
 ### What's documented here
@@ -15,7 +15,7 @@ This page describes how to use and configure Linear auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Linear MCP Server](/resources/integrations/productivity/linear), which provides pre-built tools for interacting with Linear
+- The [Arcade Linear MCP Server](/en/resources/integrations/productivity/linear), which provides pre-built tools for interacting with Linear
 - Your [app code](#using-linear-auth-in-app-code) that needs to call Linear APIs
 - Or, your [custom tools](#using-linear-auth-in-custom-tools) that need to call Linear APIs
 
@@ -24,7 +24,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -79,14 +79,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Linear auth using your Arcade account credentials, Arcade will automatically use this Linear OAuth provider. If you have multiple Linear providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Linear auth using your Arcade account credentials, Arcade will automatically use this Linear OAuth provider. If you have multiple Linear providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Linear auth in app code
 
-Use the Linear auth provider in your own agents and AI apps to get a user token for Linear APIs. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Linear auth provider in your own agents and AI apps to get a user token for Linear APIs. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for Linear APIs:
 
@@ -238,9 +238,9 @@ console.log(teams);
 
 ## Using Linear auth in custom tools
 
-You can use the pre-built [Arcade Linear MCP Server](/resources/integrations/productivity/linear) to quickly build agents and AI apps that interact with Linear.
+You can use the pre-built [Arcade Linear MCP Server](/en/resources/integrations/productivity/linear) to quickly build agents and AI apps that interact with Linear.
 
-If the pre-built tools in the Linear MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Linear API.
+If the pre-built tools in the Linear MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Linear API.
 
 Use the `Linear()` auth class to specify that a tool requires authorization with Linear. The `context.authorization.token` field will be automatically populated with the user's Linear token:
 
diff --git a/app/en/references/auth-providers/linkedin/page.mdx b/app/en/references/auth-providers/linkedin/page.mdx
index 969f398d6..fcccc015b 100644
--- a/app/en/references/auth-providers/linkedin/page.mdx
+++ b/app/en/references/auth-providers/linkedin/page.mdx
@@ -18,7 +18,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -46,7 +46,7 @@ Next, add the LinkedIn app to Arcade.
 
 ## Using LinkedIn auth in app code
 
-Use the LinkedIn auth provider in your own agents and AI apps to get a user token for LinkedIn APIs. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the LinkedIn auth provider in your own agents and AI apps to get a user token for LinkedIn APIs. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for LinkedIn APIs:
 
@@ -211,7 +211,7 @@ console.log(data);
 
 ## Using LinkedIn auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with LinkedIn APIs.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with LinkedIn APIs.
 
 Use the `LinkedIn()` auth class to specify that a tool requires authorization with LinkedIn. The `context.authorization.token` field will be automatically populated with the user's LinkedIn token:
 
diff --git a/app/en/references/auth-providers/mailchimp/page.mdx b/app/en/references/auth-providers/mailchimp/page.mdx
index 4d8d92706..3b57ae39b 100644
--- a/app/en/references/auth-providers/mailchimp/page.mdx
+++ b/app/en/references/auth-providers/mailchimp/page.mdx
@@ -6,7 +6,7 @@ The Mailchimp auth provider enables tools and agents to call [Mailchimp Marketin
 
 <Callout>
   Want to quickly get started with Mailchimp in your agent or AI app? The
-  pre-built [Arcade Mailchimp Marketing MCP Server](/resources/integrations/productivity/mailchimp-marketing-api)
+  pre-built [Arcade Mailchimp Marketing MCP Server](/en/resources/integrations/productivity/mailchimp-marketing-api)
   is what you want!
 </Callout>
 
@@ -16,7 +16,7 @@ This page describes how to use and configure Mailchimp auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Mailchimp Marketing MCP Server](/resources/integrations/productivity/mailchimp-marketing-api), which provides pre-built tools for interacting with Mailchimp
+- The [Arcade Mailchimp Marketing MCP Server](/en/resources/integrations/productivity/mailchimp-marketing-api), which provides pre-built tools for interacting with Mailchimp
 - Your [app code](#using-mailchimp-auth-in-app-code) that needs to call the Mailchimp API
 - Or, your [custom tools](#using-mailchimp-auth-in-custom-tools) that need to call the Mailchimp API
 
@@ -25,7 +25,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -113,7 +113,7 @@ Hit the **Create** button and the provider will be ready to be used.
 
 <Callout type="info">
   This method is only available when you are [self-hosting the
-  engine](/guides/deployment-hosting/on-prem
+  engine](/en/guides/deployment-hosting/on-prem
 </Callout>
 
 <Steps>
@@ -170,11 +170,11 @@ auth:
 </Tabs.Tab>
 </Tabs>
 
-When you use tools that require Mailchimp auth using your Arcade account credentials, Arcade will automatically use this Mailchimp OAuth provider. If you have multiple Mailchimp providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Mailchimp auth using your Arcade account credentials, Arcade will automatically use this Mailchimp OAuth provider. If you have multiple Mailchimp providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 ## Using Mailchimp auth in app code
 
-Use the Mailchimp auth provider in your own agents and AI apps to get a user token for the Mailchimp API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Mailchimp auth provider in your own agents and AI apps to get a user token for the Mailchimp API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Mailchimp API:
 
@@ -283,9 +283,9 @@ const apiEndpoint = metadata.api_endpoint;
 
 ## Using Mailchimp auth in custom tools
 
-You can use the pre-built [Arcade Mailchimp Marketing MCP Server](/resources/integrations/productivity/mailchimp-marketing-api) to quickly build agents and AI apps that interact with Mailchimp.
+You can use the pre-built [Arcade Mailchimp Marketing MCP Server](/en/resources/integrations/productivity/mailchimp-marketing-api) to quickly build agents and AI apps that interact with Mailchimp.
 
-If the pre-built tools in the Mailchimp MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Mailchimp API.
+If the pre-built tools in the Mailchimp MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Mailchimp API.
 
 Use the `OAuth2()` auth class to specify that a tool requires authorization with Mailchimp. The `context.authorization.token` field will be automatically populated with the user's Mailchimp token:
 
diff --git a/app/en/references/auth-providers/microsoft/page.mdx b/app/en/references/auth-providers/microsoft/page.mdx
index 45dbe3b4c..e72715574 100644
--- a/app/en/references/auth-providers/microsoft/page.mdx
+++ b/app/en/references/auth-providers/microsoft/page.mdx
@@ -24,7 +24,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -48,8 +48,8 @@ Below is the list of scopes required by the Arcade Microsoft MCP servers that ha
 
 | MCP Server                                                     | Required Permissions                                                                                                                                                                                                                                 |
 | -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Teams](/resources/integrations/social/microsoft-teams)             | `Channel.ReadBasic.All`<br/>`ChannelMessage.Read.All`<br/>`ChannelMessage.Send`<br/>`Chat.Create`<br/>`Chat.Read`<br/>`ChatMessage.Read`<br/>`ChatMessage.Send`<br/>`People.Read`<br/>`Team.ReadBasic.All`<br/>`TeamMember.Read.All`<br/>`User.Read` |
-| [SharePoint](/resources/integrations/productivity/microsoft-sharepoint)             | `Sites.Read.All`                                                                                                                                                                                                                                     |
+| [Teams](/en/resources/integrations/social/microsoft-teams)             | `Channel.ReadBasic.All`<br/>`ChannelMessage.Read.All`<br/>`ChannelMessage.Send`<br/>`Chat.Create`<br/>`Chat.Read`<br/>`ChatMessage.Read`<br/>`ChatMessage.Send`<br/>`People.Read`<br/>`Team.ReadBasic.All`<br/>`TeamMember.Read.All`<br/>`User.Read` |
+| [SharePoint](/en/resources/integrations/productivity/microsoft-sharepoint)             | `Sites.Read.All`                                                                                                                                                                                                                                     |
 
 ## Configuring your own Microsoft Auth Provider in Arcade
 
@@ -86,14 +86,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Microsoft auth using your Arcade account credentials, Arcade will automatically use this Microsoft OAuth provider. If you have multiple Microsoft providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Microsoft auth using your Arcade account credentials, Arcade will automatically use this Microsoft OAuth provider. If you have multiple Microsoft providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Microsoft auth in app code
 
-Use the Microsoft auth provider in your own agents and AI apps to get a user token for Microsoft Graph APIs. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Microsoft auth provider in your own agents and AI apps to get a user token for Microsoft Graph APIs. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for Microsoft Graph APIs:
 
@@ -159,7 +159,7 @@ const token = authResponse.context.token;
 
 ## Using Microsoft auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with Microsoft Graph APIs.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with Microsoft Graph APIs.
 
 Use the `Microsoft()` auth class to specify that a tool requires authorization with Microsoft. The `context.authorization.token` field will be automatically populated with the user's Microsoft token:
 
diff --git a/app/en/references/auth-providers/miro/page.mdx b/app/en/references/auth-providers/miro/page.mdx
index d5f4fce3c..e44733790 100644
--- a/app/en/references/auth-providers/miro/page.mdx
+++ b/app/en/references/auth-providers/miro/page.mdx
@@ -6,7 +6,7 @@ The Miro auth provider enables tools and agents to call [Miro APIs](https://deve
 
 <Callout>
   Want to quickly get started with Miro in your agent or AI app? The pre-built
-  [Arcade Miro MCP Server](/resources/integrations/productivity/miroapi) is what
+  [Arcade Miro MCP Server](/en/resources/integrations/productivity/miroapi) is what
   you want!
 </Callout>
 
@@ -16,7 +16,7 @@ This page describes how to use and configure Miro auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Miro MCP Server](/resources/integrations/productivity/miroapi), which provides pre-built tools for interacting with Miro
+- The [Arcade Miro MCP Server](/en/resources/integrations/productivity/miroapi), which provides pre-built tools for interacting with Miro
 - Your [app code](#using-miro-auth-in-app-code) that needs to call the Miro API
 - Or, your [custom tools](#using-miro-auth-in-custom-tools) that need to call the Miro API
 
@@ -25,7 +25,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -115,7 +115,7 @@ Hit the **Create** button and the provider will be ready to be used.
 
 <Callout type="info">
   This method is only available when you are [self-hosting the
-  engine](/guides/deployment-hosting/on-prem
+  engine](/en/guides/deployment-hosting/on-prem
 </Callout>
 
 <Steps>
@@ -174,11 +174,11 @@ auth:
 </Tabs.Tab>
 </Tabs>
 
-When you use tools that require Miro auth using your Arcade account credentials, Arcade will automatically use this Miro OAuth provider. If you have multiple Miro providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Miro auth using your Arcade account credentials, Arcade will automatically use this Miro OAuth provider. If you have multiple Miro providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 ## Using Miro auth in app code
 
-Use the Miro auth provider in your own agents and AI apps to get a user token for the Miro API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Miro auth provider in your own agents and AI apps to get a user token for the Miro API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Miro API:
 
@@ -245,9 +245,9 @@ const token = authResponse.context.token;
 
 ## Using Miro auth in custom tools
 
-You can use the pre-built [Arcade Miro MCP Server](/resources/integrations/productivity/miroapi) to quickly build agents and AI apps that interact with Miro.
+You can use the pre-built [Arcade Miro MCP Server](/en/resources/integrations/productivity/miroapi) to quickly build agents and AI apps that interact with Miro.
 
-If the pre-built tools in the Miro MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Miro API.
+If the pre-built tools in the Miro MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Miro API.
 
 Use the `OAuth2()` auth class to specify that a tool requires authorization with Miro. The `context.authorization.token` field will be automatically populated with the user's Miro token:
 
diff --git a/app/en/references/auth-providers/notion/page.mdx b/app/en/references/auth-providers/notion/page.mdx
index 755169461..1fabaa1d5 100644
--- a/app/en/references/auth-providers/notion/page.mdx
+++ b/app/en/references/auth-providers/notion/page.mdx
@@ -18,7 +18,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -68,14 +68,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Notion auth using your Arcade account credentials, Arcade will automatically use this Notion OAuth provider. If you have multiple Notion providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Notion auth using your Arcade account credentials, Arcade will automatically use this Notion OAuth provider. If you have multiple Notion providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Notion auth in app code
 
-Use the Notion auth provider in your own agents and AI apps to get a user token for the Notion API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Notion auth provider in your own agents and AI apps to get a user token for the Notion API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Notion API:
 
@@ -138,9 +138,9 @@ const token = authResponse.context.token;
 
 ## Using Notion auth in custom tools
 
-You can use the pre-built [Arcade Notion MCP Server](/resources/integrations/productivity/notiontoolkit) to quickly build agents and AI apps that interact with Notion.
+You can use the pre-built [Arcade Notion MCP Server](/en/resources/integrations/productivity/notiontoolkit) to quickly build agents and AI apps that interact with Notion.
 
-If the pre-built tools in the Notion MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Notion API.
+If the pre-built tools in the Notion MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Notion API.
 
 Use the `Notion()` auth class to specify that a tool requires authorization with Notion. The `context.authorization.token` field will be automatically populated with the user's Notion token:
 
diff --git a/app/en/references/auth-providers/oauth2/page.mdx b/app/en/references/auth-providers/oauth2/page.mdx
index bf4e4a3b5..707622557 100644
--- a/app/en/references/auth-providers/oauth2/page.mdx
+++ b/app/en/references/auth-providers/oauth2/page.mdx
@@ -11,7 +11,7 @@ import ToggleContent from "@/app/_components/toggle-content";
 The OAuth 2.0 auth provider enables tools and agents to authorize with any OAuth 2.0-compatible API on behalf of a user.
 
 <Callout>
-  Arcade has [pre-built auth providers](/references/auth-providers) for many popular
+  Arcade has [pre-built auth providers](/en/references/auth-providers) for many popular
   OAuth 2.0 services. Use this OAuth 2.0 provider to connect to other systems
   that aren't pre-built.
 </Callout>
@@ -29,7 +29,7 @@ The only supported OAuth 2.0 flow is the authorization code grant flow (with or
 
 ## Configuring OAuth 2.0
 
-How you configure the OAuth 2.0 provider depends on whether you use the Arcade Cloud Engine or a [self-hosted Engine](/guides/deployment-hosting/on-prem). If you use the Cloud Engine, you must configure your provider in the Dashboard.
+How you configure the OAuth 2.0 provider depends on whether you use the Arcade Cloud Engine or a [self-hosted Engine](/en/guides/deployment-hosting/on-prem). If you use the Cloud Engine, you must configure your provider in the Dashboard.
 
 <Callout type="info">
   When configuring your app in the OAuth 2.0 enabled service, you must use the
@@ -42,7 +42,7 @@ How you configure the OAuth 2.0 provider depends on whether you use the Arcade C
 <Callout type="info">
   When using the Arcade Cloud Platform, the Dashboard is available at
   [`https://api.arcade.dev/dashboard`](https://api.arcade.dev/dashboard). If you
-  are [self-hosting Arcade](/guides/deployment-hosting/on-prem), by default
+  are [self-hosting Arcade](/en/guides/deployment-hosting/on-prem), by default
   the Dashboard is available at
   [`http://localhost:9099/dashboard`](http://localhost:9099/dashboard). Adjust
   the host and port, if necessary, to match your environment.
@@ -61,7 +61,7 @@ When you use tools that require OAuth 2.0 authorization using your Arcade accoun
 
 <Callout type="info">
   This method is only available when you are [self-hosting the
-  engine](/guides/deployment-hosting/on-prem
+  engine](/en/guides/deployment-hosting/on-prem
 </Callout>
 
 <Steps>
@@ -83,7 +83,7 @@ HOOLI_CLIENT_SECRET="<your client secret>"
 ```
 
 <Callout>
-  See [configuration](/guides/deployment-hosting/configure-engine) for more
+  See [configuration](/en/guides/deployment-hosting/configure-engine) for more
   information on how to set environment variables and configure the Arcade
   Engine.
 </Callout>
@@ -93,7 +93,7 @@ HOOLI_CLIENT_SECRET="<your client secret>"
 <Callout>
   To locate the `engine.yaml` file in your OS after installing the Arcade
   Engine, check the [Engine configuration
-  file](/guides/deployment-hosting/configure-engine)
+  file](/en/guides/deployment-hosting/configure-engine)
   documentation.
 </Callout>
 
@@ -517,7 +517,7 @@ auth:
 
 ## Using OAuth 2.0 in app code
 
-Use the OAuth 2.0 auth provider in your own agents and AI apps to get a user token for any OAuth 2.0-compatible APIs. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the OAuth 2.0 auth provider in your own agents and AI apps to get a user token for any OAuth 2.0-compatible APIs. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get an access token:
 
@@ -585,7 +585,7 @@ const token = authResponse.context.token;
 
 ## Using OAuth 2.0 in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with any OAuth 2.0-compatible APIs.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with any OAuth 2.0-compatible APIs.
 
 Use the `OAuth2()` auth class to specify that a tool requires OAuth 2.0 authorization. In your tool function, `context.authorization` will be automatically populated with the following properties:
 
diff --git a/app/en/references/auth-providers/page.mdx b/app/en/references/auth-providers/page.mdx
index bc3c0151e..cd9a5b66e 100644
--- a/app/en/references/auth-providers/page.mdx
+++ b/app/en/references/auth-providers/page.mdx
@@ -15,7 +15,7 @@ It can be useful to configure your own auth provider for the following reasons:
 
 - You want to use your own brand on the auth screen
 - You want to isolate your rate limits from other Arcade customers
-- You want to use a service that Arcade [does not have a built-in auth provider for](/references/auth-providers/oauth2)
+- You want to use a service that Arcade [does not have a built-in auth provider for](/en/references/auth-providers/oauth2)
 
 After adding an auth provider used by an Arcade tool, executing the tool will automatically use your auth provider. Even in the Arcade Cloud Platform, your auth provider will take precedence over the arcade-provided auth provider.
 
@@ -156,7 +156,7 @@ For more information on how to customize your auth provider, select an auth prov
   />
 </div>
 
-If the auth provider you need is not listed, try the [OAuth 2.0](/references/auth-providers/oauth2) provider, or [get in touch](mailto:contact@arcade.dev) with us!
+If the auth provider you need is not listed, try the [OAuth 2.0](/en/references/auth-providers/oauth2) provider, or [get in touch](mailto:contact@arcade.dev) with us!
 
 ## Using multiple providers of the same type
 
@@ -179,4 +179,4 @@ async def list_emails(
 
 This is similar to the pattern used in the generic OAuth2 provider, but instead of using the `OAuth2` class, you use the `Google` class and specify the `id` of the auth provider you want to use.
 
-See the docs about [Authoring Tools](/guides/create-tools/tool-basics/build-mcp-server) for more information on how to create and serve a MCP Server.
+See the docs about [Authoring Tools](/en/guides/create-tools/tool-basics/build-mcp-server) for more information on how to create and serve a MCP Server.
diff --git a/app/en/references/auth-providers/pagerduty/page.mdx b/app/en/references/auth-providers/pagerduty/page.mdx
index 01af07a78..0d3982f67 100644
--- a/app/en/references/auth-providers/pagerduty/page.mdx
+++ b/app/en/references/auth-providers/pagerduty/page.mdx
@@ -14,7 +14,7 @@ The PagerDuty auth provider enables tools and agents to call [PagerDuty APIs](ht
 <Callout>
   Want to quickly get started with PagerDuty in your agent or AI app? The
   pre-built [Arcade PagerDuty MCP
-  Server](/resources/integrations/development/pagerdutyapi) is what you want!
+  Server](/en/resources/integrations/development/pagerdutyapi) is what you want!
 </Callout>
 
 ### What's documented here
@@ -23,7 +23,7 @@ This page describes how to use and configure PagerDuty auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade PagerDuty MCP Server](/resources/integrations/development/pagerdutyapi), which provides pre-built tools for interacting with PagerDuty
+- The [Arcade PagerDuty MCP Server](/en/resources/integrations/development/pagerdutyapi), which provides pre-built tools for interacting with PagerDuty
 - Your [app code](#using-pagerduty-auth-in-app-code) that needs to call the PagerDuty API
 - Or, your [custom tools](#using-pagerduty-auth-in-custom-tools) that need to call the PagerDuty API
 
@@ -32,7 +32,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -122,7 +122,7 @@ Hit the **Create** button and the provider will be ready to be used.
 
 <Callout type="info">
   This method is only available when you are [self-hosting the
-  engine](/guides/deployment-hosting/on-prem
+  engine](/en/guides/deployment-hosting/on-prem
 </Callout>
 
 <Steps>
@@ -181,11 +181,11 @@ auth:
 </Tabs.Tab>
 </Tabs>
 
-When you use tools that require PagerDuty auth using your Arcade account credentials, Arcade will automatically use this PagerDuty OAuth provider. If you have multiple PagerDuty providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require PagerDuty auth using your Arcade account credentials, Arcade will automatically use this PagerDuty OAuth provider. If you have multiple PagerDuty providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 ## Using PagerDuty auth in app code
 
-Use the PagerDuty auth provider in your own agents and AI apps to get a user token for the PagerDuty API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the PagerDuty auth provider in your own agents and AI apps to get a user token for the PagerDuty API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the PagerDuty API:
 
@@ -249,9 +249,9 @@ const token = authResponse.context.token;
 
 ## Using PagerDuty auth in custom tools
 
-You can use the pre-built [Arcade PagerDuty MCP Server](/resources/integrations/development/pagerdutyapi) to quickly build agents and AI apps that interact with PagerDuty.
+You can use the pre-built [Arcade PagerDuty MCP Server](/en/resources/integrations/development/pagerdutyapi) to quickly build agents and AI apps that interact with PagerDuty.
 
-If the pre-built tools in the PagerDuty MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the PagerDuty API.
+If the pre-built tools in the PagerDuty MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the PagerDuty API.
 
 Use the `PagerDuty()` auth class to specify that a tool requires authorization with PagerDuty. The `context.authorization.token` field will be automatically populated with the user's PagerDuty token:
 
diff --git a/app/en/references/auth-providers/reddit/page.mdx b/app/en/references/auth-providers/reddit/page.mdx
index 556d5b2bb..88c583f9e 100644
--- a/app/en/references/auth-providers/reddit/page.mdx
+++ b/app/en/references/auth-providers/reddit/page.mdx
@@ -24,7 +24,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -76,14 +76,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Reddit auth using your Arcade account credentials, Arcade will automatically use this Reddit OAuth provider. If you have multiple Reddit providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Reddit auth using your Arcade account credentials, Arcade will automatically use this Reddit OAuth provider. If you have multiple Reddit providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Reddit auth in app code
 
-Use the Reddit auth provider in your own agents and AI apps to get a user-scoped token for the Reddit API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Reddit auth provider in your own agents and AI apps to get a user-scoped token for the Reddit API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Reddit API:
 
@@ -149,7 +149,7 @@ const token = authResponse.context.token;
 
 ## Using Reddit auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Reddit API.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Reddit API.
 
 Use the `Reddit()` auth class to specify that a tool requires authorization with Reddit. The `context.authorization.token` field will be automatically populated with the user's Reddit token:
 
diff --git a/app/en/references/auth-providers/salesforce/page.mdx b/app/en/references/auth-providers/salesforce/page.mdx
index 62cc5f125..dc5562dc3 100644
--- a/app/en/references/auth-providers/salesforce/page.mdx
+++ b/app/en/references/auth-providers/salesforce/page.mdx
@@ -12,7 +12,7 @@ This page describes how to use and configure Salesforce auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Salesforce MCP Server](/resources/integrations/sales/salesforce), which provides pre-built tools for interacting with Salesforce services
+- The [Arcade Salesforce MCP Server](/en/resources/integrations/sales/salesforce), which provides pre-built tools for interacting with Salesforce services
 - Your [app code](#calling-salesforce-apis-directly) that needs to call Salesforce APIs
 - Or, your [custom tools](#create-your-own-salesforce-tools) that need to call Salesforce APIs
 
@@ -21,7 +21,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -94,12 +94,12 @@ Set the `SALESFORCE_ORG_SUBDOMAIN` secret in the Arcade Dashboard:
 
 The Salesforce API requires the App developer to create [OAuth custom scopes](https://help.salesforce.com/s/articleView?id=xcloud.remoteaccess_oauth_customscopes.htm&type=5) defining granular permissions for their application users to authorize.
 
-The custom scopes required by the [Arcade Salesforce MCP Server](/resources/integrations/sales/salesforce) are listed below, along with their descriptions:
+The custom scopes required by the [Arcade Salesforce MCP Server](/en/resources/integrations/sales/salesforce) are listed below, along with their descriptions:
 
 <Callout type="info">
-  The custom scopes listed below are only required if you are using the [Arcade Salesforce MCP Server](/resources/integrations/sales/salesforce).
+  The custom scopes listed below are only required if you are using the [Arcade Salesforce MCP Server](/en/resources/integrations/sales/salesforce).
 
-If you're creating your own [custom Salesforce tools](/guides/create-tools/tool-basics/build-mcp-server) or using Arcade to authorize users and call Salesforce APIs directly, you are free to define custom scope(s) that fit best your application use cases. Observe that you must have at least one custom scope assigned to your Salesforce app in order to use the Salesforce API.
+If you're creating your own [custom Salesforce tools](/en/guides/create-tools/tool-basics/build-mcp-server) or using Arcade to authorize users and call Salesforce APIs directly, you are free to define custom scope(s) that fit best your application use cases. Observe that you must have at least one custom scope assigned to your Salesforce app in order to use the Salesforce API.
 
 </Callout>
 
@@ -141,7 +141,7 @@ Go to the [Arcade Dashboard](https://api.arcade.dev/dashboard) and log in with y
 
 #### Enter the provider details
 
-- Enter `salesforce` as the **ID** for your provider (the ID must be `salesforce` to use the [Arcade Salesforce MCP Server](/resources/integrations/sales/salesforce)).
+- Enter `salesforce` as the **ID** for your provider (the ID must be `salesforce` to use the [Arcade Salesforce MCP Server](/en/resources/integrations/sales/salesforce)).
 - Optionally enter a **Description**.
 - Enter your **Client ID** (Consumer Key) and **Client Secret** (Consumer Secret) from your Salesforce External Client App.
 - Note the **Redirect URL** generated by Arcade. This must be set as your Salesforce External Client App's callback URL.
@@ -191,23 +191,23 @@ Click the **Create** button and the provider will be ready to be used in the Arc
 
 ## Using the Arcade Salesforce MCP Server
 
-The [Arcade Salesforce MCP Server](/resources/integrations/sales/salesforce) provides tools to interact with various Salesforce objects, such as accounts, contacts, leads, opportunities, notes, tasks, email messages, call logs, etc.
+The [Arcade Salesforce MCP Server](/en/resources/integrations/sales/salesforce) provides tools to interact with various Salesforce objects, such as accounts, contacts, leads, opportunities, notes, tasks, email messages, call logs, etc.
 
-Refer to the [MCP Server documentation and examples](/resources/integrations/sales/salesforce) to learn how to use the MCP Server to build agents and AI apps that interact with Salesforce services.
+Refer to the [MCP Server documentation and examples](/en/resources/integrations/sales/salesforce) to learn how to use the MCP Server to build agents and AI apps that interact with Salesforce services.
 
 <Callout>
   Check our introductory documentation to understand what are tools and how
-  [tool calling works](/guides/tool-calling).
+  [tool calling works](/en/guides/tool-calling).
 </Callout>
 
 ## Calling Salesforce APIs directly
 
-Use the Salesforce auth provider to get a user authorization token and call Salesforce API endpoints directly, without the use of any tools. See [How Arcade helps with Agent Authorization](/get-started/about-arcade) to understand how this works.
+Use the Salesforce auth provider to get a user authorization token and call Salesforce API endpoints directly, without the use of any tools. See [How Arcade helps with Agent Authorization](/en/get-started/about-arcade) to understand how this works.
 
 ### Prerequisites
 
 1. Create an <SignupLink linkLocation="docs:/home/auth-providers/salesforce">Arcade account</SignupLink>
-1. Get an [Arcade API key](/get-started/setup/api-keys).
+1. Get an [Arcade API key](/en/get-started/setup/api-keys).
 1. Set the `ARCADE_API_KEY` environment variable (`export ARCADE_API_KEY=<your-api-key>` on Bash, `$env:ARCADE_API_KEY="<your-api-key>"` on PowerShell).
 1. Make sure to have Python 3.10+ or Node.js 18+ installed.
 
@@ -569,7 +569,7 @@ console.log(await response.json());
 
 ## Create your own Salesforce Tools
 
-If the pre-built tools in the [Arcade Salesforce MCP Server](/resources/integrations/sales/salesforce) don't meet your needs, you can create your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Salesforce APIs.
+If the pre-built tools in the [Arcade Salesforce MCP Server](/en/resources/integrations/sales/salesforce) don't meet your needs, you can create your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Salesforce APIs.
 
 The code implemented in the Arcade Salesforce tools is the best guide for you to understand how to implement your own.
 ```
diff --git a/app/en/references/auth-providers/slack/page.mdx b/app/en/references/auth-providers/slack/page.mdx
index febe16fc7..e293aaf13 100644
--- a/app/en/references/auth-providers/slack/page.mdx
+++ b/app/en/references/auth-providers/slack/page.mdx
@@ -6,7 +6,7 @@ The Slack auth provider enables tools and agents to call [Slack APIs](https://ap
 
 <Callout>
   Want to quickly get started with Slack in your agent or AI app? The pre-built
-  [Arcade Slack MCP Server](/resources/integrations/social/slack) is what you
+  [Arcade Slack MCP Server](/en/resources/integrations/social/slack) is what you
   want!
 </Callout>
 
@@ -16,7 +16,7 @@ This page describes how to use and configure Slack auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Slack MCP Server](/resources/integrations/social/slack), which provides pre-built tools for interacting with Slack
+- The [Arcade Slack MCP Server](/en/resources/integrations/social/slack), which provides pre-built tools for interacting with Slack
 - Your [app code](#using-slack-auth-in-app-code) that needs to call the Slack API
 - Or, your [custom tools](#using-slack-auth-in-custom-tools) that need to call the Slack API
 
@@ -25,7 +25,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -40,12 +40,12 @@ Before showing how to configure your Slack app credentials, let's go through the
 <Callout type="warning">
   In May 29, 2025, [Slack announced](https://api.slack.com/changelog/2025-05-terms-rate-limit-update-and-faq) changes to their API rate-limits and terms of service for apps that are not approved for the Slack Marketplace.
 
-The `conversations.history` and `conversations.replies` endpoints are now limited to 1 request/minute and up to 15 objects returned per request. This affects various tools in the [Arcade Slack MCP Server](/resources/integrations/social/slack). Additionally, the [API Terms of Service](https://slack.com/terms-of-service/api) now requires [Slack Marketplace](https://api.slack.com/slack-marketplace/using) approval for commercial distribution.
+The `conversations.history` and `conversations.replies` endpoints are now limited to 1 request/minute and up to 15 objects returned per request. This affects various tools in the [Arcade Slack MCP Server](/en/resources/integrations/social/slack). Additionally, the [API Terms of Service](https://slack.com/terms-of-service/api) now requires [Slack Marketplace](https://api.slack.com/slack-marketplace/using) approval for commercial distribution.
 
 </Callout>
 
 - Follow Slack's guide to [registering a Slack app](https://api.slack.com/quickstart)
-- If you plan to use the [Arcade Slack MCP Server](/resources/integrations/social/slack), select the scopes below (include additional scopes for your application's authorization needs or custom tools, in any):
+- If you plan to use the [Arcade Slack MCP Server](/en/resources/integrations/social/slack), select the scopes below (include additional scopes for your application's authorization needs or custom tools, in any):
   - `channels:history`
   - `channels:read`
   - `chat:write`
@@ -99,14 +99,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Slack auth using your Arcade account credentials, Arcade will automatically use this Slack OAuth provider. If you have multiple Slack providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Slack auth using your Arcade account credentials, Arcade will automatically use this Slack OAuth provider. If you have multiple Slack providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Slack auth in app code
 
-Use the Slack auth provider in your own agents and AI apps to get a user token for the Slack API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Slack auth provider in your own agents and AI apps to get a user token for the Slack API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Slack API:
 
@@ -177,9 +177,9 @@ const token = authResponse.context.token;
 
 ## Using Slack auth in custom tools
 
-You can use the pre-built [Arcade Slack MCP Server](/resources/integrations/social/slack) to quickly build agents and AI apps that interact with Slack.
+You can use the pre-built [Arcade Slack MCP Server](/en/resources/integrations/social/slack) to quickly build agents and AI apps that interact with Slack.
 
-If the pre-built tools in the Slack MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Slack API.
+If the pre-built tools in the Slack MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Slack API.
 
 Use the `Slack()` auth class to specify that a tool requires authorization with Slack. The `context.authorization.token` field will be automatically populated with the user's Slack token:
 
diff --git a/app/en/references/auth-providers/spotify/page.mdx b/app/en/references/auth-providers/spotify/page.mdx
index 28c7c4509..41fab79b0 100644
--- a/app/en/references/auth-providers/spotify/page.mdx
+++ b/app/en/references/auth-providers/spotify/page.mdx
@@ -24,7 +24,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -77,14 +77,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Spotify auth using your Arcade account credentials, Arcade will automatically use this Spotify OAuth provider. If you have multiple Spotify providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Spotify auth using your Arcade account credentials, Arcade will automatically use this Spotify OAuth provider. If you have multiple Spotify providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Spotify auth in app code
 
-Use the Spotify auth provider in your own agents and AI apps to get a user token for the Spotify API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Spotify auth provider in your own agents and AI apps to get a user token for the Spotify API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Spotify API:
 
@@ -150,7 +150,7 @@ const token = authResponse.context.token;
 
 ## Using Spotify auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Spotify API.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Spotify API.
 
 Use the `Spotify()` auth class to specify that a tool requires authorization with Spotify. The `context.authorization.token` field will be automatically populated with the user's Spotify token:
 
diff --git a/app/en/references/auth-providers/square/page.mdx b/app/en/references/auth-providers/square/page.mdx
index 2c02bd355..2f399eee8 100644
--- a/app/en/references/auth-providers/square/page.mdx
+++ b/app/en/references/auth-providers/square/page.mdx
@@ -6,7 +6,7 @@ The Square auth provider enables tools and agents to call [Square APIs](https://
 
 <Callout>
   Want to quickly get started with Square in your agent or AI app? The pre-built
-  [Arcade Square MCP Server](/resources/integrations/productivity/squareupapi)
+  [Arcade Square MCP Server](/en/resources/integrations/productivity/squareupapi)
   is what you want!
 </Callout>
 
@@ -16,7 +16,7 @@ This page describes how to use and configure Square auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Square MCP Server](/resources/integrations/productivity/squareupapi), which provides pre-built tools for interacting with Square
+- The [Arcade Square MCP Server](/en/resources/integrations/productivity/squareupapi), which provides pre-built tools for interacting with Square
 - Your [app code](#using-square-auth-in-app-code) that needs to call the Square API
 - Or, your [custom tools](#using-square-auth-in-custom-tools) that need to call the Square API
 
@@ -25,7 +25,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -117,7 +117,7 @@ Hit the **Create** button and the provider will be ready to be used.
 
 <Callout type="info">
   This method is only available when you are [self-hosting the
-  engine](/guides/deployment-hosting/on-prem
+  engine](/en/guides/deployment-hosting/on-prem
 </Callout>
 
 <Steps>
@@ -176,11 +176,11 @@ auth:
 </Tabs.Tab>
 </Tabs>
 
-When you use tools that require Square auth using your Arcade account credentials, Arcade will automatically use this Square OAuth provider. If you have multiple Square providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Square auth using your Arcade account credentials, Arcade will automatically use this Square OAuth provider. If you have multiple Square providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 ## Using Square auth in app code
 
-Use the Square auth provider in your own agents and AI apps to get a user token for the Square API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Square auth provider in your own agents and AI apps to get a user token for the Square API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Square API:
 
@@ -247,9 +247,9 @@ const token = authResponse.context.token;
 
 ## Using Square auth in custom tools
 
-You can use the pre-built [Arcade Square MCP Server](/resources/integrations/productivity/squareupapi) to quickly build agents and AI apps that interact with Square.
+You can use the pre-built [Arcade Square MCP Server](/en/resources/integrations/productivity/squareupapi) to quickly build agents and AI apps that interact with Square.
 
-If the pre-built tools in the Square MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Square API.
+If the pre-built tools in the Square MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Square API.
 
 Use the `OAuth2()` auth class to specify that a tool requires authorization with Square. The `context.authorization.token` field will be automatically populated with the user's Square token:
 
diff --git a/app/en/references/auth-providers/ticktick/page.mdx b/app/en/references/auth-providers/ticktick/page.mdx
index 14ff5bbc7..4c4609e2d 100644
--- a/app/en/references/auth-providers/ticktick/page.mdx
+++ b/app/en/references/auth-providers/ticktick/page.mdx
@@ -7,7 +7,7 @@ The TickTick auth provider enables tools and agents to call [TickTick APIs](http
 <Callout>
   Want to quickly get started with TickTick in your agent or AI app? The
   pre-built [Arcade TickTick API MCP
-  Server](/resources/integrations/productivity/ticktickapi) is what you want!
+  Server](/en/resources/integrations/productivity/ticktickapi) is what you want!
 </Callout>
 
 ### What's documented here
@@ -16,7 +16,7 @@ This page describes how to use and configure TickTick auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade TickTick API MCP Server](/resources/integrations/productivity/ticktickapi), which provides pre-built tools for interacting with TickTick
+- The [Arcade TickTick API MCP Server](/en/resources/integrations/productivity/ticktickapi), which provides pre-built tools for interacting with TickTick
 - Your [app code](#using-ticktick-auth-in-app-code) that needs to call the TickTick API
 - Or, your [custom tools](#using-ticktick-auth-in-custom-tools) that need to call the TickTick API
 
@@ -25,7 +25,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -110,7 +110,7 @@ Hit the **Create** button and the provider will be ready to be used.
 
 <Callout type="info">
   This method is only available when you are [self-hosting the
-  engine](/guides/deployment-hosting/on-prem
+  engine](/en/guides/deployment-hosting/on-prem
 </Callout>
 
 <Steps>
@@ -180,11 +180,11 @@ auth:
 </Tabs.Tab>
 </Tabs>
 
-When you use tools that require TickTick auth using your Arcade account credentials, Arcade will automatically use this TickTick OAuth provider. If you have multiple TickTick providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require TickTick auth using your Arcade account credentials, Arcade will automatically use this TickTick OAuth provider. If you have multiple TickTick providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 ## Using TickTick auth in app code
 
-Use the TickTick auth provider in your own agents and AI apps to get a user token for the TickTick API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the TickTick auth provider in your own agents and AI apps to get a user token for the TickTick API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the TickTick API:
 
@@ -251,9 +251,9 @@ const token = authResponse.context.token;
 
 ## Using TickTick auth in custom tools
 
-You can use the pre-built [Arcade TickTick API MCP Server](/resources/integrations/productivity/ticktickapi) to quickly build agents and AI apps that interact with TickTick.
+You can use the pre-built [Arcade TickTick API MCP Server](/en/resources/integrations/productivity/ticktickapi) to quickly build agents and AI apps that interact with TickTick.
 
-If the pre-built tools in the TickTick MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the TickTick API.
+If the pre-built tools in the TickTick MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the TickTick API.
 
 Use the `OAuth2()` auth class to specify that a tool requires authorization with TickTick. The `context.authorization.token` field will be automatically populated with the user's TickTick token:
 
diff --git a/app/en/references/auth-providers/twitch/page.mdx b/app/en/references/auth-providers/twitch/page.mdx
index ead1080c1..3362d50d1 100644
--- a/app/en/references/auth-providers/twitch/page.mdx
+++ b/app/en/references/auth-providers/twitch/page.mdx
@@ -24,7 +24,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -80,14 +80,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Twitch auth using your Arcade account credentials, Arcade will automatically use this Twitch OAuth provider. If you have multiple Twitch providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Twitch auth using your Arcade account credentials, Arcade will automatically use this Twitch OAuth provider. If you have multiple Twitch providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Twitch auth in app code
 
-Use the Twitch auth provider in your own agents and AI apps to get a user-scoped token for the Twitch API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Twitch auth provider in your own agents and AI apps to get a user-scoped token for the Twitch API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Twitch API:
 
@@ -153,7 +153,7 @@ const token = authResponse.context.token;
 
 ## Using Twitch auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Twitch API.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Twitch API.
 
 Use the `Twitch()` auth class to specify that a tool requires authorization with Twitch. The `context.authorization.token` field will be automatically populated with the user's Twitch token:
 
diff --git a/app/en/references/auth-providers/x/page.mdx b/app/en/references/auth-providers/x/page.mdx
index 473f1bfca..7b4a3868b 100644
--- a/app/en/references/auth-providers/x/page.mdx
+++ b/app/en/references/auth-providers/x/page.mdx
@@ -6,7 +6,7 @@ The X auth provider enables tools and agents to call the X (Twitter) API on beha
 
 <Callout>
   Want to quickly get started with X services in your agent or AI app? The
-  pre-built [Arcade X MCP Server](/resources/integrations/social/x) is what you
+  pre-built [Arcade X MCP Server](/en/resources/integrations/social/x) is what you
   want!
 </Callout>
 
@@ -16,7 +16,7 @@ This page describes how to use and configure X auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade X MCP Server](/resources/integrations/social/x), which provides pre-built tools for interacting with X
+- The [Arcade X MCP Server](/en/resources/integrations/social/x), which provides pre-built tools for interacting with X
 - Your [app code](#using-x-auth-in-app-code) that needs to call X APIs
 - Or, your [custom tools](#using-x-auth-in-custom-tools) that need to call X APIs
 
@@ -25,7 +25,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -79,14 +79,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require X auth using your Arcade account credentials, Arcade will automatically use this X OAuth provider. If you have multiple X providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require X auth using your Arcade account credentials, Arcade will automatically use this X OAuth provider. If you have multiple X providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using X auth in app code
 
-Use the X auth provider in your own agents and AI apps to get a user token for the X API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the X auth provider in your own agents and AI apps to get a user token for the X API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for X:
 
@@ -154,9 +154,9 @@ const token = authResponse.context.token;
 
 ## Using X auth in custom tools
 
-You can use the pre-built [Arcade X MCP Server](/resources/integrations/social/x) to quickly build agents and AI apps that interact with X.
+You can use the pre-built [Arcade X MCP Server](/en/resources/integrations/social/x) to quickly build agents and AI apps that interact with X.
 
-If the pre-built tools in the X MCP Server don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the X API.
+If the pre-built tools in the X MCP Server don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the X API.
 
 Use the `X()` auth class to specify that a tool requires authorization with X. The `context.authorization.token` field will be automatically populated with the user's X token:
 
diff --git a/app/en/references/auth-providers/zendesk/page.mdx b/app/en/references/auth-providers/zendesk/page.mdx
index 70c7db8b3..85ef0034d 100644
--- a/app/en/references/auth-providers/zendesk/page.mdx
+++ b/app/en/references/auth-providers/zendesk/page.mdx
@@ -5,7 +5,7 @@ import { SignupLink } from "@/app/_components/analytics";
 
 <Callout type="info">
   Arcade does not offer a default Zendesk Auth Provider. To use Zendesk auth,
-  you must create a [custom provider configuration](/references/auth-providers/oauth2)
+  you must create a [custom provider configuration](/en/references/auth-providers/oauth2)
   as described below.
 </Callout>
 
@@ -17,7 +17,7 @@ This page describes how to use and configure Zendesk auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Zendesk MCP Server](/resources/integrations/customer-support/zendesk), which provides pre-built tools for interacting with Zendesk services
+- The [Arcade Zendesk MCP Server](/en/resources/integrations/customer-support/zendesk), which provides pre-built tools for interacting with Zendesk services
 - Your [app code](#using-zendesk-auth-in-app-code) that needs to call Zendesk APIs
 - Or, your [custom tools](#using-zendesk-auth-in-custom-tools) that need to call Zendesk APIs
 
@@ -26,7 +26,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -117,7 +117,7 @@ Note the **Redirect URL** generated by Arcade. This must be set as your Zendesk
 
 ## Using Zendesk auth in app code
 
-Use the Zendesk auth provider you just created in your own agents and AI apps to get a user token for Zendesk APIs. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Zendesk auth provider you just created in your own agents and AI apps to get a user token for Zendesk APIs. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for Zendesk APIs:
 
@@ -184,7 +184,7 @@ const token = authResponse.context.token;
 
 ## Using Zendesk auth in custom tools
 
-If the [Arcade Zendesk MCP Server](/resources/integrations/customer-support/zendesk) does not meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with Zendesk APIs.
+If the [Arcade Zendesk MCP Server](/en/resources/integrations/customer-support/zendesk) does not meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with Zendesk APIs.
 
 Use the `OAuth2()` auth class to specify that a tool requires authorization with Zendesk. The `context.authorization.token` field will be automatically populated with the user's Zendesk token:
 
diff --git a/app/en/references/auth-providers/zoho/page.mdx b/app/en/references/auth-providers/zoho/page.mdx
index 3a1550a3b..1f04995a5 100644
--- a/app/en/references/auth-providers/zoho/page.mdx
+++ b/app/en/references/auth-providers/zoho/page.mdx
@@ -7,7 +7,7 @@ The Zoho auth provider enables tools and agents to call [Zoho APIs](https://www.
 <Callout>
   Want to quickly get started with Zoho in your agent or AI app? Check out the
   pre-built Arcade Zoho MCP Servers: - [Zoho Books API MCP
-  Server](/resources/integrations/payments/zoho-books-api)
+  Server](/en/resources/integrations/payments/zoho-books-api)
   - Zoho Creator API MCP Server (coming soon)
 </Callout>
 
@@ -17,7 +17,7 @@ This page describes how to use and configure Zoho auth with Arcade.
 
 This auth provider is used by:
 
-- The [Arcade Zoho Books API MCP Server](/resources/integrations/payments/zoho-books-api), which provides pre-built tools for interacting with Zoho Books
+- The [Arcade Zoho Books API MCP Server](/en/resources/integrations/payments/zoho-books-api), which provides pre-built tools for interacting with Zoho Books
 - The Arcade Zoho Creator API MCP Server (coming soon), which will provide pre-built tools for interacting with Zoho Creator
 - Your [app code](#using-zoho-auth-in-app-code) that needs to call Zoho APIs
 - Or, your [custom tools](#using-zoho-auth-in-custom-tools) that need to call Zoho APIs
@@ -27,7 +27,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -126,7 +126,7 @@ Hit the **Create** button and the provider will be ready to be used.
 
 <Callout type="info">
   This method is only available when you are [self-hosting the
-  engine](/guides/deployment-hosting/on-prem
+  engine](/en/guides/deployment-hosting/on-prem
 </Callout>
 
 <Steps>
@@ -205,11 +205,11 @@ auth:
 </Tabs.Tab>
 </Tabs>
 
-When you use tools that require Zoho auth using your Arcade account credentials, Arcade will automatically use this Zoho OAuth provider. If you have multiple Zoho providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Zoho auth using your Arcade account credentials, Arcade will automatically use this Zoho OAuth provider. If you have multiple Zoho providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 ## Using Zoho auth in app code
 
-Use the Zoho auth provider in your own agents and AI apps to get a user token for Zoho APIs. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Zoho auth provider in your own agents and AI apps to get a user token for Zoho APIs. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for Zoho APIs:
 
@@ -275,9 +275,9 @@ const token = authResponse.context.token;
 
 ## Using Zoho auth in custom tools
 
-You can use the pre-built Arcade Zoho MCP Servers ([Zoho Books](/resources/integrations/payments/zoho-books-api), Zoho Creator (coming soon)) to quickly build agents and AI apps that interact with Zoho.
+You can use the pre-built Arcade Zoho MCP Servers ([Zoho Books](/en/resources/integrations/payments/zoho-books-api), Zoho Creator (coming soon)) to quickly build agents and AI apps that interact with Zoho.
 
-If the pre-built tools don't meet your needs, you can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with Zoho APIs.
+If the pre-built tools don't meet your needs, you can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with Zoho APIs.
 
 Use the `OAuth2()` auth class to specify that a tool requires authorization with Zoho. The `context.authorization.token` field will be automatically populated with the user's Zoho token:
 
diff --git a/app/en/references/auth-providers/zoom/page.mdx b/app/en/references/auth-providers/zoom/page.mdx
index da29ae659..e8c5d142f 100644
--- a/app/en/references/auth-providers/zoom/page.mdx
+++ b/app/en/references/auth-providers/zoom/page.mdx
@@ -24,7 +24,7 @@ This auth provider is used by:
 <Callout type="info">
   When using your own app credentials, make sure you configure your project to
   use a [custom user
-  verifier](/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
+  verifier](/en/guides/user-facing-agents/secure-auth-production#build-a-custom-user-verifier).
   Without this, your end-users will not be able to use your app or agent in
   production.
 </Callout>
@@ -78,14 +78,14 @@ Hit the **Create** button and the provider will be ready to be used.
 
 </Steps>
 
-When you use tools that require Zoom auth using your Arcade account credentials, Arcade will automatically use this Zoom OAuth provider. If you have multiple Zoom providers, see [using multiple auth providers of the same type](/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
+When you use tools that require Zoom auth using your Arcade account credentials, Arcade will automatically use this Zoom OAuth provider. If you have multiple Zoom providers, see [using multiple auth providers of the same type](/en/references/auth-providers#using-multiple-providers-of-the-same-type) for more information.
 
 </Tabs.Tab>
 </Tabs>
 
 ## Using Zoom auth in app code
 
-Use the Zoom auth provider in your own agents and AI apps to get a user token for the Zoom API. See [authorizing agents with Arcade](/get-started/about-arcade) to understand how this works.
+Use the Zoom auth provider in your own agents and AI apps to get a user token for the Zoom API. See [authorizing agents with Arcade](/en/get-started/about-arcade) to understand how this works.
 
 Use `client.auth.start()` to get a user token for the Zoom API:
 
@@ -151,7 +151,7 @@ const token = authResponse.context.token;
 
 ## Using Zoom auth in custom tools
 
-You can author your own [custom tools](/guides/create-tools/tool-basics/build-mcp-server) that interact with the Zoom API.
+You can author your own [custom tools](/en/guides/create-tools/tool-basics/build-mcp-server) that interact with the Zoom API.
 
 Use the `Zoom()` auth class to specify that a tool requires authorization with Zoom. The `context.authorization.token` field will be automatically populated with the user's Zoom token:
 
diff --git a/app/en/references/changelog/page.mdx b/app/en/references/changelog/page.mdx
index 2b4ef7f34..37004b96b 100644
--- a/app/en/references/changelog/page.mdx
+++ b/app/en/references/changelog/page.mdx
@@ -142,7 +142,7 @@ _Here's what's new at Arcade.dev!_
 
 <Callout type="info">
   Contextual Access for Tool Executions is Live! Learn more
-  [here](/guides/contextual-access)
+  [here](/en/guides/contextual-access)
 </Callout>
 
 **Arcade MCP Servers**
@@ -189,7 +189,7 @@ _Here's what's new at Arcade.dev!_
 
 **Arcade MCP Servers**
 
-- `[feature - 🚀]` Launched `https://ctl.arcade.dev/mcp` - Arcade's Gateway Assistant. Connect your LLM to help build MCP Gateways and MCP Servers for any agent use case. Learn more about it [here](/guides/mcp-gateways/create-via-ai)!
+- `[feature - 🚀]` Launched `https://ctl.arcade.dev/mcp` - Arcade's Gateway Assistant. Connect your LLM to help build MCP Gateways and MCP Servers for any agent use case. Learn more about it [here](/en/guides/mcp-gateways/create-via-ai)!
 
 **Platform and Engine**
 
@@ -221,12 +221,12 @@ _Here's what's new at Arcade.dev!_
 <Callout type="important">
   We've dramatically revamped our documentation to focus on making it easier to
   get started with Arcade. Update your links and let us know what you think
-  [here](/resources/contact-us)!
+  [here](/en/resources/contact-us)!
 </Callout>
 
 <Callout type="info">
   MCP Gateways now support OAuth! Learn more about it
-  [here](/guides/mcp-gateways)!
+  [here](/en/guides/mcp-gateways)!
 </Callout>
 
 **Arcade MCP Servers**
@@ -254,13 +254,13 @@ _Here's what's new at Arcade.dev!_
 
 **Arcade MCP Servers**
 
-- `[feature - 🚀]` OAuth authentication for `arcade-mcp` servers. Learn more about it [here](/guides/create-tools/secure-your-server/secure-your-mcp-server)
+- `[feature - 🚀]` OAuth authentication for `arcade-mcp` servers. Learn more about it [here](/en/guides/create-tools/secure-your-server/secure-your-mcp-server)
 - `[maintenance - 🔧]` Ability to run multiple uvicorn workers
 - `[maintenance - 🔧]` Include type annotations for `arcade_mcp_server`
 
 **Arcade CLI**
 
-- `[feature - 🚀]` Support multiple orgs & projects in Arcade's CLI. Learn more about it [here](/references/arcade-cli)!
+- `[feature - 🚀]` Support multiple orgs & projects in Arcade's CLI. Learn more about it [here](/en/references/arcade-cli)!
 
 **Platform and Engine**
 
@@ -406,21 +406,21 @@ _Here's what's new at Arcade.dev!_
 <Callout type="important">
   We've updated our documentation to be more clear, consistent, and easier to
   navigate. This includes updated quickstarts, guides, and reference
-  information. [Let us know what you think](/resources/contact-us)!
+  information. [Let us know what you think](/en/resources/contact-us)!
 </Callout>
 
 <Callout type="info">
   This week we released `arcade-mcp`, the best way to build MCP Servers.
   `arcade-mcp` supersedes the Arcade TDK. Learn more about it
-  [here](/get-started/quickstarts/mcp-server-quickstart)! Detailed reference
-  information for `arcade-mcp` is available [here](/references/mcp/python).
+  [here](/en/get-started/quickstarts/mcp-server-quickstart)! Detailed reference
+  information for `arcade-mcp` is available [here](/en/references/mcp/python).
 </Callout>
 
 <Callout type="info">
   This week MCP Gateways are now generally available! MCP Gateways allow you to
   federate the tools from multiple MCP Servers into a single collection for
   easier management, control, and access. Learn more about them
-  [here](/guides/create-tools/mcp-gateways!
+  [here](/en/guides/create-tools/mcp-gateways!
 </Callout>
 
 <Callout type="info">
@@ -431,7 +431,7 @@ _Here's what's new at Arcade.dev!_
 
 **Toolkits**
 
-- `[feature - 🚀]` `arcade-mcp` is now generally available! Learn more about it [here](/get-started/quickstarts/mcp-server-quickstart)!
+- `[feature - 🚀]` `arcade-mcp` is now generally available! Learn more about it [here](/en/get-started/quickstarts/mcp-server-quickstart)!
 - `[feature - 🚀]` [Toolkits/BrightData] Added BrightData Toolkit
 - `[feature - 🚀]` [Toolkits/Figma] Added Figma Starter MCP Server
 - `[feature - 🚀]` [Toolkits/Freshservice] Added Freshservice Starter MCP Server
@@ -444,14 +444,14 @@ _Here's what's new at Arcade.dev!_
 **Platform and Engine**
 
 - `[feature - 🚀]` Dashboard: Allow OAuth on MCP Servers
-- `[feature - 🚀]` MCP Gateways are now generally available! Learn more about them [here](/guides/create-tools/mcp-gateways!
+- `[feature - 🚀]` MCP Gateways are now generally available! Learn more about them [here](/en/guides/create-tools/mcp-gateways!
 - `[feature - 🚀]` Projects are now generally available.
 - `[maintenance - 🔧]` Support remote MCP servers which require DCR (dynamic client registration).
 
 **Misc**
 
 - `[documentation - 📝]` Updated documentation to be more clear, consistent, and easier to navigate. This includes updated quickstarts, guides, and reference information.
-- `[documentation - 📝]` `llms.txt` is now kept up to date and simplified. We've also added a new section to the docs for [agentic development](/get-started/setup/connect-arcade-docs).
+- `[documentation - 📝]` `llms.txt` is now kept up to date and simplified. We've also added a new section to the docs for [agentic development](/en/get-started/setup/connect-arcade-docs).
 
 ## 2025-10-10
 
@@ -478,8 +478,8 @@ _Here's what's new at Arcade.dev!_
 
 **Toolkits**
 
-- `[feature - 🚀]` Box.com Starter MCP Server released ([docs](/resources/integrations/productivity/boxapi))
-- `[feature - 🚀]` Stripe Starter MCP Server released ([docs](/resources/integrations/payments/stripeapi))
+- `[feature - 🚀]` Box.com Starter MCP Server released ([docs](/en/resources/integrations/productivity/boxapi))
+- `[feature - 🚀]` Stripe Starter MCP Server released ([docs](/en/resources/integrations/payments/stripeapi))
 
 **Misc**
 
@@ -489,9 +489,9 @@ _Here's what's new at Arcade.dev!_
 
 **Toolkits**
 
-- `[feature - 🚀]` Introduce [Unoptimized tools](/guides/create-tools/improve/types-of-tools), a new type of tool that mirrors the original HTTP API design of the upstream service.
+- `[feature - 🚀]` Introduce [Unoptimized tools](/en/guides/create-tools/improve/types-of-tools), a new type of tool that mirrors the original HTTP API design of the upstream service.
 - `[feature - 🚀]` Release Slack started MCP Server which contains support for most of the Slack API.
-- `[feature - 🚀]` Include advanced error handling in the following MCP Servers: Google, Microsoft, Slack, and Asana. Learn more about handling tool errors [here](/guides/create-tools/error-handling/useful-tool-errors).
+- `[feature - 🚀]` Include advanced error handling in the following MCP Servers: Google, Microsoft, Slack, and Asana. Learn more about handling tool errors [here](/en/guides/create-tools/error-handling/useful-tool-errors).
 - `[bugfix - 🐛]` [MCP Servers/MS Teams] Fix get_chat_metadata by chat's users
 - `[feature - 🚀]` [MCP Servers/confluence] Adding WhoAmI tools for Confluence
 
@@ -617,7 +617,7 @@ _Here's what's new at Arcade.dev!_
 
 **Toolkits**
 
-- `[feature - 🚀]` Sharepoint Toolkit added ([docs](/resources/integrations/productivity/microsoft-sharepoint))
+- `[feature - 🚀]` Sharepoint Toolkit added ([docs](/en/resources/integrations/productivity/microsoft-sharepoint))
 - `[feature - 🚀]` Google Slides Toolkit added
 - `[feature - 🚀]` Commenting on Google Docs added
 - `[bugfix - 🐛]` Improvements in Microsoft Teams message search tool for better agentic experience. Fix bug when no messages match the search query.
@@ -698,7 +698,7 @@ _Here's what's new at Arcade.dev!_
 ## 2025-07-18
 
 <Callout type="info">
-  Version 2.0.0 of the Arcade Engine was released this week.  Upgrading to version 2.0.0 is recommended for all self-hosted developers, and includes an important security fix for [secure OAuth flows](/guides/user-facing-agents/secure-auth-production).  After upgrading, all projects will default to using the Arcade user verifier.  If desired, you can then implement a custom user verifier in your application/agent and make the switch via the Arcade Dashboard.
+  Version 2.0.0 of the Arcade Engine was released this week.  Upgrading to version 2.0.0 is recommended for all self-hosted developers, and includes an important security fix for [secure OAuth flows](/en/guides/user-facing-agents/secure-auth-production).  After upgrading, all projects will default to using the Arcade user verifier.  If desired, you can then implement a custom user verifier in your application/agent and make the switch via the Arcade Dashboard.
 
 Self-hosed Arcade developers cannot be grandfathered into the old (insecure) behavior of skipping user verification once the Engine is upgraded to version 2.0.0 or higher.
 
@@ -784,11 +784,11 @@ Self-hosed Arcade developers cannot be grandfathered into the old (insecure) beh
 
 **Frameworks**
 
-- `[feature - 🚀]` Support for OpenAI Agent SDK in Typescript ([docs](/get-started/agent-frameworks/openai-agents/overview))
+- `[feature - 🚀]` Support for OpenAI Agent SDK in Typescript ([docs](/en/get-started/agent-frameworks/openai-agents/overview))
 
 **Toolkits**
 
-- `[feature - 🚀]` Jira MCP Server released ([docs](/resources/integrations/productivity/jira))
+- `[feature - 🚀]` Jira MCP Server released ([docs](/en/resources/integrations/productivity/jira))
 
 **CLI and TDK**
 
@@ -800,7 +800,7 @@ Self-hosed Arcade developers cannot be grandfathered into the old (insecure) beh
 
 - `[feature - 🚀]` Admin APIs released for managing users, secrets, and tools ([API References](https://reference.arcade.dev/api-reference#tag/admin))
 - `[bugfix - 🐛]` Unauthenticated MCP servers can be called anonymously
-- `[feature - 🚀]` End-user credentials and auth status can be fetched in batches ([docs](/guides/tool-calling/custom-apps/check-auth-status))
+- `[feature - 🚀]` End-user credentials and auth status can be fetched in batches ([docs](/en/guides/tool-calling/custom-apps/check-auth-status))
 
 **Misc**
 
diff --git a/app/en/references/cli-cheat-sheet/page.mdx b/app/en/references/cli-cheat-sheet/page.mdx
index cf2abf4f0..97e244433 100644
--- a/app/en/references/cli-cheat-sheet/page.mdx
+++ b/app/en/references/cli-cheat-sheet/page.mdx
@@ -60,7 +60,7 @@ import '../../../cheat-sheet-print.css'
 
     <InfoBox type="tip">Use `uv` for faster installs and better dependency management</InfoBox>
     <InfoBox type="tip">
-      Using Windows and PowerShell? See [Windows environment setup](/get-started/setup/windows-environment) for install options with and without `uv`.
+      Using Windows and PowerShell? See [Windows environment setup](/en/get-started/setup/windows-environment) for install options with and without `uv`.
     </InfoBox>
 
   </CheatSheetSection>
diff --git a/app/en/references/mcp/python/page.mdx b/app/en/references/mcp/python/page.mdx
index e09614252..dc1fadd9c 100644
--- a/app/en/references/mcp/python/page.mdx
+++ b/app/en/references/mcp/python/page.mdx
@@ -133,7 +133,7 @@ def settings_handler(uri: str) -> str:
     ...
 ```
 
-Decorator for registering resources and resource templates. See [Resources](/references/mcp/python/resources) for full documentation.
+Decorator for registering resources and resource templates. See [Resources](/en/references/mcp/python/resources) for full documentation.
 
 #### `add_resource`
 
@@ -141,7 +141,7 @@ Decorator for registering resources and resource templates. See [Resources](/ref
 app.add_resource(uri, name=None, handler=my_handler, ...)
 ```
 
-Imperative form of `@app.resource`. See [Resources](/references/mcp/python/resources) for full documentation.
+Imperative form of `@app.resource`. See [Resources](/en/references/mcp/python/resources) for full documentation.
 
 #### `add_text_resource`
 
@@ -149,7 +149,7 @@ Imperative form of `@app.resource`. See [Resources](/references/mcp/python/resou
 app.add_text_resource(uri, text="...", name=None, ...)
 ```
 
-Register a static text resource. See [Resources](/references/mcp/python/resources) for full documentation.
+Register a static text resource. See [Resources](/en/references/mcp/python/resources) for full documentation.
 
 #### `add_file_resource`
 
@@ -157,7 +157,7 @@ Register a static text resource. See [Resources](/references/mcp/python/resource
 app.add_file_resource(uri, path="path/to/file", name=None, ...)
 ```
 
-Register a file-backed resource. See [Resources](/references/mcp/python/resources) for full documentation.
+Register a file-backed resource. See [Resources](/en/references/mcp/python/resources) for full documentation.
 
 #### `add_tool`
 
diff --git a/app/en/references/mcp/python/server/page.mdx b/app/en/references/mcp/python/server/page.mdx
index 6f86eaf9d..8dfb1d4e7 100644
--- a/app/en/references/mcp/python/server/page.mdx
+++ b/app/en/references/mcp/python/server/page.mdx
@@ -8,7 +8,7 @@ import { Callout } from "nextra/components";
 # Server
 
 <Callout type="info">
-  Most users should use [`MCPApp`](/references/mcp/python) instead of `MCPServer` directly. `MCPServer` is a low-level API for advanced use cases.
+  Most users should use [`MCPApp`](/en/references/mcp/python) instead of `MCPServer` directly. `MCPServer` is a low-level API for advanced use cases.
 </Callout>
 
 The `MCPServer` class is the core server implementation that handles MCP protocol messages, middleware orchestration, and component management for tools, resources, and prompts.
diff --git a/app/en/references/mcp/telemetry/page.mdx b/app/en/references/mcp/telemetry/page.mdx
index 1c0e9db49..68166a1d2 100644
--- a/app/en/references/mcp/telemetry/page.mdx
+++ b/app/en/references/mcp/telemetry/page.mdx
@@ -26,7 +26,7 @@ This data will let us better tailor Arcade to the masses, ensuring its continued
 
 We track general usage information for the `arcade-mcp` product, including:
 
-- Command invoked (e.g., `arcade new`, `arcade evals`, other commands listed [here](/references/arcade-cli) )
+- Command invoked (e.g., `arcade new`, `arcade evals`, other commands listed [here](/en/references/arcade-cli) )
 - Count of local tool executions (we do NOT collect tool names, parameters, or any other personally identifiable information related to the tools you or your agents execute locally or when self-hosted)
 - General machine information (e.g., macOS/Windows/Linux, whether the command was run within the CLI)
 - Duration of commands
diff --git a/app/en/references/page.mdx b/app/en/references/page.mdx
index bff9c24f7..273527066 100644
--- a/app/en/references/page.mdx
+++ b/app/en/references/page.mdx
@@ -30,7 +30,7 @@ Complete reference documentation for Arcade's APIs, MCP servers, and available a
             asChild
             className="bg-primary text-white hover:bg-primary/90"
           >
-            <Link href="/references/api">View API Reference</Link>
+            <Link href="/en/references/api">View API Reference</Link>
           </Button>
         </div>
       </div>
@@ -50,7 +50,7 @@ Complete reference documentation for Arcade's APIs, MCP servers, and available a
             asChild
             className="bg-primary text-white hover:bg-primary/90"
           >
-            <Link href="/references/mcp/python">
+            <Link href="/en/references/mcp/python">
               View SDK Reference
             </Link>
           </Button>
diff --git a/app/en/resources/examples/page.mdx b/app/en/resources/examples/page.mdx
index 1aefa332e..349c0ccb1 100644
--- a/app/en/resources/examples/page.mdx
+++ b/app/en/resources/examples/page.mdx
@@ -128,7 +128,7 @@ Built something with Arcade? The team would love to feature it! Submit your app
 
 #### Need help?
 
-If you have questions about submitting your app, feel free to [contact the team](/resources/contact-us) or open an issue in the docs repository.
+If you have questions about submitting your app, feel free to [contact the team](/en/resources/contact-us) or open an issue in the docs repository.
 
 </Tabs.Tab>
 <Tabs.Tab>
@@ -166,7 +166,7 @@ Built an MCP server with Arcade? The team would love to feature it! Submit your
 
 #### Need help?
 
-If you have questions about submitting your MCP server, feel free to [contact the team](/resources/contact-us) or open an issue in the docs repository.
+If you have questions about submitting your MCP server, feel free to [contact the team](/en/resources/contact-us) or open an issue in the docs repository.
 
 </Tabs.Tab>
 </Tabs>
diff --git a/app/en/resources/faq/page.mdx b/app/en/resources/faq/page.mdx
index b00f027bd..7546db029 100644
--- a/app/en/resources/faq/page.mdx
+++ b/app/en/resources/faq/page.mdx
@@ -12,7 +12,7 @@ import { Tabs } from "nextra/components";
 
 ## What if I need a Tool that Arcade doesn't have?
 
-Arcade makes it easy to build your own tools! You can fork our existing tools, or build your own from scratch. Learn more about [building your own MCP Server](/guides/create-tools/tool-basics/build-mcp-server).
+Arcade makes it easy to build your own tools! You can fork our existing tools, or build your own from scratch. Learn more about [building your own MCP Server](/en/guides/create-tools/tool-basics/build-mcp-server).
 
 ## How do I contribute back a Tool to the Registry?
 
@@ -20,7 +20,7 @@ We're always looking for new tools and MCP Servers! If you have a tool that you
 
 ## What is the difference between the Arcade CLI and the Arcade Clients?
 
-The [Arcade CLI](/references/arcade-cli) is a command line tool that makes it easy to build, test, and deploy your own tools to production. The [Arcade Client libraries](/references) are what you will use within your own agents and applications to call the tools.
+The [Arcade CLI](/en/references/arcade-cli) is a command line tool that makes it easy to build, test, and deploy your own tools to production. The [Arcade Client libraries](/en/references) are what you will use within your own agents and applications to call the tools.
 
 ## What is the difference between personal API keys and project API keys?
 
@@ -32,7 +32,7 @@ Arcade now uses **project API keys** as the standard way to authenticate with th
 - **Clearer organization**: Keys are organized by project, making it easier to manage multiple projects and their respective resources and permissions.
 - **Simplified key management**: Manage one key per project instead of individual keys for each team member.
 
-If you're still using a personal API key, we recommend migrating to a project API key. Learn more about [API keys](/get-started/setup/api-keys) and how to create them.
+If you're still using a personal API key, we recommend migrating to a project API key. Learn more about [API keys](/en/get-started/setup/api-keys) and how to create them.
 
 ## Auth FAQ
 
@@ -49,7 +49,7 @@ Please [contact us](mailto:support@arcade.dev) if you need this feature.
 Yes, as long as they are from the same OAuth provider. You need to collect all
 the scopes required by the tools you need, and then authenticate with that
 provider with all these scopes. For example, for [Google
-Tools](/references/auth-providers/google, you can use this code to authenticate once:
+Tools](/en/references/auth-providers/google, you can use this code to authenticate once:
 
 <Tabs items={["Python", "JavaScript"]} storageKey="preferredLanguage">
 <Tabs.Tab>
diff --git a/app/en/resources/glossary/page.mdx b/app/en/resources/glossary/page.mdx
index f46eada38..67d03194b 100644
--- a/app/en/resources/glossary/page.mdx
+++ b/app/en/resources/glossary/page.mdx
@@ -29,7 +29,7 @@ This (Reason + Act) is the most common agentic pattern, where an LLM runs in a l
 
 A 'Context' is an object that is passed to a tool as a parameter when the tool is executed. It contains information about the tool call, the user for which the tool is being called, and any secrets the tool requires to run.
 
-_Learn more about [context](/guides/create-tools/tool-basics/runtime-data-access)._
+_Learn more about [context](/en/guides/create-tools/tool-basics/runtime-data-access)._
 
 ### Entrypoint File
 
@@ -67,25 +67,25 @@ An unprotected (anonymous) MCP server can be used by any MCP client on the netwo
 
 A 'tool' is a function that can be called by an agent which performs some action - commonly via an API, filesystem, database, etc. Tools are written in Python and deployed by running a worker which contains the MCP Server's code. Tools are defined by the `@tool()` decorator and will be passed `ToolContext` as the first argument. If a tool has dependencies that are not met (a secret is not provided, for example), the tool will fail to execute.
 
-Tools are commonly referred to by a qualified name that includes their MCP Server. For example, [Gmail.SendEmail](/resources/integrations/productivity/gmail#gmailsendemail)
+Tools are commonly referred to by a qualified name that includes their MCP Server. For example, [Gmail.SendEmail](/en/resources/integrations/productivity/gmail#gmailsendemail)
 
-_Learn more about [tools](/guides/create-tools/tool-basics/build-mcp-server)._
+_Learn more about [tools](/en/guides/create-tools/tool-basics/build-mcp-server)._
 
 #### Optimized tools
 
-[Optimized tools](/guides/create-tools/improve/types-of-tools#optimized-tools) are designed from scratch to provide the best performance for LLMs in terms of speed, reliability, accuracy, and cost-effectiveness.
+[Optimized tools](/en/guides/create-tools/improve/types-of-tools#optimized-tools) are designed from scratch to provide the best performance for LLMs in terms of speed, reliability, accuracy, and cost-effectiveness.
 
 #### Unoptimized tools
 
-[Unoptimized tools](/guides/create-tools/improve/types-of-tools#unoptimized-tools) are designed to mirror the original HTTP API design of the upstream service. They are not optimized for LLM usage and are not subject to evaluation suites. We recommend thoroughly evaluating each Unoptimized tool with your Agents or chatbots before using it in production.
+[Unoptimized tools](/en/guides/create-tools/improve/types-of-tools#unoptimized-tools) are designed to mirror the original HTTP API design of the upstream service. They are not optimized for LLM usage and are not subject to evaluation suites. We recommend thoroughly evaluating each Unoptimized tool with your Agents or chatbots before using it in production.
 
-Understand why [LLMs perform poorly when](/guides/create-tools/improve/types-of-tools#why-llms-perform-poorly when-calling-http-apis) calling HTTP APIs.
+Understand why [LLMs perform poorly when](/en/guides/create-tools/improve/types-of-tools#why-llms-perform-poorly when-calling-http-apis) calling HTTP APIs.
 
 ### Tool Context
 
 'Tool context' is an object that is passed to a tool as a parameter when the tool is executed. It contains information about the tool call, the user for which the tool is being called, and any secrets the tool requires to run.
 
-_Learn more about [tool context](/guides/create-tools/tool-basics/runtime-data-access)._
+_Learn more about [tool context](/en/guides/create-tools/tool-basics/runtime-data-access)._
 
 ### Transport Modes
 
@@ -128,7 +128,7 @@ A 'project' is a collection of agents and tools. It is smallest unit of organiza
 
 ### Arcade API
 
-The 'Arcade API' is a set of endpoints that allow you to interact with the Arcade platform. You can use the API to call tools, get tool definitions, manage user auth, and more. See the [Arcade API Reference](/references/api) for more details.
+The 'Arcade API' is a set of endpoints that allow you to interact with the Arcade platform. You can use the API to call tools, get tool definitions, manage user auth, and more. See the [Arcade API Reference](/en/references/api) for more details.
 
 ### API Key
 
@@ -158,19 +158,19 @@ User Challenges are the count of authorizations performed for any user (specifie
 
 An 'auth provider' is a service that your users sign in with to let the agent access their data or take actions on their behalf. This can be a hosted service like Google or Slack, or a custom OAuth provider. Multiple MCP Servers may share the same auth provider (for example, Gmail and Google Drive both use Google's OAuth provider). Custom auth providers are defined in the Arcade Dashboard, or in your Engine YAML if you're self-hosting.
 
-_Learn more about [auth providers](/references/auth-providers)._
+_Learn more about [auth providers](/en/references/auth-providers)._
 
 ### Authorization Scope
 
 An 'authorization scope' is a permission that a user can grant to an agent. This is used to control what the agent can do with the user's data. Available authorization scopes are defined by the authentication provider, and each tool defines the scopes it requires.
 
-Learn more about [authorized tool calling](/guides/tool-calling/custom-apps/auth-tool-calling).
+Learn more about [authorized tool calling](/en/guides/tool-calling/custom-apps/auth-tool-calling).
 
 ### Tool Executions
 
 A 'tool execution' is a single call to a tool to interact with a remote system or service. The tool execution itself may fail (e.g. the user does not have permission to call the tool), but as long as the execution was able to be routed to a worker, it will be counted.
 
-_Learn more about [tool executions](/guides/tool-calling)._
+_Learn more about [tool executions](/en/guides/tool-calling)._
 
 ### Standard and Pro Tool Executions
 
@@ -206,7 +206,7 @@ graph TD
 
 The 'Arcade client' is the SDK that you use to interact with the Arcade platform. It is how your agent lists and calls tools, tied back to your project via an API key. We offer clients for many popular languages and frameworks, including Python, JavaScript, and more.
 
-_Learn more about [the Arcade clients](/references)._
+_Learn more about [the Arcade clients](/en/references)._
 
 ### Arcade Engine
 
@@ -226,4 +226,4 @@ Arcade MCP is the secure framework for building MCP servers. It is responsible f
 
 Evaluations are a way to test the LLMs' ability to select and call your tools. Arcade's eval suite can and should be run as part of the development process to ensure your tools are working as expected.
 
-_Learn more about evaluations [here](/guides/create-tools/evaluate-tools/why-evaluate)._
+_Learn more about evaluations [here](/en/guides/create-tools/evaluate-tools/why-evaluate)._
diff --git a/app/en/resources/integrations/search/tavily/page.mdx b/app/en/resources/integrations/search/tavily/page.mdx
index a7dde7909..8cfab4a23 100644
--- a/app/en/resources/integrations/search/tavily/page.mdx
+++ b/app/en/resources/integrations/search/tavily/page.mdx
@@ -7,7 +7,7 @@ import { Callout, Steps } from "nextra/components";
 
 # Tavily
 
-This integration is a remote MCP Server offered by [Tavily](https://tavily.com), an Arcade Partner. Add it to an [MCP Gateway](/guides/mcp-gateways/add-remote-servers) for central governance, authorization, and access control alongside Arcade's native servers.
+This integration is a remote MCP Server offered by [Tavily](https://tavily.com), an Arcade Partner. Add it to an [MCP Gateway](/en/guides/mcp-gateways/add-remote-servers) for central governance, authorization, and access control alongside Arcade's native servers.
 
 ## MCP Server URL
 
@@ -45,7 +45,7 @@ Go to [tavily.com](https://tavily.com) → **Overview** → **Generate MCP Link*
 Open the [Arcade Dashboard](https://api.arcade.dev/dashboard) → **Servers** → **Add Server** → **Remote MCP**. Paste the URL from the [MCP Server URL](#mcp-server-url) section above (with your API key in place of `YOUR_API_KEY`) and save.
 
 <Callout type="info">
-  See the full walkthrough in <a href="/guides/mcp-gateways/add-remote-servers">Add remote MCP servers</a> for advanced settings like connection retries, OAuth, and custom headers.
+  See the full walkthrough in <a href="/en/guides/mcp-gateways/add-remote-servers">Add remote MCP servers</a> for advanced settings like connection retries, OAuth, and custom headers.
 </Callout>
 
 ### Verify Tavily tools
@@ -75,6 +75,6 @@ See the open-source [Financial Intelligence Agent](https://github.com/arcadeai-l
 ## Resources
 
 - [Tavily documentation](https://docs.tavily.com)
-- [Add remote MCP servers to Arcade](/guides/mcp-gateways/add-remote-servers)
-- [Create an MCP Gateway](/guides/mcp-gateways/create-via-dashboard)
-- [Connect to MCP clients](/get-started/mcp-clients)
+- [Add remote MCP servers to Arcade](/en/guides/mcp-gateways/add-remote-servers)
+- [Create an MCP Gateway](/en/guides/mcp-gateways/create-via-dashboard)
+- [Connect to MCP clients](/en/get-started/mcp-clients)
diff --git a/app/en/resources/registry-early-access/page.mdx b/app/en/resources/registry-early-access/page.mdx
index 0ae0a81df..54830dee8 100644
--- a/app/en/resources/registry-early-access/page.mdx
+++ b/app/en/resources/registry-early-access/page.mdx
@@ -14,7 +14,7 @@ The **Arcade Registry** is how agentic tool developers share their work with the
 <TakeSurvey />
 
 **_The components of the Arcade Registry_**
-![The Arcade Registry diagram](/images/registry/registry.png)
+![The Arcade Registry diagram](/en/images/registry/registry.png)
 
 Unlike traditional read-only tool libraries, Arcade.dev couples the runtime with the registry. This way we can collect real metrics and usage information about your tools, sharing meaningful information and feedback back to the developers. You'll get error reports and statistics about how your tools are getting used. Arcade.dev also makes it possible for developers to optionally choose to sell their tools with a markup on top of the Arcade platform fees.
 
diff --git a/app/en/resources/tools/page.mdx b/app/en/resources/tools/page.mdx
index 6b8a0e017..42a4d723f 100644
--- a/app/en/resources/tools/page.mdx
+++ b/app/en/resources/tools/page.mdx
@@ -6,19 +6,19 @@ Arcade provides a comprehensive ecosystem for AI tools that enable your agents t
 
 Discover thousands of ready-to-use tools for popular services like Gmail, Slack, GitHub, and more. Our catalog contains production-ready MCP servers that handle authentication, permissions, and API integrations seamlessly.
 
-[Browse Tool Catalog →](/resources/integrations)
+[Browse Tool Catalog →](/en/resources/integrations)
 
 ## Create Your Own Tools
 
 Build custom tools tailored to your specific needs using our powerful development framework. Create MCP servers, define tool schemas, and deploy them to production with ease.
 
-[Learn to Build Tools →](/guides/create-tools/tool-basics/build-mcp-server)
+[Learn to Build Tools →](/en/guides/create-tools/tool-basics/build-mcp-server)
 
 ## Contribute to the Catalog
 
 Share your tools with the Arcade community and help expand our ecosystem. Submit your MCP servers to make them available to developers worldwide.
 
-[Add Your Tools to the Catalog →](/resources/registry-early-access)
+[Add Your Tools to the Catalog →](/en/resources/registry-early-access)
 
 ## Why Choose Arcade Tools?
 
diff --git a/next.config.ts b/next.config.ts
index 5f4317567..041f76d3c 100644
--- a/next.config.ts
+++ b/next.config.ts
@@ -24,6 +24,950 @@ const nextConfig: NextConfig = withLlmsTxt({
   withNextra({
     async redirects() {
       return [
+        // Locale-less siblings for single-hop redirect (D-1)
+        {
+          source: "/home/auth/authorized-tool-calling",
+          destination: "/en/guides/tool-calling/custom-apps/auth-tool-calling",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/create-a-toolkit",
+          destination: "/en/guides/create-tools/tool-basics",
+          permanent: true,
+        },
+        {
+          source: "/home/configure/arcade-deploy",
+          destination: "/en/guides/deployment-hosting/arcade-deploy",
+          permanent: true,
+        },
+        {
+          source: "/home/hybrid-deployment/hybrid-worker",
+          destination: "/en/guides/deployment-hosting",
+          permanent: true,
+        },
+        {
+          source: "/home/local-deployment/install/local",
+          destination: "/en/guides/deployment-hosting/on-prem",
+          permanent: true,
+        },
+        {
+          source: "/home/local-deployment/install/overview",
+          destination: "/en/guides/deployment-hosting",
+          permanent: true,
+        },
+        {
+          source: "/references/auth-providers/squareup",
+          destination: "/en/references/auth-providers/square",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/entertainment/twitch",
+          destination: "/en/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social/discord",
+          destination: "/en/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social/twilio",
+          destination: "/en/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/obsidian",
+          destination: "/en/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/closeio",
+          destination: "/en/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/daytona/overview",
+          destination: "/en/resources/integrations/development/daytona",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/google/gmail",
+          destination: "/en/resources/integrations/productivity/gmail",
+          permanent: true,
+        },
+        {
+          source: "/guides/security/security-research-program",
+          destination: "/en/resources/security-research-program",
+          permanent: true,
+        },
+        {
+          source: "/guides/security/securing-arcade-mcp",
+          destination: "/en/guides/create-tools/secure-your-server",
+          permanent: true,
+        },
+        {
+          source: "/guides/security/secure-your-mcp-server",
+          destination:
+            "/en/guides/create-tools/secure-your-server/secure-your-mcp-server",
+          permanent: true,
+        },
+        {
+          source: "/guides/security",
+          destination: "/en/guides/create-tools/secure-your-server",
+          permanent: true,
+        },
+        {
+          source: "/references/mcp/python/transports",
+          destination: "/en/references/mcp/python",
+          permanent: true,
+        },
+        {
+          source: "/references/mcp/python/types",
+          destination: "/en/references/mcp/python",
+          permanent: true,
+        },
+        {
+          source: "/get-started/agent-frameworks/crewai/custom-auth-flow",
+          destination:
+            "/en/get-started/agent-frameworks/crewai/use-arcade-tools",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/others/:path*",
+          destination: "/en/resources/integrations",
+          permanent: false,
+        },
+        {
+          source: "/get-started/agent-frameworks/google-adk/use-arcade-tools",
+          destination: "/en/get-started/agent-frameworks/google-adk/overview",
+          permanent: true,
+        },
+        {
+          source: "/references/logic-extensions-api",
+          destination: "/en/references/contextual-access-webhook-api",
+          permanent: true,
+        },
+        {
+          source: "/guides/logic-extensions",
+          destination: "/en/guides/contextual-access",
+          permanent: true,
+        },
+        {
+          source: "/guides/logic-extensions/build-your-own",
+          destination: "/en/guides/contextual-access/build-your-own",
+          permanent: true,
+        },
+        {
+          source: "/guides/logic-extensions/examples",
+          destination: "/en/guides/contextual-access/examples",
+          permanent: true,
+        },
+        {
+          source: "/guides/logic-extensions/how-hooks-work",
+          destination: "/en/guides/contextual-access/how-hooks-work",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/preview",
+          destination: "/en/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/customer-support/zendesk/reference",
+          destination: "/en/resources/integrations/customer-support/zendesk",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/development/firecrawl/reference",
+          destination: "/en/resources/integrations/development/firecrawl",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/asana/reference",
+          destination: "/en/resources/integrations/productivity/asana",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/clickup/reference",
+          destination: "/en/resources/integrations/productivity/clickup",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/dropbox/reference",
+          destination: "/en/resources/integrations/productivity/dropbox",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/gmail/reference",
+          destination: "/en/resources/integrations/productivity/gmail",
+          permanent: true,
+        },
+        {
+          source:
+            "/resources/integrations/productivity/google-calendar/reference",
+          destination:
+            "/en/resources/integrations/productivity/google-calendar",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/google-docs/reference",
+          destination: "/en/resources/integrations/productivity/google-docs",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/google-drive/reference",
+          destination: "/en/resources/integrations/productivity/google-drive",
+          permanent: true,
+        },
+        {
+          source:
+            "/resources/integrations/productivity/google-sheets/reference",
+          destination: "/en/resources/integrations/productivity/google-sheets",
+          permanent: true,
+        },
+        {
+          source:
+            "/resources/integrations/productivity/jira/environment-variables",
+          destination: "/en/resources/integrations/productivity/jira",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/jira/reference",
+          destination: "/en/resources/integrations/productivity/jira",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/sales/hubspot/reference",
+          destination: "/en/resources/integrations/sales/hubspot",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social-communication/discord",
+          destination: "/en/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social-communication/linkedin",
+          destination: "/en/resources/integrations/social/linkedin",
+          permanent: true,
+        },
+        {
+          source:
+            "/resources/integrations/social-communication/microsoft-teams",
+          destination: "/en/resources/integrations/social/microsoft-teams",
+          permanent: true,
+        },
+        {
+          source:
+            "/resources/integrations/social-communication/microsoft-teams/reference",
+          destination: "/en/resources/integrations/social/microsoft-teams",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social-communication/reddit",
+          destination: "/en/resources/integrations/social/reddit",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social-communication/slack-api",
+          destination: "/en/resources/integrations/social/slack-api",
+          permanent: true,
+        },
+        {
+          source:
+            "/resources/integrations/social-communication/slack/environment-variables",
+          destination: "/en/resources/integrations/social/slack",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social-communication/slack/install",
+          destination: "/en/resources/integrations/social/slack",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social-communication/slack",
+          destination: "/en/resources/integrations/social/slack",
+          permanent: true,
+        },
+        {
+          source:
+            "/resources/integrations/social-communication/slack/reference",
+          destination: "/en/resources/integrations/social/slack",
+          permanent: true,
+        },
+        {
+          source:
+            "/resources/integrations/social-communication/teams/reference",
+          destination: "/en/resources/integrations/social/microsoft-teams",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social-communication/twilio",
+          destination: "/en/resources/integrations",
+          permanent: true,
+        },
+        {
+          source:
+            "/resources/integrations/social-communication/twilio/reference",
+          destination: "/en/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social-communication/x",
+          destination: "/en/resources/integrations/social/x",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social-communication/zoom/install",
+          destination: "/en/resources/integrations/social/zoom",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/social-communication/zoom",
+          destination: "/en/resources/integrations/social/zoom",
+          permanent: true,
+        },
+        {
+          source: "/guides/create-tools/contribute/registry-early-access",
+          destination: "/en/resources/registry-early-access",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/contribute-a-server",
+          destination: "/en/resources/registry-early-access",
+          permanent: true,
+        },
+        {
+          source: "/guides/create-tools/mcp-gateways",
+          destination: "/en/guides/mcp-gateways",
+          permanent: true,
+        },
+        {
+          source: "/get-started/agent-frameworks/langchain/use-arcade-tools",
+          destination:
+            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
+          permanent: true,
+        },
+        {
+          source:
+            "/get-started/agent-frameworks/langchain/user-auth-interrupts",
+          destination:
+            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
+          permanent: true,
+        },
+        {
+          source: "/get-started/agent-frameworks/mastra/overview",
+          destination: "/en/get-started/agent-frameworks/mastra",
+          permanent: true,
+        },
+        {
+          source: "/get-started/agent-frameworks/mastra/use-arcade-tools",
+          destination: "/en/get-started/agent-frameworks/mastra",
+          permanent: true,
+        },
+        {
+          source: "/get-started/agent-frameworks/mastra/user-auth-interrupts",
+          destination: "/en/get-started/agent-frameworks/mastra",
+          permanent: true,
+        },
+        {
+          source:
+            "/get-started/agent-frameworks/openai-agents/use-arcade-with-openai-agents",
+          destination:
+            "/en/get-started/agent-frameworks/openai-agents/overview",
+          permanent: true,
+        },
+        {
+          source:
+            "/get-started/agent-frameworks/openai-agents/use-arcade-tools",
+          destination:
+            "/en/get-started/agent-frameworks/openai-agents/overview",
+          permanent: true,
+        },
+        {
+          source:
+            "/get-started/agent-frameworks/openai-agents/user-auth-interrupts",
+          destination:
+            "/en/get-started/agent-frameworks/openai-agents/overview",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/setup-arcade-with-your-llm-python",
+          destination:
+            "/en/get-started/agent-frameworks/setup-arcade-with-your-llm-python",
+          permanent: true,
+        },
+        {
+          source: "/home/langchain/use-arcade-tools",
+          destination:
+            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/langchain/use-arcade-tools",
+          destination:
+            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
+          permanent: true,
+        },
+        {
+          source: "/home/langchain/user-auth-interrupts",
+          destination:
+            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/langchain/user-auth-interrupts",
+          destination:
+            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
+          permanent: true,
+        },
+        {
+          source:
+            "/get-started/agent-frameworks/langchain/use-arcade-with-langchain",
+          destination:
+            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
+          permanent: true,
+        },
+        {
+          source: "/home/oai-agents/user-auth-interrupts",
+          destination:
+            "/en/get-started/agent-frameworks/openai-agents/overview",
+          permanent: true,
+        },
+        {
+          source: "/home/mastra/user-auth-interrupts",
+          destination: "/en/get-started/agent-frameworks/mastra",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/server-level-vs-tool-level-auth",
+          destination: "/en/learn/server-level-vs-tool-level-auth",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/secure-your-mcp-server",
+          destination:
+            "/en/guides/create-tools/secure-your-server/secure-your-mcp-server",
+          permanent: true,
+        },
+        {
+          source: "/home/agent-frameworks-overview",
+          destination: "/en/get-started/agent-frameworks",
+          permanent: true,
+        },
+        {
+          source: "/home/agentic-development",
+          destination: "/en/get-started/setup/connect-arcade-docs",
+          permanent: true,
+        },
+        {
+          source: "/home/api-keys",
+          destination: "/en/get-started/setup/api-keys",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/vercelai/using-arcade-tools",
+          destination: "/en/get-started/agent-frameworks/vercelai",
+          permanent: true,
+        },
+        {
+          source: "/home/arcade-cli",
+          destination: "/en/references/arcade-cli",
+          permanent: true,
+        },
+        {
+          source: "/home/auth-providers",
+          destination: "/en/references/auth-providers",
+          permanent: true,
+        },
+        {
+          source: "/home/auth-providers/:path*",
+          destination: "/en/references/auth-providers/:path*",
+          permanent: true,
+        },
+        {
+          source: "/home/auth/auth-tool-calling",
+          destination: "/en/guides/tool-calling/custom-apps/auth-tool-calling",
+          permanent: true,
+        },
+        {
+          source: "/home/auth/call-third-party-apis-directly",
+          destination: "/en/guides/tool-calling/call-third-party-apis",
+          permanent: true,
+        },
+        {
+          source: "/home/auth/how-arcade-helps",
+          destination: "/en/get-started/about-arcade",
+          permanent: true,
+        },
+        {
+          source: "/home/auth/secure-auth-production",
+          destination: "/en/guides/user-facing-agents/secure-auth-production",
+          permanent: true,
+        },
+        {
+          source: "/home/auth/tool-auth-status",
+          destination: "/en/guides/tool-calling/custom-apps/check-auth-status",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/call-tools-from-mcp-clients",
+          destination: "/en/guides/create-tools/tool-basics/call-tools-mcp",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/create-a-mcp-server",
+          destination: "/en/guides/create-tools/tool-basics/build-mcp-server",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/create-a-tool-with-auth",
+          destination: "/en/guides/create-tools/tool-basics/create-tool-auth",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/create-a-tool-with-secrets",
+          destination:
+            "/en/guides/create-tools/tool-basics/create-tool-secrets",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/migrate-from-toolkits",
+          destination: "/en/guides/create-tools/migrate-toolkits",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/organize-mcp-server-tools",
+          destination: "/en/guides/create-tools/tool-basics/organize-mcp-tools",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/providing-useful-tool-errors",
+          destination:
+            "/en/guides/create-tools/error-handling/useful-tool-errors",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/retry-tools-with-improved-prompt",
+          destination: "/en/guides/create-tools/error-handling/retry-tools",
+          permanent: true,
+        },
+        {
+          source: "/home/build-tools/tool-context",
+          destination:
+            "/en/guides/create-tools/tool-basics/runtime-data-access",
+          permanent: true,
+        },
+        {
+          source: "/home/changelog",
+          destination: "/en/references/changelog",
+          permanent: true,
+        },
+        {
+          source: "/home/compare-server-types",
+          destination:
+            "/en/guides/create-tools/tool-basics/compare-server-types",
+          permanent: true,
+        },
+        {
+          source: "/home/contact-us",
+          destination: "/en/resources/contact-us",
+          permanent: true,
+        },
+        {
+          source: "/home/crewai/custom-auth-flow",
+          destination:
+            "/en/get-started/agent-frameworks/crewai/use-arcade-tools",
+          permanent: true,
+        },
+        {
+          source: "/home/crewai/use-arcade-tools",
+          destination:
+            "/en/get-started/agent-frameworks/crewai/use-arcade-tools",
+          permanent: true,
+        },
+        {
+          source: "/home/custom-mcp-server-quickstart",
+          destination: "/en/get-started/quickstarts/mcp-server-quickstart",
+          permanent: true,
+        },
+        {
+          source: "/home/deployment/arcade-cloud-infra",
+          destination: "/en/guides/deployment-hosting/arcade-cloud",
+          permanent: true,
+        },
+        {
+          source: "/home/deployment/engine-configuration",
+          destination: "/en/guides/deployment-hosting/configure-engine",
+          permanent: true,
+        },
+        {
+          source: "/home/evaluate-tools/create-an-evaluation-suite",
+          destination:
+            "/en/guides/create-tools/evaluate-tools/create-evaluation-suite",
+          permanent: true,
+        },
+        {
+          source: "/home/evaluate-tools/run-evaluations",
+          destination: "/en/guides/create-tools/evaluate-tools/run-evaluations",
+          permanent: true,
+        },
+        {
+          source: "/home/evaluate-tools/why-evaluate-tools",
+          destination: "/en/guides/create-tools/evaluate-tools/why-evaluate",
+          permanent: true,
+        },
+        {
+          source: "/home/examples",
+          destination: "/en/resources/examples",
+          permanent: true,
+        },
+        {
+          source: "/home/faq",
+          destination: "/en/resources/faq",
+          permanent: true,
+        },
+        {
+          source: "/home/glossary",
+          destination: "/en/resources/glossary",
+          permanent: true,
+        },
+        {
+          source: "/home/google-adk/use-arcade-tools",
+          destination:
+            "/en/get-started/agent-frameworks/google-adk/setup-python",
+          permanent: true,
+        },
+        {
+          source: "/home/hosting-overview",
+          destination: "/en/guides/deployment-hosting",
+          permanent: true,
+        },
+        {
+          source: "/home/langchain/auth-langchain-tools",
+          destination:
+            "/en/get-started/agent-frameworks/langchain/auth-langchain-tools",
+          permanent: true,
+        },
+        {
+          source: "/home/mastra/use-arcade-tools",
+          destination: "/en/get-started/agent-frameworks/mastra",
+          permanent: true,
+        },
+        {
+          source: "/home/mcp-clients/claude-desktop",
+          destination: "/en/get-started/mcp-clients/claude-desktop",
+          permanent: true,
+        },
+        {
+          source: "/home/mcp-clients/claude-code",
+          destination: "/en/get-started/mcp-clients/claude-code",
+          permanent: true,
+        },
+        {
+          source: "/home/mcp-clients/cursor",
+          destination: "/en/get-started/mcp-clients/cursor",
+          permanent: true,
+        },
+        {
+          source: "/home/mcp-clients/visual-studio-code",
+          destination: "/en/get-started/mcp-clients/visual-studio-code",
+          permanent: true,
+        },
+        {
+          source: "/home/mcp-gateway-quickstart",
+          destination: "/en/get-started/quickstarts/call-tool-client",
+          permanent: true,
+        },
+        {
+          source: "/home/mcp-gateways",
+          destination: "/en/guides/mcp-gateways",
+          permanent: true,
+        },
+        {
+          source: "/home/oai-agents/use-arcade-tools",
+          destination:
+            "/en/get-started/agent-frameworks/openai-agents/overview",
+          permanent: true,
+        },
+        {
+          source: "/home/quickstart",
+          destination: "/en/get-started/quickstarts/call-tool-agent",
+          permanent: true,
+        },
+        {
+          source: "/home/registry-early-access",
+          destination: "/en/resources/registry-early-access",
+          permanent: true,
+        },
+        {
+          source: "/home/serve-tools/arcade-deploy",
+          destination: "/en/guides/deployment-hosting/arcade-deploy",
+          permanent: true,
+        },
+        {
+          source: "/home/serve-tools/hybrid-worker",
+          destination: "/en/guides/deployment-hosting/on-prem",
+          permanent: true,
+        },
+        {
+          source: "/home/use-tools/get-tool-definitions",
+          destination:
+            "/en/guides/tool-calling/custom-apps/get-tool-definitions",
+          permanent: true,
+        },
+        {
+          source: "/home/use-tools/tools-overview",
+          destination: "/en/guides/tool-calling",
+          permanent: true,
+        },
+        {
+          source: "/home/use-tools/types-of-tools",
+          destination: "/en/guides/create-tools/improve/types-of-tools",
+          permanent: true,
+        },
+        {
+          source: "/home/use-tools/error-handling",
+          destination: "/en/guides/tool-calling/error-handling",
+          permanent: true,
+        },
+        {
+          source: "/home/vercelai/using-arcade-tools",
+          destination: "/en/get-started/agent-frameworks/vercelai",
+          permanent: true,
+        },
+        {
+          source: "/references/mcp",
+          destination: "/en/references/mcp/python",
+          permanent: true,
+        },
+        {
+          source: "/references/mcp/python/overview",
+          destination: "/en/references/mcp/python",
+          permanent: true,
+        },
+        {
+          source: "/references/arcade-cliarcade-configure",
+          destination: "/en/references/arcade-cli",
+          permanent: true,
+        },
+        {
+          source: "/get-started/setup/api-key",
+          destination: "/en/get-started/setup/api-keys",
+          permanent: true,
+        },
+        {
+          source: "/guides/tool-calling/custom-apps/authorized-tool-calling",
+          destination: "/en/guides/tool-calling/custom-apps/auth-tool-calling",
+          permanent: true,
+        },
+        {
+          source: "/guides/user-facing-agents/brand-provider",
+          destination: "/en/guides/user-facing-agents/secure-auth-production",
+          permanent: true,
+        },
+        {
+          source: "/guides/user-facing-agents/configure-oauth-provider",
+          destination: "/en/guides/user-facing-agents/secure-auth-production",
+          permanent: true,
+        },
+        {
+          source: "/guides/tool-calling/mcp-client/:client",
+          destination: "/en/get-started/mcp-clients/:client",
+          permanent: true,
+        },
+        {
+          source: "/guides/tool-calling/get-tool-definitions",
+          destination:
+            "/en/guides/tool-calling/custom-apps/get-tool-definitions",
+          permanent: true,
+        },
+        {
+          source: "/guides/deployment-hosting/engine-configuration",
+          destination: "/en/guides/deployment-hosting/configure-engine",
+          permanent: true,
+        },
+        {
+          source: "/guides/create-tools/performance/run-evaluations",
+          destination: "/en/guides/create-tools/evaluate-tools/run-evaluations",
+          permanent: true,
+        },
+        {
+          source: "/guides/create-tools/contribute/registry",
+          destination: "/en/resources/registry-early-access",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/crewai/python",
+          destination:
+            "/en/get-started/agent-frameworks/crewai/use-arcade-tools",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/langchain/python",
+          destination:
+            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/langchain/tools",
+          destination:
+            "/en/get-started/agent-frameworks/langchain/auth-langchain-tools",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/mastra/typescript",
+          destination: "/en/get-started/agent-frameworks/mastra",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/google-adk/python",
+          destination:
+            "/en/get-started/agent-frameworks/google-adk/setup-python",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/openai/python",
+          destination:
+            "/en/get-started/agent-frameworks/openai-agents/overview",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/vercel-ai/typescript",
+          destination: "/en/get-started/agent-frameworks/vercelai",
+          permanent: true,
+        },
+        {
+          source: "/resources/mastra/user-auth-interrupts",
+          destination: "/en/get-started/agent-frameworks/mastra",
+          permanent: true,
+        },
+        {
+          source: "/resources/oai-agents/overview",
+          destination:
+            "/en/get-started/agent-frameworks/openai-agents/overview",
+          permanent: true,
+        },
+        {
+          source: "/resources/creating-tools/:path*",
+          destination: "/en/guides/create-tools/:path*",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks",
+          destination: "/en/get-started/agent-frameworks",
+          permanent: true,
+        },
+        {
+          source: "/guides/agent-frameworks/:path*",
+          destination: "/en/get-started/agent-frameworks/:path*",
+          permanent: true,
+        },
+        {
+          source: "/guides/tool-calling/mcp-clients",
+          destination: "/en/get-started/mcp-clients",
+          permanent: true,
+        },
+        {
+          source: "/guides/tool-calling/mcp-clients/:path*",
+          destination: "/en/get-started/mcp-clients/:path*",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/sharepoint",
+          destination:
+            "/en/resources/integrations/productivity/microsoft-sharepoint",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/outlook-mail",
+          destination:
+            "/en/resources/integrations/productivity/microsoft-outlook-mail",
+          permanent: true,
+        },
+        {
+          source: "/resources/integrations/productivity/outlook-calendar",
+          destination:
+            "/en/resources/integrations/productivity/microsoft-outlook-calendar",
+          permanent: true,
+        },
+
+        // Broken /en/home/* paths from old doc structure — redirect to current locations
+        {
+          source: "/:locale/home/auth/authorized-tool-calling",
+          destination:
+            "/:locale/guides/tool-calling/custom-apps/auth-tool-calling",
+          permanent: true,
+        },
+        {
+          source: "/:locale/home/build-tools/create-a-toolkit",
+          destination: "/:locale/guides/create-tools/tool-basics",
+          permanent: true,
+        },
+        {
+          source: "/:locale/home/configure/arcade-deploy",
+          destination: "/:locale/guides/deployment-hosting/arcade-deploy",
+          permanent: true,
+        },
+        {
+          source: "/:locale/home/hybrid-deployment/hybrid-worker",
+          destination: "/:locale/guides/deployment-hosting",
+          permanent: true,
+        },
+        {
+          source: "/:locale/home/local-deployment/install/local",
+          destination: "/:locale/guides/deployment-hosting/on-prem",
+          permanent: true,
+        },
+        {
+          source: "/:locale/home/local-deployment/install/overview",
+          destination: "/:locale/guides/deployment-hosting",
+          permanent: true,
+        },
+        // squareup renamed to square
+        {
+          source: "/:locale/references/auth-providers/squareup",
+          destination: "/:locale/references/auth-providers/square",
+          permanent: true,
+        },
+        // Removed toolkit pages — redirect to integrations index
+        {
+          source: "/:locale/resources/integrations/entertainment/twitch",
+          destination: "/:locale/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/:locale/resources/integrations/social/discord",
+          destination: "/:locale/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/:locale/resources/integrations/social/twilio",
+          destination: "/:locale/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/:locale/resources/integrations/productivity/obsidian",
+          destination: "/:locale/resources/integrations",
+          permanent: true,
+        },
+        {
+          source: "/:locale/resources/integrations/productivity/closeio",
+          destination: "/:locale/resources/integrations",
+          permanent: true,
+        },
+        // Old daytona path structure — redirect to current category page
+        {
+          source: "/:locale/resources/integrations/daytona/overview",
+          destination: "/:locale/resources/integrations/development/daytona",
+          permanent: true,
+        },
+        // Old nested Google/Gmail toolkit path
+        {
+          source: "/:locale/resources/integrations/productivity/google/gmail",
+          destination: "/:locale/resources/integrations/productivity/gmail",
+          permanent: true,
+        },
         // Dissolved guides/security section
         {
           source: "/:locale/guides/security/security-research-program",

From e5dba0c46dc6a322aa4c2cb9f9ea815820398755 Mon Sep 17 00:00:00 2001
From: Teal Larson <teal@arcade.dev>
Date: Wed, 29 Apr 2026 11:45:29 -0400
Subject: [PATCH 2/2] fix: drop locale-less redirect siblings, rely on proxy.ts
 for locale prefix
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The proxy.ts (renamed from middleware.ts in #752a7b54) already adds the
/en/ prefix for locale-less requests. The 163 sibling rules were
duplicating that work to save one hop on external inbound links.

Trade-off accepted: 47 redirect chains stay 2-hop (proxy + restructure),
but the diff shrinks by ~900 lines and the multi-locale story stays
honest (proxy can grow Accept-Language detection later without a
hardcoded /en/ destination in 163 places).

Also fix collateral damage: D-2's MDX bulk rewrite mangled image paths
(![alt](/images/foo) → ![alt](/en/images/foo)) — revert image-syntax
matches back to /images/.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .../agent-frameworks/mastra/page.mdx          |   4 +-
 .../setup/connect-arcade-docs/page.mdx        |   2 +-
 app/en/guides/audit-logs/page.mdx             |   2 +-
 app/en/guides/contextual-access/page.mdx      |   2 +-
 .../resources/registry-early-access/page.mdx  |   2 +-
 next.config.ts                                | 868 ------------------
 6 files changed, 6 insertions(+), 874 deletions(-)

diff --git a/app/en/get-started/agent-frameworks/mastra/page.mdx b/app/en/get-started/agent-frameworks/mastra/page.mdx
index 2efdb25f8..4f98fb401 100644
--- a/app/en/get-started/agent-frameworks/mastra/page.mdx
+++ b/app/en/get-started/agent-frameworks/mastra/page.mdx
@@ -366,7 +366,7 @@ On first use, the agent will return an authorization URL. Visit the URL to conne
 
 </Steps>
 
-![Mastra Studio agent interaction](/en/images/screenshots/mastra-studio-agent-interaction.png)
+![Mastra Studio agent interaction](/images/screenshots/mastra-studio-agent-interaction.png)
 
 ## Build a workflow
 
@@ -613,7 +613,7 @@ export const mastra = new Mastra({
 
 </Steps>
 
-![Mastra Studio workflow run](/en/images/screenshots/mastra-studio-workflow-run.png)
+![Mastra Studio workflow run](/images/screenshots/mastra-studio-workflow-run.png)
 
 ## Key takeaways
 
diff --git a/app/en/get-started/setup/connect-arcade-docs/page.mdx b/app/en/get-started/setup/connect-arcade-docs/page.mdx
index 191fa09de..cc82c5059 100644
--- a/app/en/get-started/setup/connect-arcade-docs/page.mdx
+++ b/app/en/get-started/setup/connect-arcade-docs/page.mdx
@@ -22,6 +22,6 @@ LLMs.txt is a file format that allows you to give your AI IDE access to Arcade.d
 
 The LLMs.txt files are available at [`/llms.txt`](/en/llms.txt).
 
-![LLMs.txt example](/en/images/agentic-development/cursor-llms-txt.png)
+![LLMs.txt example](/images/agentic-development/cursor-llms-txt.png)
 
 Learn more about the LLMs.txt file format [here](https://llmstxt.org/).
diff --git a/app/en/guides/audit-logs/page.mdx b/app/en/guides/audit-logs/page.mdx
index edff0b276..681e56721 100644
--- a/app/en/guides/audit-logs/page.mdx
+++ b/app/en/guides/audit-logs/page.mdx
@@ -7,7 +7,7 @@ description: "Arcade.dev now captures every administrative action across the pla
 
 TL;DR: Arcade.dev captures every administrative action across the runtime automatically — who did it, how, what changed, and when. There's nothing to enable. Audit logs are on by default, with a filterable dashboard and a REST API for pulling data into your own systems.
 
-![Audit Log Dashboard](/en/images/screenshots/audit-log.png)
+![Audit Log Dashboard](/images/screenshots/audit-log.png)
 
 If you want audit events outside the dashboard, there's a REST API. You can pull logs programmatically to feed into your existing SIEM, compliance tooling, or internal reporting.
 
diff --git a/app/en/guides/contextual-access/page.mdx b/app/en/guides/contextual-access/page.mdx
index f515c4be7..2ccf1f202 100644
--- a/app/en/guides/contextual-access/page.mdx
+++ b/app/en/guides/contextual-access/page.mdx
@@ -22,7 +22,7 @@ You connect your own access-control, compliance, or transformation logic to the
 
 Contextual access is powered by **Logic Extensions**, a framework that allows you to hook in and add logic directly to Arcade's execution flow. Arcade calls your server at three predefined hook points in the tool lifecycle:
 
-![Contextual Access Flow Diagram](/en/images/logic-extensions/flow_diagram.png)
+![Contextual Access Flow Diagram](/images/logic-extensions/flow_diagram.png)
 
 | Hook point | When it runs | What it can do |
 | --- | --- | --- |
diff --git a/app/en/resources/registry-early-access/page.mdx b/app/en/resources/registry-early-access/page.mdx
index 54830dee8..0ae0a81df 100644
--- a/app/en/resources/registry-early-access/page.mdx
+++ b/app/en/resources/registry-early-access/page.mdx
@@ -14,7 +14,7 @@ The **Arcade Registry** is how agentic tool developers share their work with the
 <TakeSurvey />
 
 **_The components of the Arcade Registry_**
-![The Arcade Registry diagram](/en/images/registry/registry.png)
+![The Arcade Registry diagram](/images/registry/registry.png)
 
 Unlike traditional read-only tool libraries, Arcade.dev couples the runtime with the registry. This way we can collect real metrics and usage information about your tools, sharing meaningful information and feedback back to the developers. You'll get error reports and statistics about how your tools are getting used. Arcade.dev also makes it possible for developers to optionally choose to sell their tools with a markup on top of the Arcade platform fees.
 
diff --git a/next.config.ts b/next.config.ts
index 041f76d3c..9356b57c0 100644
--- a/next.config.ts
+++ b/next.config.ts
@@ -24,874 +24,6 @@ const nextConfig: NextConfig = withLlmsTxt({
   withNextra({
     async redirects() {
       return [
-        // Locale-less siblings for single-hop redirect (D-1)
-        {
-          source: "/home/auth/authorized-tool-calling",
-          destination: "/en/guides/tool-calling/custom-apps/auth-tool-calling",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/create-a-toolkit",
-          destination: "/en/guides/create-tools/tool-basics",
-          permanent: true,
-        },
-        {
-          source: "/home/configure/arcade-deploy",
-          destination: "/en/guides/deployment-hosting/arcade-deploy",
-          permanent: true,
-        },
-        {
-          source: "/home/hybrid-deployment/hybrid-worker",
-          destination: "/en/guides/deployment-hosting",
-          permanent: true,
-        },
-        {
-          source: "/home/local-deployment/install/local",
-          destination: "/en/guides/deployment-hosting/on-prem",
-          permanent: true,
-        },
-        {
-          source: "/home/local-deployment/install/overview",
-          destination: "/en/guides/deployment-hosting",
-          permanent: true,
-        },
-        {
-          source: "/references/auth-providers/squareup",
-          destination: "/en/references/auth-providers/square",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/entertainment/twitch",
-          destination: "/en/resources/integrations",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social/discord",
-          destination: "/en/resources/integrations",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social/twilio",
-          destination: "/en/resources/integrations",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/obsidian",
-          destination: "/en/resources/integrations",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/closeio",
-          destination: "/en/resources/integrations",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/daytona/overview",
-          destination: "/en/resources/integrations/development/daytona",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/google/gmail",
-          destination: "/en/resources/integrations/productivity/gmail",
-          permanent: true,
-        },
-        {
-          source: "/guides/security/security-research-program",
-          destination: "/en/resources/security-research-program",
-          permanent: true,
-        },
-        {
-          source: "/guides/security/securing-arcade-mcp",
-          destination: "/en/guides/create-tools/secure-your-server",
-          permanent: true,
-        },
-        {
-          source: "/guides/security/secure-your-mcp-server",
-          destination:
-            "/en/guides/create-tools/secure-your-server/secure-your-mcp-server",
-          permanent: true,
-        },
-        {
-          source: "/guides/security",
-          destination: "/en/guides/create-tools/secure-your-server",
-          permanent: true,
-        },
-        {
-          source: "/references/mcp/python/transports",
-          destination: "/en/references/mcp/python",
-          permanent: true,
-        },
-        {
-          source: "/references/mcp/python/types",
-          destination: "/en/references/mcp/python",
-          permanent: true,
-        },
-        {
-          source: "/get-started/agent-frameworks/crewai/custom-auth-flow",
-          destination:
-            "/en/get-started/agent-frameworks/crewai/use-arcade-tools",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/others/:path*",
-          destination: "/en/resources/integrations",
-          permanent: false,
-        },
-        {
-          source: "/get-started/agent-frameworks/google-adk/use-arcade-tools",
-          destination: "/en/get-started/agent-frameworks/google-adk/overview",
-          permanent: true,
-        },
-        {
-          source: "/references/logic-extensions-api",
-          destination: "/en/references/contextual-access-webhook-api",
-          permanent: true,
-        },
-        {
-          source: "/guides/logic-extensions",
-          destination: "/en/guides/contextual-access",
-          permanent: true,
-        },
-        {
-          source: "/guides/logic-extensions/build-your-own",
-          destination: "/en/guides/contextual-access/build-your-own",
-          permanent: true,
-        },
-        {
-          source: "/guides/logic-extensions/examples",
-          destination: "/en/guides/contextual-access/examples",
-          permanent: true,
-        },
-        {
-          source: "/guides/logic-extensions/how-hooks-work",
-          destination: "/en/guides/contextual-access/how-hooks-work",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/preview",
-          destination: "/en/resources/integrations",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/customer-support/zendesk/reference",
-          destination: "/en/resources/integrations/customer-support/zendesk",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/development/firecrawl/reference",
-          destination: "/en/resources/integrations/development/firecrawl",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/asana/reference",
-          destination: "/en/resources/integrations/productivity/asana",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/clickup/reference",
-          destination: "/en/resources/integrations/productivity/clickup",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/dropbox/reference",
-          destination: "/en/resources/integrations/productivity/dropbox",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/gmail/reference",
-          destination: "/en/resources/integrations/productivity/gmail",
-          permanent: true,
-        },
-        {
-          source:
-            "/resources/integrations/productivity/google-calendar/reference",
-          destination:
-            "/en/resources/integrations/productivity/google-calendar",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/google-docs/reference",
-          destination: "/en/resources/integrations/productivity/google-docs",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/google-drive/reference",
-          destination: "/en/resources/integrations/productivity/google-drive",
-          permanent: true,
-        },
-        {
-          source:
-            "/resources/integrations/productivity/google-sheets/reference",
-          destination: "/en/resources/integrations/productivity/google-sheets",
-          permanent: true,
-        },
-        {
-          source:
-            "/resources/integrations/productivity/jira/environment-variables",
-          destination: "/en/resources/integrations/productivity/jira",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/jira/reference",
-          destination: "/en/resources/integrations/productivity/jira",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/sales/hubspot/reference",
-          destination: "/en/resources/integrations/sales/hubspot",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social-communication/discord",
-          destination: "/en/resources/integrations",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social-communication/linkedin",
-          destination: "/en/resources/integrations/social/linkedin",
-          permanent: true,
-        },
-        {
-          source:
-            "/resources/integrations/social-communication/microsoft-teams",
-          destination: "/en/resources/integrations/social/microsoft-teams",
-          permanent: true,
-        },
-        {
-          source:
-            "/resources/integrations/social-communication/microsoft-teams/reference",
-          destination: "/en/resources/integrations/social/microsoft-teams",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social-communication/reddit",
-          destination: "/en/resources/integrations/social/reddit",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social-communication/slack-api",
-          destination: "/en/resources/integrations/social/slack-api",
-          permanent: true,
-        },
-        {
-          source:
-            "/resources/integrations/social-communication/slack/environment-variables",
-          destination: "/en/resources/integrations/social/slack",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social-communication/slack/install",
-          destination: "/en/resources/integrations/social/slack",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social-communication/slack",
-          destination: "/en/resources/integrations/social/slack",
-          permanent: true,
-        },
-        {
-          source:
-            "/resources/integrations/social-communication/slack/reference",
-          destination: "/en/resources/integrations/social/slack",
-          permanent: true,
-        },
-        {
-          source:
-            "/resources/integrations/social-communication/teams/reference",
-          destination: "/en/resources/integrations/social/microsoft-teams",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social-communication/twilio",
-          destination: "/en/resources/integrations",
-          permanent: true,
-        },
-        {
-          source:
-            "/resources/integrations/social-communication/twilio/reference",
-          destination: "/en/resources/integrations",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social-communication/x",
-          destination: "/en/resources/integrations/social/x",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social-communication/zoom/install",
-          destination: "/en/resources/integrations/social/zoom",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/social-communication/zoom",
-          destination: "/en/resources/integrations/social/zoom",
-          permanent: true,
-        },
-        {
-          source: "/guides/create-tools/contribute/registry-early-access",
-          destination: "/en/resources/registry-early-access",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/contribute-a-server",
-          destination: "/en/resources/registry-early-access",
-          permanent: true,
-        },
-        {
-          source: "/guides/create-tools/mcp-gateways",
-          destination: "/en/guides/mcp-gateways",
-          permanent: true,
-        },
-        {
-          source: "/get-started/agent-frameworks/langchain/use-arcade-tools",
-          destination:
-            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
-          permanent: true,
-        },
-        {
-          source:
-            "/get-started/agent-frameworks/langchain/user-auth-interrupts",
-          destination:
-            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
-          permanent: true,
-        },
-        {
-          source: "/get-started/agent-frameworks/mastra/overview",
-          destination: "/en/get-started/agent-frameworks/mastra",
-          permanent: true,
-        },
-        {
-          source: "/get-started/agent-frameworks/mastra/use-arcade-tools",
-          destination: "/en/get-started/agent-frameworks/mastra",
-          permanent: true,
-        },
-        {
-          source: "/get-started/agent-frameworks/mastra/user-auth-interrupts",
-          destination: "/en/get-started/agent-frameworks/mastra",
-          permanent: true,
-        },
-        {
-          source:
-            "/get-started/agent-frameworks/openai-agents/use-arcade-with-openai-agents",
-          destination:
-            "/en/get-started/agent-frameworks/openai-agents/overview",
-          permanent: true,
-        },
-        {
-          source:
-            "/get-started/agent-frameworks/openai-agents/use-arcade-tools",
-          destination:
-            "/en/get-started/agent-frameworks/openai-agents/overview",
-          permanent: true,
-        },
-        {
-          source:
-            "/get-started/agent-frameworks/openai-agents/user-auth-interrupts",
-          destination:
-            "/en/get-started/agent-frameworks/openai-agents/overview",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/setup-arcade-with-your-llm-python",
-          destination:
-            "/en/get-started/agent-frameworks/setup-arcade-with-your-llm-python",
-          permanent: true,
-        },
-        {
-          source: "/home/langchain/use-arcade-tools",
-          destination:
-            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/langchain/use-arcade-tools",
-          destination:
-            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
-          permanent: true,
-        },
-        {
-          source: "/home/langchain/user-auth-interrupts",
-          destination:
-            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/langchain/user-auth-interrupts",
-          destination:
-            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
-          permanent: true,
-        },
-        {
-          source:
-            "/get-started/agent-frameworks/langchain/use-arcade-with-langchain",
-          destination:
-            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
-          permanent: true,
-        },
-        {
-          source: "/home/oai-agents/user-auth-interrupts",
-          destination:
-            "/en/get-started/agent-frameworks/openai-agents/overview",
-          permanent: true,
-        },
-        {
-          source: "/home/mastra/user-auth-interrupts",
-          destination: "/en/get-started/agent-frameworks/mastra",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/server-level-vs-tool-level-auth",
-          destination: "/en/learn/server-level-vs-tool-level-auth",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/secure-your-mcp-server",
-          destination:
-            "/en/guides/create-tools/secure-your-server/secure-your-mcp-server",
-          permanent: true,
-        },
-        {
-          source: "/home/agent-frameworks-overview",
-          destination: "/en/get-started/agent-frameworks",
-          permanent: true,
-        },
-        {
-          source: "/home/agentic-development",
-          destination: "/en/get-started/setup/connect-arcade-docs",
-          permanent: true,
-        },
-        {
-          source: "/home/api-keys",
-          destination: "/en/get-started/setup/api-keys",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/vercelai/using-arcade-tools",
-          destination: "/en/get-started/agent-frameworks/vercelai",
-          permanent: true,
-        },
-        {
-          source: "/home/arcade-cli",
-          destination: "/en/references/arcade-cli",
-          permanent: true,
-        },
-        {
-          source: "/home/auth-providers",
-          destination: "/en/references/auth-providers",
-          permanent: true,
-        },
-        {
-          source: "/home/auth-providers/:path*",
-          destination: "/en/references/auth-providers/:path*",
-          permanent: true,
-        },
-        {
-          source: "/home/auth/auth-tool-calling",
-          destination: "/en/guides/tool-calling/custom-apps/auth-tool-calling",
-          permanent: true,
-        },
-        {
-          source: "/home/auth/call-third-party-apis-directly",
-          destination: "/en/guides/tool-calling/call-third-party-apis",
-          permanent: true,
-        },
-        {
-          source: "/home/auth/how-arcade-helps",
-          destination: "/en/get-started/about-arcade",
-          permanent: true,
-        },
-        {
-          source: "/home/auth/secure-auth-production",
-          destination: "/en/guides/user-facing-agents/secure-auth-production",
-          permanent: true,
-        },
-        {
-          source: "/home/auth/tool-auth-status",
-          destination: "/en/guides/tool-calling/custom-apps/check-auth-status",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/call-tools-from-mcp-clients",
-          destination: "/en/guides/create-tools/tool-basics/call-tools-mcp",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/create-a-mcp-server",
-          destination: "/en/guides/create-tools/tool-basics/build-mcp-server",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/create-a-tool-with-auth",
-          destination: "/en/guides/create-tools/tool-basics/create-tool-auth",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/create-a-tool-with-secrets",
-          destination:
-            "/en/guides/create-tools/tool-basics/create-tool-secrets",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/migrate-from-toolkits",
-          destination: "/en/guides/create-tools/migrate-toolkits",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/organize-mcp-server-tools",
-          destination: "/en/guides/create-tools/tool-basics/organize-mcp-tools",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/providing-useful-tool-errors",
-          destination:
-            "/en/guides/create-tools/error-handling/useful-tool-errors",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/retry-tools-with-improved-prompt",
-          destination: "/en/guides/create-tools/error-handling/retry-tools",
-          permanent: true,
-        },
-        {
-          source: "/home/build-tools/tool-context",
-          destination:
-            "/en/guides/create-tools/tool-basics/runtime-data-access",
-          permanent: true,
-        },
-        {
-          source: "/home/changelog",
-          destination: "/en/references/changelog",
-          permanent: true,
-        },
-        {
-          source: "/home/compare-server-types",
-          destination:
-            "/en/guides/create-tools/tool-basics/compare-server-types",
-          permanent: true,
-        },
-        {
-          source: "/home/contact-us",
-          destination: "/en/resources/contact-us",
-          permanent: true,
-        },
-        {
-          source: "/home/crewai/custom-auth-flow",
-          destination:
-            "/en/get-started/agent-frameworks/crewai/use-arcade-tools",
-          permanent: true,
-        },
-        {
-          source: "/home/crewai/use-arcade-tools",
-          destination:
-            "/en/get-started/agent-frameworks/crewai/use-arcade-tools",
-          permanent: true,
-        },
-        {
-          source: "/home/custom-mcp-server-quickstart",
-          destination: "/en/get-started/quickstarts/mcp-server-quickstart",
-          permanent: true,
-        },
-        {
-          source: "/home/deployment/arcade-cloud-infra",
-          destination: "/en/guides/deployment-hosting/arcade-cloud",
-          permanent: true,
-        },
-        {
-          source: "/home/deployment/engine-configuration",
-          destination: "/en/guides/deployment-hosting/configure-engine",
-          permanent: true,
-        },
-        {
-          source: "/home/evaluate-tools/create-an-evaluation-suite",
-          destination:
-            "/en/guides/create-tools/evaluate-tools/create-evaluation-suite",
-          permanent: true,
-        },
-        {
-          source: "/home/evaluate-tools/run-evaluations",
-          destination: "/en/guides/create-tools/evaluate-tools/run-evaluations",
-          permanent: true,
-        },
-        {
-          source: "/home/evaluate-tools/why-evaluate-tools",
-          destination: "/en/guides/create-tools/evaluate-tools/why-evaluate",
-          permanent: true,
-        },
-        {
-          source: "/home/examples",
-          destination: "/en/resources/examples",
-          permanent: true,
-        },
-        {
-          source: "/home/faq",
-          destination: "/en/resources/faq",
-          permanent: true,
-        },
-        {
-          source: "/home/glossary",
-          destination: "/en/resources/glossary",
-          permanent: true,
-        },
-        {
-          source: "/home/google-adk/use-arcade-tools",
-          destination:
-            "/en/get-started/agent-frameworks/google-adk/setup-python",
-          permanent: true,
-        },
-        {
-          source: "/home/hosting-overview",
-          destination: "/en/guides/deployment-hosting",
-          permanent: true,
-        },
-        {
-          source: "/home/langchain/auth-langchain-tools",
-          destination:
-            "/en/get-started/agent-frameworks/langchain/auth-langchain-tools",
-          permanent: true,
-        },
-        {
-          source: "/home/mastra/use-arcade-tools",
-          destination: "/en/get-started/agent-frameworks/mastra",
-          permanent: true,
-        },
-        {
-          source: "/home/mcp-clients/claude-desktop",
-          destination: "/en/get-started/mcp-clients/claude-desktop",
-          permanent: true,
-        },
-        {
-          source: "/home/mcp-clients/claude-code",
-          destination: "/en/get-started/mcp-clients/claude-code",
-          permanent: true,
-        },
-        {
-          source: "/home/mcp-clients/cursor",
-          destination: "/en/get-started/mcp-clients/cursor",
-          permanent: true,
-        },
-        {
-          source: "/home/mcp-clients/visual-studio-code",
-          destination: "/en/get-started/mcp-clients/visual-studio-code",
-          permanent: true,
-        },
-        {
-          source: "/home/mcp-gateway-quickstart",
-          destination: "/en/get-started/quickstarts/call-tool-client",
-          permanent: true,
-        },
-        {
-          source: "/home/mcp-gateways",
-          destination: "/en/guides/mcp-gateways",
-          permanent: true,
-        },
-        {
-          source: "/home/oai-agents/use-arcade-tools",
-          destination:
-            "/en/get-started/agent-frameworks/openai-agents/overview",
-          permanent: true,
-        },
-        {
-          source: "/home/quickstart",
-          destination: "/en/get-started/quickstarts/call-tool-agent",
-          permanent: true,
-        },
-        {
-          source: "/home/registry-early-access",
-          destination: "/en/resources/registry-early-access",
-          permanent: true,
-        },
-        {
-          source: "/home/serve-tools/arcade-deploy",
-          destination: "/en/guides/deployment-hosting/arcade-deploy",
-          permanent: true,
-        },
-        {
-          source: "/home/serve-tools/hybrid-worker",
-          destination: "/en/guides/deployment-hosting/on-prem",
-          permanent: true,
-        },
-        {
-          source: "/home/use-tools/get-tool-definitions",
-          destination:
-            "/en/guides/tool-calling/custom-apps/get-tool-definitions",
-          permanent: true,
-        },
-        {
-          source: "/home/use-tools/tools-overview",
-          destination: "/en/guides/tool-calling",
-          permanent: true,
-        },
-        {
-          source: "/home/use-tools/types-of-tools",
-          destination: "/en/guides/create-tools/improve/types-of-tools",
-          permanent: true,
-        },
-        {
-          source: "/home/use-tools/error-handling",
-          destination: "/en/guides/tool-calling/error-handling",
-          permanent: true,
-        },
-        {
-          source: "/home/vercelai/using-arcade-tools",
-          destination: "/en/get-started/agent-frameworks/vercelai",
-          permanent: true,
-        },
-        {
-          source: "/references/mcp",
-          destination: "/en/references/mcp/python",
-          permanent: true,
-        },
-        {
-          source: "/references/mcp/python/overview",
-          destination: "/en/references/mcp/python",
-          permanent: true,
-        },
-        {
-          source: "/references/arcade-cliarcade-configure",
-          destination: "/en/references/arcade-cli",
-          permanent: true,
-        },
-        {
-          source: "/get-started/setup/api-key",
-          destination: "/en/get-started/setup/api-keys",
-          permanent: true,
-        },
-        {
-          source: "/guides/tool-calling/custom-apps/authorized-tool-calling",
-          destination: "/en/guides/tool-calling/custom-apps/auth-tool-calling",
-          permanent: true,
-        },
-        {
-          source: "/guides/user-facing-agents/brand-provider",
-          destination: "/en/guides/user-facing-agents/secure-auth-production",
-          permanent: true,
-        },
-        {
-          source: "/guides/user-facing-agents/configure-oauth-provider",
-          destination: "/en/guides/user-facing-agents/secure-auth-production",
-          permanent: true,
-        },
-        {
-          source: "/guides/tool-calling/mcp-client/:client",
-          destination: "/en/get-started/mcp-clients/:client",
-          permanent: true,
-        },
-        {
-          source: "/guides/tool-calling/get-tool-definitions",
-          destination:
-            "/en/guides/tool-calling/custom-apps/get-tool-definitions",
-          permanent: true,
-        },
-        {
-          source: "/guides/deployment-hosting/engine-configuration",
-          destination: "/en/guides/deployment-hosting/configure-engine",
-          permanent: true,
-        },
-        {
-          source: "/guides/create-tools/performance/run-evaluations",
-          destination: "/en/guides/create-tools/evaluate-tools/run-evaluations",
-          permanent: true,
-        },
-        {
-          source: "/guides/create-tools/contribute/registry",
-          destination: "/en/resources/registry-early-access",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/crewai/python",
-          destination:
-            "/en/get-started/agent-frameworks/crewai/use-arcade-tools",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/langchain/python",
-          destination:
-            "/en/get-started/agent-frameworks/langchain/use-arcade-with-langchain-py",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/langchain/tools",
-          destination:
-            "/en/get-started/agent-frameworks/langchain/auth-langchain-tools",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/mastra/typescript",
-          destination: "/en/get-started/agent-frameworks/mastra",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/google-adk/python",
-          destination:
-            "/en/get-started/agent-frameworks/google-adk/setup-python",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/openai/python",
-          destination:
-            "/en/get-started/agent-frameworks/openai-agents/overview",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/vercel-ai/typescript",
-          destination: "/en/get-started/agent-frameworks/vercelai",
-          permanent: true,
-        },
-        {
-          source: "/resources/mastra/user-auth-interrupts",
-          destination: "/en/get-started/agent-frameworks/mastra",
-          permanent: true,
-        },
-        {
-          source: "/resources/oai-agents/overview",
-          destination:
-            "/en/get-started/agent-frameworks/openai-agents/overview",
-          permanent: true,
-        },
-        {
-          source: "/resources/creating-tools/:path*",
-          destination: "/en/guides/create-tools/:path*",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks",
-          destination: "/en/get-started/agent-frameworks",
-          permanent: true,
-        },
-        {
-          source: "/guides/agent-frameworks/:path*",
-          destination: "/en/get-started/agent-frameworks/:path*",
-          permanent: true,
-        },
-        {
-          source: "/guides/tool-calling/mcp-clients",
-          destination: "/en/get-started/mcp-clients",
-          permanent: true,
-        },
-        {
-          source: "/guides/tool-calling/mcp-clients/:path*",
-          destination: "/en/get-started/mcp-clients/:path*",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/sharepoint",
-          destination:
-            "/en/resources/integrations/productivity/microsoft-sharepoint",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/outlook-mail",
-          destination:
-            "/en/resources/integrations/productivity/microsoft-outlook-mail",
-          permanent: true,
-        },
-        {
-          source: "/resources/integrations/productivity/outlook-calendar",
-          destination:
-            "/en/resources/integrations/productivity/microsoft-outlook-calendar",
-          permanent: true,
-        },
-
         // Broken /en/home/* paths from old doc structure — redirect to current locations
         {
           source: "/:locale/home/auth/authorized-tool-calling",