To connect TradingView to MT5, send your TradingView alerts to PineConnector and run the PineConnector Expert Advisor (EA) in an MT5 terminal. With PineConnector Edge, we host that terminal for you. You connect your broker account in Portal, then configure and test your alerts. Your own computer can be off after setup.
The traditional route remains available: install the EA in MT5 on your own Windows computer or VPS and manage that environment yourself. This guide explains the difference, walks through Edge setup and finishes with a demo trade you can verify at your broker.
What changes with PineConnector Edge?
The alert path stays the same: TradingView → PineConnector Bridge → the PineConnector EA in MT5 → your broker. Edge changes where MT5 runs and who maintains the hosting. It does not choose your trades or replace your broker account.
| Your setup | PineConnector Edge | Self-hosted MT5 |
|---|---|---|
| Where MT5 runs | Hosted by PineConnector. | Your Windows computer or Windows VPS. |
| Installation and upkeep | No local MT5 or EA installation. Manage the hosted connection in Portal. | You install MT5 and the EA, and maintain the terminal and its host. |
| Your own computer | Can be off after setup. Use your browser to manage the connection. | Must stay running if it hosts MT5. A separately running VPS lets your computer be off. |
| Supported environment | MT5 with the PineConnector EA, on supported broker servers. No MT4 or third-party EAs. | Use your own supported environment when you need other EAs or terminal controls. |
| EA settings | View and change in Portal → Edge → EA Settings; applying a change restarts the terminal. | Configure the EA in your own terminal. |
| Monitoring | Bridge processing history and hosted Experts and Journal logs in Portal. | Bridge processing history, plus Experts and Journal in your MT5 terminal. |
Start with Edge if you want the TradingView-to-MT5 workflow without maintaining an always-on terminal. Choose self-hosted when you need another EA or control of your Windows environment. Check the current Edge support and EA Settings guide before choosing.
You can manage Edge from a Mac or Windows browser without installing the PineConnector EA locally. Use your broker’s supported MT5 mobile app, web terminal or desktop terminal to inspect the actual positions and history.
Before you connect
- PineConnector access: an active Core, Plus or Pro plan with an available connection. Edge and self-hosted accounts share your plan’s connection allowance. If you have a legacy subscription, check its Edge access in Portal.
- A demo MT5 account: have the account number, trading password and exact broker server name ready. Use the trading password, rather than a read-only investor password.
- An exact supported server: check the Edge server directory, then confirm the match in Portal’s live Broker Server Name selector. A similar server name is not a substitute.
- TradingView webhook access: your plan must support webhooks and two-factor authentication must be enabled.
Check the recipients before testing. An alert’s License ID selects every account connected to that ID, including Edge and self-hosted accounts. Review them in Portal → Connections. Keep a demo test separate from live accounts; use a separate available ID when those accounts should receive different instructions.
Connect MT5 with PineConnector Edge
The Connect MT5 walkthrough has screenshots for every step. Here is the full connection sequence:
- Open Portal → Edge → Add Instance. Start with the demo account you prepared.
- Choose the intended License ID in Select a license. Check which other accounts receive its alerts, then select Next Step.
- Complete Configure Broker. Enter a recognisable Connection Name, your demo Trading Account Number and Trading Account Password. Select the exact Broker Server Name. These are your broker’s MT5 details, not your TradingView or PineConnector password.
- Review, then select Go live once. Confirm the demo account and License ID first, and read Portal’s password-saving notice. Wait for the on-screen setup checks instead of creating another instance while it is working.
- When Your instance is live appears, select Confirm. “Live” here means the hosted instance is running; your broker account can still be demo. Select the listed instance and check its connection name and broker.
- Open Connections and copy that account’s License ID. Confirm the broker, intended demo account and Edge tag. Copy the value unchanged using the copy icon.
If setup reports a problem, read the result and recheck the broker account, password and server. Ask PineConnector Support if it remains unresolved; repeatedly adding instances is not a diagnosis.
Configure the TradingView webhook and message
The same webhook URL and PineConnector Syntax apply to Edge and self-hosted MT5. In your TradingView alert, open Notifications, tick Webhook URL and paste:
https://webhook.pineconnector.comPut the trading instruction in Message, not in the webhook field. The message structure is:
LicenseID,Command,Symbol,ParametersFor example, the following illustrative demo buy request asks for 0.01 lots of EURUSD without a stop loss or take profit. It is not an executed trade. Replace LicenseID with the copied ID and EURUSD with your broker’s exact symbol, including any prefix or suffix. On Edge, the Symbols tab (Portal → Edge → Symbols) lists every symbol your broker offers, with its specification, so you can copy the exact name into the alert (Symbols guide). Symbol names are case-sensitive and can differ between account types on the same server. Check that the demo instrument permits 0.01 lots and is open for trading.
LicenseID,buy,EURUSD,vol_lots=0.01Use a demo account. A buy message can place a real-money order if a live account receives it. Check every recipient of the ID before creating the alert. If Signal Authentication is enabled, use the authenticated form in Test your setup and add the matching secret privately in TradingView. Never put a broker password in an alert message.
The PineConnector Syntax reference explains supported commands, volume methods, stops and targets. The symbol on your TradingView chart is not automatically the symbol your broker uses for orders.
Finish with a verified demo trade
A connected instance confirms setup, not trading. The test walkthrough separates a connection test from an actual TradingView-to-broker demo order.
First, check the connection. The fixed LicenseID,test,test message checks delivery and the expected processing record. The docs connection-test tool or a Portal test can help isolate that part of the path. It does not prove a broker trade or your TradingView alert configuration.
Then test from TradingView. Follow the walkthrough’s temporary price alert using Price → Greater Than → 0 and Only Once (some layouts say Once only). Use a chart receiving positive live quotes and an open trading session for the broker instrument. Name it Demo trade test, paste the reviewed buy message, enable the webhook and select Create once. This temporary condition tests the connection; it is not a strategy recommendation.
- TradingView → Alerts → Log: find the test and check the time and actual message that fired.
- Portal → Bridge: match the new entry to the time and intended account. Read the message, symbol, action and processing result. In Logs, the Edge tag identifies hosted processing; read the separate status for its result.
- Your broker account: open its positions or history in a supported MT5 interface. Confirm the intended demo account, exact symbol, Buy direction, permitted volume and no unexpected additional order. For the unchanged example, expect 0.01 lots and no SL or TP from that message.
Close the demo position through your broker interface, then disable or delete the temporary alert. The setup test is complete when the TradingView event matches its processing record and the expected broker trade, with no unintended duplicate.
Before resending a trading command, check the broker account’s positions and history. A delayed notification is not proof that the first request failed. Keep one test alert active rather than creating several copies while waiting.
Prefer the traditional self-hosted route?
Use the MT5 EA installation guide for the complete screenshot walkthrough. This route uses a supported Windows environment with the PineConnector EA and DLL. The published guide does not support installing that DLL workflow directly in macOS or in MetaQuotes’ built-in VPS service.
- Install MT5 and log in to your demo broker account. Download the current PineConnector MT5 EA package from Portal → Downloads.
- Open File → Open Data Folder → MQL5 → Experts. Extract the EA and DLL files directly into that terminal’s Experts folder, rather than a subfolder.
- Enable terminal permissions. In Tools → Options → Expert Advisors, allow algorithmic trading and DLL imports. Enable Algo Trading on the toolbar.
- Attach the EA to one chart. Refresh Expert Advisors in Navigator, then select Attach to Chart. Check the EA’s own Allow Algo Trading and Allow DLL imports permissions too.
- Enter your License ID in Inputs. Confirm the intended broker account in Portal → Connections.
- Keep the host and terminal running. Configure the TradingView alert and complete the same demo verification above.
You do not need a MetaTrader WebRequest URL for this MT5 installation. The webhook belongs in TradingView. If you want your own terminal running separately from your computer, read the Windows VPS setup guide. ForexVPS (affiliate link) offers Windows VPS plans for MetaTrader.
Switching from self-hosted MT5 to Edge
Keep one active PineConnector receiver per broker account. Running the same account through Edge and a self-hosted terminal under the same alert License ID can cause duplicate execution.
Before any move, ask Support to confirm the supported procedure for your connection. If you are migrating a live account, rehearse the Edge workflow on a separately routed demo account before the live cutover. Reconnecting a live account does not make it demo. Never send this article’s example buy request to a live account.
- Review before cutover. Check open positions, pending orders and active alerts, including any other EA or terminal-side trailing or exit logic. Pause the relevant alerts so they cannot fire during the move.
- Stop the old PineConnector receiver before testing Edge on that account. Close the old terminal or remove its PineConnector EA. Confirm it is no longer receiving commands.
- Connect and review Edge. Recheck the broker account and all recipients in Connections. Copy the License ID actually assigned to the Edge connection; update the alert if you chose a different ID.
- Validate for the account you moved. On a demo account, use the full TradingView demo test, check the broker outcome and remove the temporary alert before re-enabling the intended strategy alerts. For a live account, follow the validation procedure confirmed with Support; do not use the demo buy example as a live test.
Stopping the receiver does not close broker positions or cancel pending orders. Manage them through your broker or another terminal. The webhook URL and syntax stay the same, but do not assume a restart or migration will replay missed alerts or transfer the previous terminal’s state. The Edge interruption and account guidance explains what to review before a change.
If an alert fires but no trade appears
| Where the evidence stops | What to check next |
|---|---|
| No TradingView log event | Check the alert condition, enabled state and incoming chart quotes. Creating an alert does not mean it has triggered. |
| TradingView event, no matching Bridge entry | Check the webhook checkbox, exact URL, License ID and complete message. Follow An alert is missing. |
| Bridge entry, unexpected result | Read the actual processing details. Match any reported error to the EA error guide, rather than assuming a cause. |
| Processing record, no expected broker trade | Inspect the broker account, trading session and exact symbol. Read Experts and Journal; on Edge, select the instance in Portal → Edge. Check positions and history before resending. |
| Unexpected duplicate | Review every recipient of the License ID, active self-hosted receivers and the TradingView event count. Pause the relevant alerts while investigating. |
A green connection indicator or a received webhook is useful evidence, but neither guarantees a broker order. TradingView notes that webhook delivery can occasionally fail; your broker also determines whether a requested trade is accepted.
Connect your own strategy
After the demo test, use Connect your strategy to choose the alert workflow for your indicator or strategy. Check the actual message, symbol, size and exits before enabling it. A condition that buys successfully does not establish your strategy’s closing logic or profitability.
Your next step: open Connect MT5, connect one demo account with Edge and work through Test your setup. For current access and connection allowances, check Portal or the current plans.
Frequently asked questions
Do I still need a VPS with Edge?
You do not need your own VPS for the supported PineConnector Edge workflow. Edge hosts MT5 and the PineConnector EA. A self-managed Windows VPS remains an option when you need other EAs or control of the terminal environment.
Can I use the same alerts after switching?
The webhook and syntax are unchanged. Check the License ID assigned to the new connection and all its recipients. Stop the old receiver for that account before testing the new one.
Does Edge support MT4 or custom EAs?
No. Edge hosts MT5 with the PineConnector EA. For MT4 or another EA, review the appropriate self-hosted documentation instead.
Can I change the hosted EA settings?
Yes. Open Portal → Edge → EA Settings to view and change the hosted EA’s settings. Applying a change restarts the terminal, so signals pause for about a minute, and the tab shows whether your saved settings are the ones the terminal is running. See the EA Settings guide.
Related reading
- What is PineConnector Edge? Hosted MT5, explained
- VPS for automated trading
- TradingView to MT5 without an always-on PC
Updated 3 October 2026; Edge EA Settings updated 6 October 2026. Setup instructions and product limits were checked against the current sources below. The message example is illustrative; no trading account or order was used to produce this article.
Sources and current documentation
- PineConnector Docs: Connect MT5, and PineConnector Edge. Setup, routing, supported scope and hosted controls.
- PineConnector Edge and current plans. Check current access and account allowances in Portal.
- TradingView: How to configure webhook alerts. Webhook requirements and delivery limitations.
- PineConnector Syntax and Test your setup. Message structure and end-to-end demo verification.
- PineConnector Docs: Install the MT5 EA. Self-hosted installation and compatibility.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
