<!--
  Full-page Markdown export (rendered HTML → GFM).
  Source: https://neotoma.io/neotoma-with-openclaw-connect-remote-http
  Generated: 2026-05-04T09:51:01.011Z
-->
# 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.  **Start Neotoma with a tunnel:** follow the [tunnel guide](/tunnel) to expose your local Neotoma instance over HTTPS. The quickest path:
    
    Code snippet
    
    Copy the exact snippet shown below.
    
    ```
    neotoma api start --env prod --tunnel
    ```
    
2.  **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)