compare server types (#529)

* compare server types

* Update app/en/home/compare-server-types/page.mdx

Co-authored-by: Eric Gustin <[email protected]>

* added server types to glossary

---------

Co-authored-by: Eric Gustin <[email protected]>

Author: torresmateo

app/en/home/_meta.tsx

@@ -125,6 +125,9 @@ export const meta: MetaRecord = {
   faq: {
     title: "FAQ",
   },
+  "compare-server-types": {
+    title: "Compare Server Types",
+  },
   "agentic-development": {
     title: "Agentic Development",
   },

app/en/home/compare-server-types/page.mdx

@@ -0,0 +1,17 @@
+---
+title: "Compare Server Types"
+description: "Compare the different types of MCP servers"
+---
+
+# Compare MCP Server Types
+
+Depending on the transport you use and where you want to run your MCP server, Arcade offers different functionalities and features. Below is a comparison of the different server types and their capabilities.
+
+| Transport | Deployment                                                              | Tools without requirements | Tools with secrets | Tools with auth (single-user) | Tools with auth (multi-user) |
+| --------- | ----------------------------------------------------------------------- | :------------------------: | :----------------: | :---------------------------: | :--------------------------: |
+| stdio     | local                                                                   |             ✅             |         ✅         |              ✅               |              ❌              |
+| http      | local ([unprotected](/home/glossary#unprotected-mcp-servers))           |             ✅             |         ❌         |              ❌               |              ❌              |
+| http      | remote ([unprotected](/home/glossary#unprotected-mcp-servers))          |             ✅             |         ❌         |              ❌               |              ❌              |
+| http      | local ([protected](/home/glossary#protected-mcp-servers)) `coming soon` |             ✅             |         ✅         |              ✅               |              ✅              |
+| http      | remote ([protected](/home/glossary#protected-mcp-servers))              |             ✅             |         ✅         |              ✅               |              ✅              |
+| http      | Arcade Cloud                                                            |             ✅             |         ✅         |              ✅               |              ✅              |

app/en/home/glossary/page.mdx

@@ -27,6 +27,14 @@ _Learn more about [context](/home/build-tools/tool-context)._
 
 A 'MCP Server' is a collection of tools that can be used by an agent, grouped logically together by a common theme or provider, and the running remote process that serves and executes the tools. MCP Servers are the unit of deployment for tools within Arcade.
 
+#### Protected MCP Servers
+
+A protected server implements [MCP authorization](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization) and requires the MCP client to provide a token identifying the user when calling the MCP server. Examples: servers that require sign-in, deal with private info, call APIs on your behalf
+
+#### Unprotected MCP Servers
+
+An unprotected (anonymous) MCP server can be used by any MCP client on the network. Because it is anonymous, it can't identify the user who is using the server. Examples: servers that return static info, weather APIs, etc
+
 ### Tool
 
 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.
@@ -168,7 +176,7 @@ The Arcade Engine is also responsible for the OAuth flow for your agent's users.
 
 ### MCP Gateway
 
-MCP gateways are a feature of the Arcade Engine that allows you to add and combine multiple MCP servers in your project. The MCP gateway is responsible for routing tool execution requests to the correct MCP server, and for enforcing security and authorization decisions.  You can mix and match tools from different MCP servers in the same project, and not all tools from a MCP server need to be available to the same LLM.
+MCP gateways are a feature of the Arcade Engine that allows you to add and combine multiple MCP servers in your project. The MCP gateway is responsible for routing tool execution requests to the correct MCP server, and for enforcing security and authorization decisions. You can mix and match tools from different MCP servers in the same project, and not all tools from a MCP server need to be available to the same LLM.
 
 ### Arcade MCP (Server Development Kit)