Account & Licensing

Activating your license key

New MTContext users often look for a license code in their welcome email — there isn't one. Activation works a little differently, and it's simple once you know the shape of it: you generate a terminal key in your dashboard and bind it to your terminal by connecting once. This article walks through it. What a terminal key is A terminal key is the single credential your Expert Advisor and your AI client both use. It looks like MTMCP- followed by 32 hex characters, and each key is bound to exactly one MetaTrader 5 terminal the first time that terminal connects with it. That one-key-one-terminal binding is what guarantees a command can never be routed to the wrong account. Step 1 — Generate the key 1. Log in to your dashboard with the email you used at checkout. 2. Go to Terminal Keys → Generate New Key. 3. Copy the key somewhere safe — the plaintext value is shown only once. If you lose it, you generate a new one; the old plaintext can't be revealed again. Step 2 — Bind it to your terminal A freshly generated key isn't usable until a terminal has connected with it once: 1. Install the MTContext Expert Advisor on the terminal you want to connect (see Installing the EA on MT5). 2. Enter the terminal key as the EA's license input and let it connect once. 3. When the EA shows as connected in your dashboard, the key is bound. It will now work in any MCP client configuration. Step 3 — Use it in your AI client With the key bound, add it to your AI client as the bearer token (Authorization: Bearer MTMCP-YOUR-TERMINAL-KEY) pointing at https://mcp.mtcontext.com/mcp/v1. The client guides — Connecting Claude Desktop and the others — show exactly where each client wants it. Does the free tier get a key? Yes. Every account, including free, generates a terminal key the same way — the tier just determines which tools the key can use (free keys are read-only). If activation isn't working - Confirm the key starts with MTMCP- and has no trailing spaces. - Confirm the EA has connected at least once so the key is bound. - A 401 Unauthorized means the key is invalid, mistyped, or revoked; a 403 Forbidden means it's valid but your tier lacks that tool's capability. See EA won't connect / shows "disconnected" and "No terminal connected" in your AI client for deeper troubleshooting. Next steps Ready to connect a client? See Connect any AI client to MetaTrader. Rotating a key safely later? That's covered in Rotating or revoking a terminal key. Manage your keys at mtcontext.com/dashboard.

Rotating or revoking a terminal key

A terminal key is a durable credential — anyone holding it can act on the bound terminal within your subscription's capabilities until you revoke it. That makes rotating and revoking keys worth knowing cold, both for routine hygiene and for the day one leaks. Rotate without downtime When you want to swap a key without interrupting anything, generate the new one first and retire the old one last: 1. Generate a new key in Dashboard → Terminal Keys → Generate New Key. 2. Update your client (and/or EA) configuration to use the new key. 3. Verify with a read-only prompt — "What's the EURUSD price?" (get_tick) or "What's my balance?" (get_account_info). 4. Once the new key works, revoke the previous key. Doing it in that order means there's never a moment where no valid key is in place. Revoke immediately on a suspected leak If a key may have been exposed, reverse the order — safety first: 1. Revoke the exposed key from Dashboard → Terminal Keys right away. The server stops issuing new sessions for it within seconds. 2. Then generate a new key and deploy it. What happens to sessions already running Revocation stops new sessions immediately, but a session token that's already been issued keeps working until it expires (by default within an hour) and then fails to refresh. So a live MCP session may keep functioning for a short window after you revoke — this is expected. For a true emergency, revoking is still the right move; the blast radius closes as the cached session token lapses. (See Session tokens: getting and rotating your JWT for how that token lifecycle works.) Notes and gotchas - The plaintext key is shown once at creation. If you lose it, you can't reveal it again — generate a new one and rebind. - A new key must be bound by letting a terminal connect with it once before it works in a client (see Activating your license key). - Revoking a key doesn't free a terminal seat the way you might expect if you're at your seat cap — see Terminal seats: PRO vs TEAM. Next steps For the broader hygiene picture, see Keeping your terminal key and JWT safe. If a client suddenly stops authenticating, see Auth errors and expired tokens. Manage your keys at mtcontext.com/dashboard.

Terminal seats: PRO vs TEAM

If you run more than one MetaTrader terminal — a couple of accounts, a demo and a live, or a whole team — you need to understand seats. A seat is simply one connected terminal, and your plan sets how many you can have at once. What a seat is One terminal seat = one MetaTrader 5 terminal bound and connected to your account. Each terminal you connect uses a terminal key, and each bound-and-active key occupies a seat. Read-only or trading, it's counted the same way. (MetaTrader 4 support is coming soon and will count the same.) How many each plan includes - Pro includes 1 seat, and you can add up to 4 more — a maximum of 5 terminals. - Team includes 5 seats, and you can add up to 10 more — a maximum of 15 terminals. Additional seats are a flat add-on ($19/mo or $190/yr each), the same price on both plans. Free and Enterprise don't use the paid seat add-on model. Choosing between Pro and Team on seats alone If seats were the only factor: pick Pro if you run up to five terminals, Team if you need more (or you want the analytics tools that come with Team regardless). But seats usually aren't the only factor — Team also unlocks the portfolio analytics, correlation, sentiment, and coaching tools. See Choosing a plan and subscribing for the full comparison. Seats and downgrades Your seat count can't drop below the number of terminal keys you're actively using. If you try to downgrade or remove seats while more terminals are connected than the new limit allows, the change is rejected until you revoke enough keys first. See Upgrading, downgrading, and cancelling. Next steps See Activating your license key to add a terminal, and Rotating or revoking a terminal key to free one up. Compare plans at mtcontext.com.