Skip to content

Fensory connection guide

Connect OpenClaw to Fensory

OpenClaw connects to Fensory as a Streamable HTTP MCP server with OAuth. Add the server in Settings or save it from the CLI, authorize the Fensory account and run a live probe before exposing the tools to an agent.

Connecting the server does not bypass OpenClaw tool policies. The OpenClaw policy and the Fensory account limits both apply. Fensory is not available to US persons.

What you need

A current OpenClaw installation with administrator access and an eligible Fensory account.

Connect OpenClaw

Use the remote Fensory server and complete OAuth with the account you want the assistant to reach.

openclaw mcp add fensory --url https://mcp.fensory.com/mcp --transport streamable-http openclaw mcp login fensory openclaw mcp doctor fensory --probe
  1. 01

    Add the server

    In Control UI, open Settings, then MCP, then Add server. Name it fensory, choose Streamable HTTP and paste https://mcp.fensory.com/mcp. The openclaw mcp add command above saves the same definition directly.

  2. 02

    Set OAuth and sign in

    Configure the server with OAuth and choose Sign in, or run openclaw mcp login fensory. Approve the Fensory account in the browser and return to OpenClaw.

  3. 03

    Probe the live server

    Run openclaw mcp doctor fensory --probe or openclaw mcp probe fensory. Saved credentials alone do not prove the endpoint and tools are reachable.

  4. 04

    Review tool access for the session

    In the composer, open Connectors, then Tool access. Enable only the Fensory tools the session needs and start with a read-only prompt.

Connect an agent

Server URL

https://mcp.fensory.com/mcp

One endpoint for every client. Sign in to Fensory once for this connection.

Claude
ChatGPT
Cursor
Codex
Hermes
OpenClaw
  1. 1

    Run this in your terminal.

    openclaw mcp add fensory --url https://mcp.fensory.com/mcp --transport streamable-http
  2. 2

    Run openclaw mcp login fensory, then verify with openclaw mcp doctor fensory --probe.

  3. 3

    Try a read-only question.

    “What can you do on Fensory?”

The Fensory app setup pattern, using the command documented by OpenClaw.

Example prompts for OpenClaw

Use these examples to check the connection, account and instrument before any order is submitted. Adapt the amount and market to your own account controls.

  • List the enabled Fensory tools for this session and identify which ones can change the account.

    Tool policy
  • Show recent account activity, pending orders and open positions. Do not change anything.

    Activity check
  • Inspect one supported spot market and one supported perpetual future, then draft an order request without submitting it.

    Market preview
  • Set account limits before the first order

    Fensory enforces three controls on the account: a kill-switch, a market allow-list and a per-order cap.

    See the controls

What to know about OpenClaw

  • Saved authorization is not a health check

    OpenClaw states that saved credentials do not prove the server is reachable. Run doctor with probe or use the connector before calling setup complete.

  • Tool policy remains in force

    An MCP connection adds tools to OpenClaw. It does not override the profile, session or tool policy that controls whether an agent may call them.

  • OAuth belongs to the selected runtime owner

    OpenClaw stores the OAuth session for the gateway or runtime where sign-in began. Make sure you authorize the same runtime that will execute the agent session.

Questions people ask

Which OpenClaw transport should I choose?
Choose Streamable HTTP and use the Fensory HTTPS endpoint. Fensory is a remote server, so no local command is required.
How do I know the connection actually works?
Run openclaw mcp doctor fensory --probe or openclaw mcp probe fensory. A saved OAuth token without a successful probe is incomplete evidence.
Can OpenClaw restrict the Fensory tools?
Yes. OpenClaw supports server and session tool filters. Those filters sit in front of the account controls enforced by Fensory.
Where is the OAuth token stored?
OpenClaw stores native MCP OAuth sessions in its owner-only state database for the runtime that owns the connection.
Can the OpenClaw connection withdraw funds?
No. On the current MCP path, the Hyperliquid agent key can sign trades and cannot withdraw, transfer or bridge funds.