Skip to content

Fensory connection guide

Connect Cursor to Fensory

Cursor connects to Fensory as a remote Streamable HTTP MCP server. Add the Fensory endpoint to mcp.json and complete OAuth in the browser.

Cursor can use the tools exposed by the connected server. Fensory enforces three controls on the account: a kill-switch, a market allow-list and a per-order cap. Those controls still decide what the account may do. Fensory is not available to US persons.

Open FensorySee the MCP server

What you need

A current Cursor installation and an eligible Fensory account.

Connect Cursor

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

{ "mcpServers": { "fensory": { "url": "https://mcp.fensory.com/mcp" } } }
  1. 01

    Open the MCP configuration

    Open ~/.cursor/mcp.json for a personal connection or .cursor/mcp.json for a project connection.

  2. 02

    Add the Fensory endpoint

    Add the Fensory server entry shown above and save the file. The URL https://mcp.fensory.com/mcp identifies the remote Streamable HTTP server.

  3. 03

    Complete browser OAuth

    Enable the server and follow the sign-in prompt. Authorize the Fensory account whose markets and limits Cursor should reach.

  4. 04

    Check tools before using them

    Confirm that the Fensory tools appear in Cursor, then start with an account or market request that does not place an order.

Example prompts for Cursor

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 Fensory tools available in this session and separate read tools from tools that can place or cancel orders.

    Tool check

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

    Account check

  • Inspect xyz:TSLA, explain the instrument and prepare an order request with all required fields. Do not execute it.

    Request 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 Cursor

  • Cursor supports remote HTTP servers

    Use the Fensory HTTPS endpoint as a remote Streamable HTTP MCP server. A local command is not required for this connection.

  • Tool approval still applies

    Cursor may ask before running an MCP tool, depending on the approval settings. Connecting Fensory does not grant every tool automatic approval.

  • Account controls remain authoritative

    Cursor sees the tools available through the server, while the connected Fensory account still enforces a kill-switch, a market allow-list and a per-order cap.

Questions people ask

Do I need to edit mcp.json?
Yes. Cursor documents mcp.json as the configuration file for a custom remote MCP server. Use ~/.cursor/mcp.json for a personal connection or .cursor/mcp.json for a project connection.
Which transport does Fensory use in Cursor?
Fensory uses a remote Streamable HTTP endpoint over HTTPS. Cursor documents Streamable HTTP as a supported transport for remote MCP servers.
How does Cursor authenticate with Fensory?
Cursor opens an OAuth flow for the remote server. Sign in to the Fensory account you want Cursor to use and approve the connection.
Can Cursor place a real trade?
Yes, when agentic trading is enabled on the connected Fensory account and the requested market and order fit its controls. Start with read-only checks and an order preview.
Does Cursor receive my private key?
No. The connection uses browser OAuth. On the current MCP path, Hyperliquid trades use a scoped signing key that cannot withdraw, transfer or bridge funds.
Account controlsAll questionsBrowse markets