Before You Start

Every client-specific guide in this section assumes two things are already true:

1. Your Expert Advisor is installed on your MT4/5 terminal and has connected to the cloud at least once (see the EA install steps in your dashboard's onboarding flow).
2. You have a terminal key. If you don't have one yet, go to Generating a Terminal Key first; every other guide in this section depends on it.

Preflight checklist

Before opening your client config, verify these quickly:

• Dashboard shows your subscription active.
• EA is attached to a chart and running (smiley/active status in MT4/MT5).
• EA can reach the network (WebRequest/connection permissions are enabled if required by your terminal setup).
• Dashboard shows the target terminal as connected recently.
• You have the terminal key copied and ready.

If any item fails, fix it first; client config usually succeeds only after terminal connectivity is healthy.

Hosted vs self-hosted

Choose one path before configuring clients:

• Hosted: quickest path, no server process to run locally, recommended for almost all users.
• Self-hosted: best for local development, infrastructure control, or custom gateway behavior.

Then pick your client:

• Claude Desktop
• Claude Code
• Cursor
• Any other MCP client
• Self-hosted / local development

All of the hosted-server guides use the same underlying mechanism: a bearer-token Authorization header carrying your terminal key, sent to the hosted MCP endpoint. The only thing that changes between clients is where that configuration lives.

First connection test

After completing any client guide:

1. Restart or reload your client so MCP config is re-read.
2. Ask a read-only prompt, for example: "What is EURUSD bid/ask right now?"
3. Confirm the client calls get_tick and returns live values.

If this fails, open the troubleshooting section in your specific client page.