> ## Documentation Index
> Fetch the complete documentation index at: https://public-openfx.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP connectors

> Connect Claude, ChatGPT, Claude Code, or Codex to your OpenFX account to query trades, deposits, and withdrawals in plain language.

Use the OpenFX connector to ask an AI app questions about your OpenFX account, build reports, and analyze trades, deposits, and withdrawals in plain language. You don't need an API key or any developer work.

## What the connector can do

The OpenFX connector is read-only. It retrieves information from your OpenFX account. It can't place trades, initiate withdrawals, move funds, or change any OpenFX records.

| Data | What you can ask for |
| - | - |
| Currency pairs | Pairs available to your organization |
| Trade history | Past trades, filterable by date, pair, and status |
| Deposit history | Incoming deposits and their status |
| Withdrawal history | Outgoing withdrawals and their status |
| Withdrawal accounts | Saved withdrawal destinations on your account |

## Before you begin

* **An OpenFX admin has turned on your AI app for your organization.** In the OpenFX dashboard, go to **Organization > MCP Platforms** and switch on the toggle for Claude, ChatGPT, Claude Code, or Codex. Only users with the Admin role can change this setting.
* **You have an OpenFX login.** Any OpenFX user can connect. The connector sees only what your OpenFX role already allows.
* **Your AI app plan supports custom connectors.** Each tab below lists the plan requirements.
* **You know which environment you want.** Live and Sandbox use different URLs. You set up each connection separately, even though your OpenFX login is shared between them.

| Environment | OpenFX MCP server URL |
| - | - |
| Live | `https://mcp.openfx.com/mcp` |
| Sandbox | `https://mcp-sandbox.openfx.com/mcp` |

## Connect your AI app

Choose your AI app. Every user completes the account connection step once per environment, including the admin who added the connector.

<Tabs>
  <Tab title="Claude">
    Claude Team and Enterprise organizations add the connector once for everyone. Claude Free, Pro, and Max users add it themselves. Free plans allow one custom connector, so Free users can add Live or Sandbox, not both.

    **Add OpenFX to Claude (Team or Enterprise)**

    Only a Claude organization Owner or Primary Owner can do this. On Enterprise, people with a custom role that includes **Manage access to Libraries** can also do it. Members skip to "Connect your OpenFX account" once it is done.

    <Steps>
      <Step title="Open the connector settings">
        In Claude, go to **Organization settings > Connectors**. Select **Add**, hover over **Custom**, then select **Web**.
      </Step>

      <Step title="Name the connector and add the URL">
        Enter the name `OpenFX`, or `OpenFX Sandbox` for the Sandbox URL. Paste the OpenFX MCP server URL for your environment, then select **Continue**.
      </Step>

      <Step title="Confirm the authentication settings">
        Review the settings Claude detected and select **Continue**. Keep OAuth sign-in on, and keep **OAuth client** set to **Use Claude's published identity (Recommended)**. OpenFX doesn't support the other OAuth client options.
      </Step>

      <Step title="Add the connector">
        Select **Add**. To add both environments, repeat these steps with the Sandbox URL and name each connector clearly so members pick the right one.
      </Step>
    </Steps>

    **Add OpenFX to Claude (Free, Pro, or Max)**

    <Steps>
      <Step title="Open your connectors">
        In Claude, go to **Customize > Connectors**, select **+**, then select **Add custom connector**.
      </Step>

      <Step title="Enter the connector details">
        Enter the name `OpenFX`, paste the OpenFX MCP server URL for your environment, then select **Continue**.
      </Step>

      <Step title="Add the connector">
        Keep the default authentication settings, with **OAuth client** set to **Use Claude's published identity (Recommended)**. Select **Add**.
      </Step>
    </Steps>

    **Connect your OpenFX account**

    <Steps>
      <Step title="Start the connection">
        Go to **Customize > Connectors**, search for OpenFX, select **OpenFX**, then select **Connect**.
      </Step>

      <Step title="Sign in to OpenFX">
        Claude redirects you to OpenFX. Sign in with your usual OpenFX email, password, and 2FA. If you're already signed in, OpenFX skips this step.
      </Step>

      <Step title="Approve access">
        Review the read permissions on the OpenFX consent screen, then select **Approve**. OpenFX shows a success screen and returns you to Claude. The OpenFX connector now shows as connected.
      </Step>
    </Steps>

    **Use OpenFX in a conversation**

    <Steps>
      <Step title="Turn on the connector">
        Start a new chat. Select **+** at the bottom left of the message box, select **Connectors**, and make sure OpenFX is switched on.
      </Step>

      <Step title="Ask your question">
        Claude asks for permission the first time it uses each OpenFX tool. Choose **Allow once** or **Always allow**.
      </Step>
    </Steps>
  </Tab>

  <Tab title="ChatGPT">
    ChatGPT Business, Enterprise, and Edu workspaces add OpenFX once for everyone. On individual plans, custom apps require Developer mode, which depends on your plan. Check OpenAI's documentation for current availability.

    <Warning>
      Custom apps work in ChatGPT on the web only, not in the ChatGPT mobile apps.
    </Warning>

    **Add OpenFX to your workspace**

    A ChatGPT workspace owner or admin completes this once. Members skip to "Connect your OpenFX account" once it is done.

    Developer mode must be on for the admin doing this. On Business, each admin or owner switches it on for themselves, and can do so from the **Create** screen below. On Enterprise and Edu, an admin first allows it under **Workspace settings > Permissions & Roles > Connected Data**, then switches it on in **Settings > Apps > Advanced settings**.

    <Steps>
      <Step title="Create the app">
        Go to **Workspace settings > Apps** and select **Create**. If prompted, switch on Developer mode.
      </Step>

      <Step title="Fill in the form">
        Enter these values and leave **Advanced settings** at their defaults. OpenFX doesn't use a Client ID or Client Secret.

        * **Name:** `OpenFX`, or `OpenFX Sandbox`
        * **Description:** `Read-only access to OpenFX trades, deposits and withdrawals`
        * **MCP Server URL:** the OpenFX URL for your environment
        * **Authentication:** OAuth
      </Step>

      <Step title="Scan the tools">
        Select **Scan Tools**. Sign in to OpenFX when prompted, then wait for the scan to finish so ChatGPT loads the OpenFX tools.
      </Step>

      <Step title="Save the draft">
        Check the acknowledgment box if shown, and select **Create**. ChatGPT saves OpenFX as a draft.
      </Step>

      <Step title="Publish the app">
        Go to **Workspace settings > Apps > Drafts**, find OpenFX, and select **Publish**. On Enterprise and Edu, use **Configure Access** to choose which groups can use OpenFX, and **Configure Actions** to review the OpenFX tools. Review the safety warnings and select **Publish**.
      </Step>
    </Steps>

    <Note>
      ChatGPT keeps a snapshot of the OpenFX tools taken when the app is published. If OpenFX adds or changes tools, an admin must refresh the app's tool list from **Workspace settings > Apps**. You don't need to delete and re-create the app.
    </Note>

    **Add OpenFX on an individual plan**

    <Steps>
      <Step title="Turn on Developer mode">
        Go to **Settings > Apps > Advanced settings** and switch on **Developer mode**.
      </Step>

      <Step title="Create the app">
        Go to **Settings > Apps** and select **Create**. Enter the name `OpenFX`, a short description, and the OpenFX MCP server URL for your environment. Set authentication to OAuth.
      </Step>

      <Step title="Scan the tools">
        Select **Scan Tools**, sign in to OpenFX when prompted, then select **Create**. OpenFX appears under **Settings > Apps > Enabled Apps** with a **Dev** label.
      </Step>
    </Steps>

    **Connect your OpenFX account**

    <Steps>
      <Step title="Start the connection">
        Search for OpenFX in the ChatGPT apps directory. Your workspace's published apps are labeled **custom**. Select **OpenFX**, then select **Connect**.
      </Step>

      <Step title="Sign in to OpenFX">
        ChatGPT redirects you to OpenFX. Sign in with your usual OpenFX email, password, and 2FA. If you're already signed in, OpenFX skips this step.
      </Step>

      <Step title="Approve access">
        Review the read permissions on the OpenFX consent screen, then select **Approve**. OpenFX shows a success screen and returns you to ChatGPT. The OpenFX app now shows as connected.
      </Step>
    </Steps>

    **Use OpenFX in a conversation**

    <Steps>
      <Step title="Turn on the app">
        Start a new chat. Select **+** in the message box, select **More**, then select **OpenFX**. The OpenFX icon appears in the message box.
      </Step>

      <Step title="Ask your question">
        For follow-ups that need fresh data, mention `@OpenFX` again.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Claude Code">
    Claude Code is included with Claude Pro, Max, Team, and Enterprise plans, and also works with a Claude Console account. Install and sign in to Claude Code before you start.

    <Note>
      Using Claude Code in the Claude desktop app? Desktop app sessions don't load servers added from the terminal. Use the Claude tab instead. Once OpenFX is connected in Claude, it's available in your desktop app Code sessions with no extra setup.
    </Note>

    **Allow OpenFX in your organization's MCP policy (admins only)**

    Skip this step if your organization doesn't restrict which MCP servers Claude Code can use. If OpenFX is blocked, members see an "enterprise policy" error when they add it. An administrator who manages Claude Code settings completes this once. Choose the option that matches how your organization manages MCP servers.

    <AccordionGroup>
      <Accordion title="Your organization uses an MCP allowlist">
        Add the OpenFX URLs to `allowedMcpServers` in your managed settings. Use server-managed settings in the Claude admin console, or a `managed-settings.json` file deployed through your device management tool. Add this fragment to your settings file:

        ```json theme={"theme":{"light":"poimandres","dark":"poimandres"}}
        {
          "allowedMcpServers": [
            { "serverUrl": "https://mcp.openfx.com/mcp" },
            { "serverUrl": "https://mcp-sandbox.openfx.com/mcp" }
          ]
        }
        ```

        Add these entries to your existing list rather than replacing it. Match OpenFX by `serverUrl`, not `serverName`, because each user chooses their own server names. Also check that no entry in `deniedMcpServers` matches the OpenFX URLs, because the denylist always wins.
      </Accordion>

      <Accordion title="You want to provide OpenFX to everyone">
        List OpenFX under `managedMcpServers` in your managed settings. Every user gets OpenFX automatically, alongside their own servers, and skips the add step. This requires Claude Code v2.1.259 or later. Add this fragment to your settings file:

        ```json theme={"theme":{"light":"poimandres","dark":"poimandres"}}
        {
          "managedMcpServers": {
            "openfx": {
              "type": "http",
              "url": "https://mcp.openfx.com/mcp"
            },
            "openfx-sandbox": {
              "type": "http",
              "url": "https://mcp-sandbox.openfx.com/mcp"
            }
          }
        }
        ```

        Each user still signs in to OpenFX with their own login. Don't add OpenFX credentials or headers to this file.
      </Accordion>

      <Accordion title="Your organization deploys a fixed server list">
        Users can't add servers themselves in this mode. Add the same `openfx` entries from the previous option under `mcpServers` in your `managed-mcp.json` file, then redeploy it.

        | Platform | `managed-mcp.json` location |
        | - | - |
        | macOS | `/Library/Application Support/ClaudeCode/managed-mcp.json` |
        | Linux and WSL | `/etc/claude-code/managed-mcp.json` |
        | Windows | `C:\Program Files\ClaudeCode\managed-mcp.json` |
      </Accordion>
    </AccordionGroup>

    To confirm the change, run `claude mcp list` on a managed machine. OpenFX appears in the list.

    **Add OpenFX to Claude Code**

    Skip this step if your admin provides OpenFX to everyone. Run `claude mcp list`. If `openfx` is already listed, go to the next section. If you already connected OpenFX in Claude and sign in to Claude Code with the same Claude account, Claude Code picks up your Claude connectors automatically. OpenFX appears as `claude.ai OpenFX` under `/mcp`, and you can skip to "Use OpenFX in a session".

    <Steps>
      <Step title="Add the server">
        Run the command for your environment.

        <CodeGroup>
          ```bash Live theme={"theme":{"light":"poimandres","dark":"poimandres"}}
          claude mcp add --transport http --scope user openfx https://mcp.openfx.com/mcp
          ```

          ```bash Sandbox theme={"theme":{"light":"poimandres","dark":"poimandres"}}
          claude mcp add --transport http --scope user openfx-sandbox https://mcp-sandbox.openfx.com/mcp
          ```
        </CodeGroup>

        `--scope user` makes OpenFX available in every project on your computer. Leave it out to add OpenFX to the current project only.
      </Step>

      <Step title="Confirm the server">
        Run `claude mcp list` and confirm `openfx` appears.
      </Step>
    </Steps>

    **Connect your OpenFX account**

    <Steps>
      <Step title="Start the sign-in">
        Run `claude`, type `/mcp`, select **openfx**, then select **Authenticate**. You can also run `claude mcp login openfx` from your terminal.
      </Step>

      <Step title="Sign in to OpenFX">
        Your browser opens to OpenFX. Sign in with your usual OpenFX email, password, and 2FA. If you're already signed in, OpenFX skips this step. If your browser doesn't open, copy the sign-in link Claude Code shows and open it yourself.
      </Step>

      <Step title="Approve access">
        Review the read permissions on the OpenFX consent screen, then select **Approve**. OpenFX shows a success screen. Return to your terminal. `/mcp` now shows OpenFX as connected.
      </Step>
    </Steps>

    **Use OpenFX in a session**

    Start Claude Code in any folder and mention OpenFX in your question, for example "Using OpenFX, …". Claude Code asks for permission the first time it uses each OpenFX tool. Approve it once, or allow it for future sessions.
  </Tab>

  <Tab title="Codex">
    Codex is included with ChatGPT Plus, Pro, Business, Edu, and Enterprise plans. Install and sign in to Codex before you start.

    <Note>
      The Codex app, Codex CLI, and Codex IDE extension share the same MCP settings. Add OpenFX once from any of them and it's available in all three. Codex doesn't use the OpenFX app your workspace published in ChatGPT, so set it up here even if you already use OpenFX in ChatGPT.
    </Note>

    **Allow OpenFX in your organization's MCP policy (admins only)**

    Skip this step if your organization doesn't restrict which MCP servers Codex can use. If OpenFX is blocked, it shows as disabled in Codex after you add it. An admin who manages Codex requirements completes this once.

    <Steps>
      <Step title="Add the allowlist entries">
        Add these entries to the `mcp_servers` allowlist in your Codex requirements.

        ```text theme={"theme":{"light":"poimandres","dark":"poimandres"}}
        [mcp_servers.openfx]
        identity = { url = "https://mcp.openfx.com/mcp" }

        [mcp_servers.openfx-sandbox]
        identity = { url = "https://mcp-sandbox.openfx.com/mcp" }
        ```
      </Step>

      <Step title="Deliver the requirements">
        Use the method your organization already uses. In the ChatGPT Admin Console, open **Agent Security** and add the entries to your cloud-managed requirements. These apply to users who sign in to Codex with ChatGPT. With device management, add the entries to the system `requirements.toml` file, or to the `requirements_toml_base64` key in the `com.openai.codex` preference domain on macOS.

        | Platform | `requirements.toml` location |
        | - | - |
        | macOS and Linux | `/etc/codex/requirements.toml` |
        | Windows | `%ProgramData%\OpenAI\Codex\requirements.toml` |
      </Step>
    </Steps>

    <Warning>
      Codex enables a server only when both its name and its URL match an allowlist entry. Tell members to use the exact names `openfx` and `openfx-sandbox`. Add these entries to your existing allowlist rather than replacing it. An empty `mcp_servers` allowlist disables every MCP server.
    </Warning>

    **Add OpenFX to Codex**

    Choose the path that matches how you use Codex. You only need one.

    <Tabs>
      <Tab title="Codex CLI">
        Run the command for your environment, then run `codex mcp list` and confirm `openfx` appears.

        <CodeGroup>
          ```bash Live theme={"theme":{"light":"poimandres","dark":"poimandres"}}
          codex mcp add openfx --url https://mcp.openfx.com/mcp
          ```

          ```bash Sandbox theme={"theme":{"light":"poimandres","dark":"poimandres"}}
          codex mcp add openfx-sandbox --url https://mcp-sandbox.openfx.com/mcp
          ```
        </CodeGroup>
      </Tab>

      <Tab title="Codex app">
        <Steps>
          <Step title="Add a server">
            Go to **Settings > MCP servers**, then select **Add server**. In the Codex IDE extension, the same settings are under the gear menu.
          </Step>

          <Step title="Enter the details">
            Enter the name `openfx`, or `openfx-sandbox` for the Sandbox URL. Use these exact names if your organization uses an MCP allowlist. Choose **Streamable HTTP** and paste the OpenFX MCP server URL for your environment.
          </Step>

          <Step title="Save the server">
            Save the server.
          </Step>
        </Steps>
      </Tab>
    </Tabs>

    **Connect your OpenFX account**

    <Steps>
      <Step title="Start the sign-in">
        Run `codex mcp login openfx` in your terminal. In the Codex app, open **Settings > MCP servers** and select **Authenticate** next to OpenFX.
      </Step>

      <Step title="Sign in to OpenFX">
        Your browser opens to OpenFX. Sign in with your usual OpenFX email, password, and 2FA. If you're already signed in, OpenFX skips this step.
      </Step>

      <Step title="Approve access">
        Review the read permissions on the OpenFX consent screen, then select **Approve**. OpenFX shows a success screen. Return to Codex. OpenFX now shows as connected.
      </Step>
    </Steps>

    **Use OpenFX in a session**

    Start a new Codex thread in the app, or run `codex` in your terminal. In the CLI, type `/mcp` to confirm OpenFX is active. Mention OpenFX in your question, for example "Using OpenFX, …". Depending on your approval settings, Codex may ask you to approve OpenFX tool calls.
  </Tab>
</Tabs>

## Try it

Start a new conversation or session and try one of these prompts:

* "Show me all my trades from last month, grouped by currency pair, with total notional per pair."
* "Compare my deposit and withdrawal totals month over month for Q3 and flag anything unusual."
* "List the currency pairs available to my organization."
* "Build a reconciliation table of every withdrawal this week with its destination account."

<Tip>
  Scheduled or recurring reports use your AI app's own scheduling features. OpenFX doesn't run schedules on your behalf.
</Tip>

## Manage or disconnect

You can disconnect from your AI app or from OpenFX.

| AI app | Disconnect from the app |
| - | - |
| Claude | Go to **Customize > Connectors**, select **OpenFX**, then select **Disconnect**. Claude organization Owners can remove the connector for everyone from **Organization settings > Connectors**. To change the URL, remove the connector and add it again. |
| ChatGPT | Go to **Settings > Apps**, select **OpenFX**, then select **Disconnect**. Workspace admins can unpublish or delete OpenFX for everyone from workspace apps. |
| Claude Code | Run `claude mcp list` to see status, `claude mcp logout openfx` to sign out and keep the server, or `claude mcp remove openfx` to remove it and its stored sign-in. To change the URL, remove OpenFX and add it again. If your admin provides OpenFX through managed settings, you can turn it off for yourself in `/mcp`, and admins remove it for everyone by deleting the entry from managed settings. |
| Codex | Run `codex mcp list` to see status, `codex mcp logout openfx` to sign out and keep the server, or `codex mcp remove openfx` to remove it. In the Codex app, use **Settings > MCP servers**. Admins block OpenFX for everyone by removing its entries from the `mcp_servers` allowlist. |

To disconnect from OpenFX, go to **Profile > MCP Platforms** in the OpenFX dashboard. Your AI app is listed with its connection status. Select **Disconnect** to end the session. This works even if you no longer have access to the AI app account or the computer where it's installed.

An OpenFX admin can also switch an AI app off for the whole organization under **Organization > MCP Platforms**. This disconnects every user in the organization.

## Session length

Your connection stays active for 30 days from when you approve access on the OpenFX consent screen, whether or not you use it. You don't need to sign in again during that time. After 30 days, your AI app asks you to sign in to OpenFX again. If your OpenFX user is suspended or removed, the connection stops working immediately.

## Troubleshooting

| What you see | What to do |
| - | - |
| "MCP is not enabled for your organization" | Ask an OpenFX admin to switch on your AI app under **Organization > MCP Platforms**, then try connecting again. |
| "Unsupported platform" | You added the URL to an AI app OpenFX doesn't support. Use Claude, ChatGPT, Claude Code, or Codex. |
| A dataset is missing, for example withdrawal accounts | The connector shows only data your OpenFX role allows. Ask your OpenFX admin to review your role. |
| You see test data, or expected test data is missing | Check that you added the right URL. Live and Sandbox are separate connections. |
| Your AI app asks you to sign in again | Your session expired. Complete the OpenFX sign-in again. In Claude Code, run `/mcp`. In Codex, run `codex mcp login openfx`. |
| OpenFX isn't listed in Claude under **Customize > Connectors** | Your Claude Owner hasn't added it yet. Share this page with them. |
| OpenFX doesn't appear in ChatGPT search | Your workspace admin hasn't published it yet, or hasn't given your group access. Share this page with them. |
| OpenFX is missing in ChatGPT on your phone | Custom apps work on the web only. Use `chatgpt.com` in a browser. |
| Claude Code: "Cannot add MCP server "openfx": not allowed by enterprise policy" | Your organization uses an MCP allowlist that doesn't include OpenFX. Ask your Claude Code admin to allow the OpenFX URLs. |
| Claude Code: "Cannot add MCP server "openfx": server is explicitly blocked by enterprise policy" | OpenFX matches your organization's denylist. Ask your Claude Code admin to remove the matching entry. |
| Claude Code: "enterprise MCP configuration is active and has exclusive control over MCP servers" | Your organization deploys a fixed server list. Ask your Claude Code admin to add OpenFX to `managed-mcp.json`. |
| OpenFX disappeared from `/mcp` after working before | Your organization's MCP policy changed and now blocks OpenFX. Share this page with your Claude Code admin. |
| OpenFX is missing in the Claude desktop app | Desktop app sessions don't load servers added from the terminal. Connect OpenFX in Claude instead. |
| Codex shows OpenFX as disabled | Your organization uses an MCP allowlist. Check that you named the server exactly `openfx` or `openfx-sandbox`. If it's still disabled, ask your admin to allow the OpenFX URLs. |
| Every MCP server is disabled in Codex | Your organization's allowlist is empty. Share this page with your admin. |
| Anything else | Contact OpenFX support at [support@mail.openfx.com](mailto:support@mail.openfx.com) with the time of the error and the AI app you were using. |

<Note>
  Data you retrieve is returned to your AI app and processed under that provider's terms: Anthropic for Claude and Claude Code, OpenAI for ChatGPT and Codex. Review the provider's data policies and your organization's AI usage policy before connecting.
</Note>