On prem MCP servers (formerly Hybrid MCP servers) (#491)

on prem MCP servers

Author: torresmateo

app/en/home/deployment/_meta.tsx

@@ -9,7 +9,7 @@ const meta: MetaRecord = {
     },
   },
   "on-prem-mcp": {
-    title: "On-premise MCP servers",
+    title: "On-premises MCP servers",
   },
   "engine-configuration": {
     title: "Engine configuration",

app/en/home/deployment/on-prem-mcp/page.mdx

@@ -1,5 +1,5 @@
 ---
-title: "On-premise MCP Servers"
+title: "On-premises MCP Servers"
 description: "Learn how to deploy MCP servers in a hybrid architecture"
 ---
 
@@ -25,93 +25,134 @@ The on-premises MCP server model uses a bidirectional connection between your lo
 - **Custom environments**: Use specific dependencies or configurations required by your tools
 - **Compliance**: Meet regulatory requirements by keeping data processing within your infrastructure
 
-## Setting up a hybrid worker
+## Setting up an on-premises MCP server
 
 <Steps>
 
 ### Setup your MCP Servers
 
 Follow the [Creating a MCP Server](/home/build-tools/create-a-mcp-server) guide to create your MCP Server.
 
-### Start your local worker
+### Start your local MCP Server
 
-Run your Arcade worker locally with a secret that you generate in a secure way:
+Ensure you are logged in to Arcade:
 
-```sh
-export ARCADE_WORKER_SECRET=your-secret
-arcade serve
+<Tabs items={["CLI", "Environment Variable"]}>
+<Tabs.Tab>
+
+```bash
+arcade login
+```
+
+</Tabs.Tab>
+<Tabs.Tab>
+
+Add the environment variables to your shell:
+
+```bash
+export ARCADE_API_KEY=<your-api-key>
+export ARCADE_USER_ID=<your-user-id>
+```
+
+or to a `.env` file:
+
+```env filename=".env"
+ARCADE_API_KEY=<your-api-key>
+ARCADE_USER_ID=<your-user-id>
+```
+
+</Tabs.Tab>
+</Tabs>
+
+Run your Arcade MCP Server locally with a secret that you generate in a secure way:
+
+```bash
+cd <your-mcp-server-directory>
+arcade mcp
 ```
 
-Verify your worker is running by visiting http://localhost:8002/worker/health.
+Your MCP server is running on http://127.0.0.1:8000
 
 ### Create a public URL
 
-To allow the Arcade cloud engine to connect to your locally running worker, you need a public URL. Here are a few options:
+To allow the Arcade cloud engine to connect to your locally running MCP Server, you need a public URL. Here are a few options:
 
 <Tabs items={["ngrok", "Cloudflare", "Tailscale"]}>
 <Tabs.Tab>
 
-```sh
-ngrok http 8002
+```bash
+ngrok http 8000
 ```
 
 </Tabs.Tab>
 
 <Tabs.Tab>
 
-```sh
-cloudflared tunnel --url http://localhost:8002
+```bash
+cloudflared tunnel --url http://localhost:8000
 ```
 
 </Tabs.Tab>
 
 <Tabs.Tab>
 
-```sh
-tailscale funnel 8002
+```bash
+tailscale funnel 8000
 ```
 
 </Tabs.Tab>
 </Tabs>
 
-### Register your worker in Arcade
+### Register your MCP Server in Arcade
 
 1. Navigate to the [Servers](https://api.arcade.dev/dashboard/servers) page in your Arcade dashboard
 1. Click **Add Server**
 1. Fill in the form:
    - **ID**: Choose a unique identifier (e.g., `my-server`)
-   - **Worker Type**: Select `Arcade`
-   - **URL**: Enter your public URL from Step 3
-   - **Secret**: Enter the secret for your worker (or use `dev` for testing)
+   - **Server Type**: Select `MCP`
+   - **URL**: Enter your public URL from Step 3, and add `/mcp` to the end
    - **Timeout** and **Retry**: Configure as needed for your use case
 1. Click **Create**
 
-### Test the connection to your worker
+### Test the connection to your MCP Server
 
-You can now test your worker by making requests through the Arcade API or using the Playground:
+You can now test your MCP Server by making requests using the Playground, or an MCP client:
+
+<Tabs items={["Playground", "MCP Client"]}>
+<Tabs.Tab>
 
 1. Go to the [Playground](https://api.arcade.dev/dashboard/playground)
 1. Select a tool from your MCP Server and execute it
-1. Verify that the response is correct and you see request logs in your worker
+1. Verify that the response is correct and you see request logs in your MCP Server
+
+</Tabs.Tab>
+<Tabs.Tab>
+
+1. Use an app that supports MCP clients, like AI assistants and IDEs:
+   - [Visual Studio Code](/home/mcp-clients/visual-studio-code)
+   - [Claude Desktop](/home/mcp-clients/claude-desktop)
+   - [Cursor](/home/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
+
+</Tabs.Tab>
+</Tabs>
 
 </Steps>
 
 ## Best practices
 
 - **Persistent URLs**: For production use, set up a persistent public URL rather than ephemeral ones
 - **TLS**: Use a TLS-enabled URL for production use
-- **Security**: Use strong secrets for worker authentication
-- **Monitoring**: Set up monitoring for your hybrid workers to ensure availability
-- **Scaling**: For high-load scenarios, consider running multiple workers behind a load balancer
+- **Monitoring**: Set up monitoring for your MCP Server to ensure availability
 
 ## Troubleshooting
 
-- **Connection issues**: Ensure your public URL is accessible and that your local worker is running
-- **Authentication failures**: Verify that the worker secret matches what's configured in the Arcade dashboard
-- **Timeout errors**: If your worker takes too long to respond, increase the timeout value in the worker configuration
+- **Connection issues**: Ensure your public URL is accessible and that your local MCP Server is running
+- **Timeout errors**: If your MCP Server takes too long to respond, increase the timeout value in the MCP Server configuration
 
 ## Next steps
 
-- [Create custom tools](/home/build-tools/create-a-mcp-server) for your hybrid worker
+- [Create custom tools](/home/build-tools/create-a-mcp-server) for your MCP Server
 - [Set up authentication](/home/build-tools/create-a-tool-with-auth) for secure access to resources
-- [Configure secrets](/home/build-tools/create-a-tool-with-secrets) for your worker
+- [Configure secrets](/home/build-tools/create-a-tool-with-secrets) for your MCP Server

app/en/home/mcp-clients/_meta.tsx

@@ -1,4 +1,5 @@
 export default {
   "claude-desktop": "Claude Desktop",
   "visual-studio-code": "Visual Studio Code",
+  cursor: "Cursor",
 };

app/en/home/mcp-clients/cursor/page.mdx

@@ -0,0 +1 @@
+Coming soon...