fxapis

Read and trade your MetaTrader 5 accounts from Claude Code, with every trade confirmed.

Website · Docs · MCP guide · Status · Support

This is the plugin marketplace for fxapis, the hosted MetaTrader 5 API. Its one plugin, fxapis, connects Claude Code to the fxapis MCP server, teaches Claude how to trade MT5 carefully, and adds a hook that makes you confirm every trade and refuses live accounts until you allow them.

/plugin marketplace add FXapis/fxapis-claude-plugins
/plugin install fxapis@fxapis

Table of contents

• Quick start

• What's inside

• How sign-in works

• Safety model

• Configuration

• Example prompts

• Use it outside Claude Code

• Troubleshooting

• Development

• Related fxapis repositories

• Contributing

• Support

• License

Related MCP server: MT5 MCP Server

Quick start

You need Claude Code and an fxapis account with at least one MT5 account connected in the console. Connecting an MT5 account takes its broker password, so it is done in the console and never through Claude.

1. Add the marketplace and install the plugin. Inside Claude Code:

/plugin marketplace add FXapis/fxapis-claude-plugins
/plugin install fxapis@fxapis

Or from your shell:

claude plugin marketplace add FXapis/fxapis-claude-plugins
claude plugin install fxapis@fxapis

2. Sign in. Ask for something that needs fxapis, such as /fxapis:status. The first tool call opens fxapis's sign-in page in your browser. Approve read access, and turn on trading only for the accounts you want.

3. Check your accounts.

/fxapis:status
/fxapis:positions

To update later, run /plugin marketplace update fxapis.

What's inside

.
├── .claude-plugin/marketplace.json        # the "fxapis" marketplace
└── plugins/fxapis/
    ├── .claude-plugin/plugin.json         # manifest and userConfig
    ├── .mcp.json                          # the fxapis MCP server
    ├── commands/                          # status, positions, connect-help
    ├── hooks/hooks.json                   # PreToolUse matcher for the seven trade tools
    ├── scripts/confirm-trade.mjs          # the confirmation hook
    └── skills/trading-mt5-safely/         # SKILL.md and its references

How sign-in works

• OAuth on first use. With no API key set, the first fxapis tool call opens fxapis's sign-in page in your browser. Sign-in is OAuth 2.1 with PKCE, as the MCP authorization spec describes.

• You choose what Claude may do. Read access (accounts, positions, orders, deals, figures, quotes) is always included. Trading is off by default; turn it on per account. It needs two-factor on your fxapis account, and you can also set a maximum order size and a number of orders a day.

• Revocable at any time. Every connected app is listed on the API keys page under Connected apps. Revoke ends its access on its next request.

• An API key is optional. For an agent that runs unattended, create a key with only the scopes it needs and set it as the plugin's api_key option. The plugin sends it as the X-API-Key header and stores it as a sensitive value.

Safety model

Several layers stand between a prompt and an order. The first two are enforced by fxapis on every call, whatever the model decides.

1. What you allowed. A read-only connection cannot trade. A trading connection can change only the accounts you picked, within the limits you set. An API key can do only what its scopes allow.

2. Two-factor for trading. Letting an app trade requires two-factor on your fxapis account.

3. The confirmation hook. It runs before each of the seven trade tools: place_market_order, place_pending_order, close_position, modify_position, cancel_order, place_multi_account_order and cancel_multi_account_order.

   • It always answers ask, so Claude Code shows a confirmation dialog even in auto-accept mode, with one line saying what will happen, for example fxapis: buy 0.10 lots EURUSD at market on account … — demo.

   • If fxapis has reported the account as live in this session, and allowLiveTrading is off, the trade is denied.

   • An account not yet listed in the session is marked "demo or live not known yet" and asked about, never assumed safe.

   • It learns each account's environment only from fxapis's own list_accounts, get_account and get_account_overview results in the session transcript, never from user text or other tools' output. Once an account is seen as live, it stays live for the session.

   • If anything goes wrong while checking, it still asks.

4. The skill. It tells Claude to suggest a demo run first, name the environment ("LIVE account 5012345") in every proposal, wait for an explicit yes per trade, and never resend an order whose outcome is unknown. This shapes behaviour; layers 1 to 3 enforce.

fxapis has no simulated market: broker demo accounts are how you test.

Configuration

The plugin declares two options in plugin.json. Set them with /plugin → fxapis → configure.

Turning on allowLiveTrading does not skip confirmation: every trade, demo or live, is still asked about.

Example prompts

• "Which of my MT5 accounts are online, and what positions are open on each?"

• "How much margin would 0.5 lots of XAUUSD need on my demo account?"

• "Is the EURUSD market open on my demo account right now?"

• "Bring all my accounts online, then tell me when they are ready."

• "Buy 0.01 lots of EURUSD on the demo account with a 20-pip stop."

• "Move the stop loss on my gold position to break-even."

• "Did anything go wrong with today's orders? Show me any that are still unknown."

Prompts that trade need a connection with trading turned on for that account, and each one stops at the confirmation dialog.

Use it outside Claude Code

There is no one-click link that adds a plugin marketplace to Claude Code or a custom connector to claude.ai; use the commands and steps below.

claude.ai and Claude Desktop

1. Open Customize → Connectors → Add custom connector. On Team and Enterprise plans, an Owner adds it under Organization settings → Connectors.

2. Remote MCP server URL: https://api.fxapis.com/mcp. Leave the OAuth client fields empty.

3. Click Connect and sign in to fxapis in the window that opens.

For the skill, download trading-mt5-safely.zip and upload it under Settings → Capabilities → Skills. The hook and commands are Claude Code features and are not part of the connector. Full steps: docs.fxapis.com/guides/claude-plugin.

Claude Code without the plugin

claude mcp add --transport http fxapis https://api.fxapis.com/mcp

Then run /mcp, choose fxapis and Authenticate. The hook also matches a server added this way under the name fxapis, but only when the plugin is installed.

VS Code and Cursor

These clients sign in through a vscode:// or cursor:// return address, which fxapis does not accept yet, so they connect with an API key instead. They get the MCP server only, without the skill or the hook.

• VS Code asks for the key once and keeps it in its secret storage.

• Cursor reads it from the FXAPIS_KEY environment variable, so set that before starting Cursor.

The configs behind these buttons, and ones for other clients, are in fxapis-mcp-examples and the MCP guide.

Troubleshooting

More: docs.fxapis.com/guides/mcp and status.fxapis.com.

Development

Requires Node.js 20 or later.

npm test                                         # hook, manifest and skill tests (node --test)
claude plugin validate . --strict                # the marketplace
claude plugin validate ./plugins/fxapis --strict # the plugin
claude --plugin-dir ./plugins/fxapis             # try it locally

CI runs the same tests and both validations on every push and pull request.

Related fxapis repositories

Contributing

Issues and pull requests are welcome. This repository is published from the fxapis monorepo, so accepted changes are applied there and then copied here. Please run the tests and both claude plugin validate commands before opening a pull request, and test anything that trades on a broker demo account.

Support

• Docs: docs.fxapis.com/guides/claude-plugin

• Status: status.fxapis.com

• Bugs: open an issue

• Everything else: support@fxapis.com

License

MIT