<!--
  Full-page Markdown export (rendered HTML → GFM).
  Source: https://neotoma.io/es/neotoma-with-openclaw-connect-remote-http
  Generated: 2026-04-28T13:35:45.184Z
-->
# OpenClaw remote setup (HTTP)

[Neotoma with OpenClaw](/neotoma-with-openclaw) · Remote setup for cloud or multi-machine deployments.

OpenClaw and Neotoma on the same machine? See [OpenClaw local setup (stdio)](/neotoma-with-openclaw-connect-local-stdio).

* * *

## Setup

If OpenClaw runs on a different machine or in the cloud, start with local install on your host machine, then configure remote access:

1.  **Install a tunnel provider:** Neotoma's `--tunnel` flag needs either [ngrok](https://ngrok.com/download) or [Cloudflare Tunnel (cloudflared)](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/downloads/) installed on your machine. Install one:
    
    Code snippet
    
    Copy the exact snippet shown below.
    
    ```
    # ngrok (via Homebrew)
    brew install ngrok
    ngrok config add-authtoken <YOUR_NGROK_TOKEN>
    
    # or Cloudflare Tunnel
    brew install cloudflared
    ```
    
    ngrok requires a free account and auth token from [dashboard.ngrok.com](https://dashboard.ngrok.com/get-started/your-authtoken). You can set the token as an environment variable instead of running `ngrok config`:
    
    Code snippet
    
    Copy the exact snippet shown below.
    
    ```
    # In your shell profile or .env
    export NGROK_AUTHTOKEN=<YOUR_NGROK_TOKEN>
    ```
    
    Cloudflare Tunnel works without an account for quick tunnels. If both providers are installed, Neotoma auto-detects which to use; pass `--tunnel-provider ngrok` or `--tunnel-provider cloudflare` to choose explicitly.
    
2.  **Start the API server with a tunnel:** the `--tunnel` flag auto-provisions a public HTTPS URL via ngrok or Cloudflare (whichever is installed)
    
    Code snippet
    
    Copy the exact snippet shown below.
    
    ```
    neotoma api start --env prod --tunnel
    ```
    
    The tunnel URL is printed to the console and written to `/tmp/ngrok-mcp-url.txt`. You can also use a reverse proxy or your own domain instead of `--tunnel`.
    
3.  **Point OpenClaw at the remote endpoint:** use the tunnel URL for the Neotoma API's OpenAPI spec (`https://<tunnel-host>/openapi.yaml`) or the remote MCP endpoint (`https://<tunnel-host>/mcp`). The Neotoma API supports the [MCP OAuth authorization flow](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization) for authenticated access.

If MCP is not yet available in your OpenClaw environment, use the Neotoma CLI directly from the same machine as a fallback:

Code snippet

Copy the exact snippet shown below.

```
neotoma store --json='[{"entity_type":"task","title":"Follow up","status":"open"}]'
neotoma entities list --type task
```

[Back to Neotoma with OpenClaw](/neotoma-with-openclaw) · [Install guide](/install) · [MCP reference](/mcp)