Skip to content

Fensory connection guide

Connect Claude to Fensory

Claude connects to Fensory as a custom remote MCP connector. Add the Fensory endpoint under Customize and Connectors, complete OAuth in the browser and enable the connector for the conversation where you want to use it.

Custom remote connectors are available on Claude Free, Pro, Max, Team and Enterprise. Free accounts may add one custom connector. Team and Enterprise owners control whether an organization connector may be added. Fensory is not available to US persons.

What you need

Claude Free, Pro, Max, Team or Enterprise, plus an eligible Fensory account. Free supports one custom connector.

Connect Claude

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

https://mcp.fensory.com/mcp
  1. 01

    Open Claude connector settings

    On Free, Pro or Max, open Customize, then Connectors. On Team or Enterprise, an Owner or Primary Owner first adds the connector under Organization settings, then members connect to it under Customize.

  2. 02

    Add the Fensory endpoint

    Choose Add custom connector, paste https://mcp.fensory.com/mcp, name it Fensory and select Add.

  3. 03

    Authorize your Fensory account

    Claude opens the Fensory OAuth flow in the browser. Sign in to the Fensory account you want the connector to use and approve the connection.

  4. 04

    Enable Fensory in the conversation

    In the chat, select the plus button, open Connectors and turn on Fensory. Start with a read-only account or market question before enabling agentic trading in Fensory.

Example prompts for Claude

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.

  • Show my Fensory account status, enabled markets and current trading limits. Do not place or cancel any order.

    Account check
  • Explain what xyz:TSLA is, including margin, leverage, funding and liquidation risk. Do not place an order.

    Instrument check
  • Draft a $10 limit order for a supported perpetual future and show every parameter. Do not submit it.

    Order 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 Claude

  • The connector is enabled per conversation

    Adding Fensory makes it available to Claude. In each conversation where Claude should call it, select the plus button, open Connectors and turn on Fensory.

  • Organization access is an admin decision

    On Team and Enterprise, an Owner or Primary Owner adds or enables organization connectors. Individual users then connect their own Fensory account.

  • The account controls still decide what can trade

    Claude can call only the tools and markets available to the connected Fensory account. The kill-switch and per-order cap are enforced on the account rather than in the prompt.

Questions people ask

Do I need Claude Desktop?
No. Anthropic documents custom remote connectors for Claude and Claude Desktop. Both use the connector settings and browser OAuth flow.
Does Claude receive my private key?
No. The connector uses OAuth. On the current MCP path, Hyperliquid trades use a scoped signing key that cannot withdraw, transfer or bridge funds.
Can Claude place a real trade?
Yes, once agentic trading is enabled on the Fensory account. Start with read-only prompts, set the account controls in Fensory and state the intended instrument before any order.
Can I disconnect Claude?
Yes. Remove or disable the connector in Claude and switch agentic trading off in Fensory. The Fensory kill-switch stops the trading tools at the account layer.
Why should I distinguish a tokenized stock from a perpetual future?
They can track the same company and are different instruments. A tokenized equity is an issuer token. A perpetual future uses margin, can be leveraged and can be liquidated.