Connect an AI assistant to your desk

Every assistant gets its own private link to your desk. You make it in the dashboard, and paste it into the assistant once.

1. Open the dashboard and go to Profile → AI assistants.
2. Name it after the assistant, for example Claude — that is the name you will see when it asks to trade.
3. Choose what it may do. Look only can read everything and change nothing. Look and trade (with my tap) can also ask to place orders, flatten and pause copying. Start with look only; you can always add a trading link later.
4. Set limits (optional). Which accounts it may use; for a trading link, which instruments (for example MNQ, MES), its largest order in contracts, and any accounts where it may trade without asking you — keep that to simulation accounts.
5. Press Create link and copy it. It looks like https://www.meridiansignaldesk.com/mcp/mrd_…. It is shown only once: if you lose it, revoke it and create another.

The link is the key to your desk — anyone who has it can use it. Paste it only into your own assistant, never into a shared file, chat or repository.

1. In Claude on the web or the desktop app, open Settings → Connectors.
2. Choose Add custom connector.
3. Name it Meridian and paste your link as the URL. Leave Advanced settings empty — your link already carries its key, so there is no OAuth sign-in.
4. Press Add. Meridian now appears in your connectors.
5. In a chat, open the + menu (or the tools menu), go to Connectors and make sure Meridian is switched on for that chat.
6. The first time Claude uses a Meridian tool it may ask your permission. Allowing the look-only tools always is fine; for trading tools you approve each order on your phone anyway.

A connector added on claude.ai is also available in the Claude desktop and mobile apps. On a Team or Enterprise plan, an owner may first need to allow custom connectors under Admin settings → Connectors. Custom connectors depend on your Claude plan, and Claude may name its menus slightly differently over time.

ChatGPT connects to MCP servers in developer mode, which you switch on once.

1. Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.
2. Back in Apps & Connectors, choose Create to add a new connector.
3. Name it Meridian, add a short description such as My trading desk, and paste your link as the MCP server URL.
4. For Authentication choose No authentication — the link carries its own key.
5. Confirm you trust the connector and press Create.
6. Start a new chat, open the + or tools menu, pick Developer mode and switch Meridian on.

Developer mode is available on paid ChatGPT plans; on Business and Enterprise an admin may need to allow it. OpenAI has moved this setting before — if it is not where described, look for Developer mode in Settings.

Run this once in a terminal, with your own link at the end:

claude mcp add --transport http --scope user meridian https://www.meridiansignaldesk.com/mcp/mrd_YOUR_LINK

--scope user makes Meridian available in every project and keeps the link in your own settings. Do not add it with --scope project: that writes the link into a .mcp.json file that is easy to commit by mistake.

Start Claude Code and type /mcp to check that meridian shows as connected.

1. Open Cursor's Settings → MCP and choose Add new global MCP server. This opens mcp.json in your home folder (~/.cursor/mcp.json).
2. Add Meridian, with your own link:

{
  "mcpServers": {
    "meridian": {
      "url": "https://www.meridiansignaldesk.com/mcp/mrd_YOUR_LINK"
    }
  }
}

3. Save the file. Back in Settings → MCP, Meridian should show a green dot and its list of tools.
4. Ask about your desk in Cursor's Agent chat.

Use the global file, not a project's .cursor/mcp.json, so the link never ends up in a code repository.

1. Open the Command Palette and run MCP: Open User Configuration.
2. Add Meridian, with your own link. Note that VS Code uses servers, not mcpServers:

{
  "servers": {
    "meridian": {
      "type": "http",
      "url": "https://www.meridiansignaldesk.com/mcp/mrd_YOUR_LINK"
    }
  }
}

3. Save, then run MCP: List Servers and start meridian if it is not running.
4. Open Copilot Chat in Agent mode — MCP tools are only used there.

Any assistant that can add a remote MCP server over HTTP (often called Streamable HTTP) can connect — Windsurf, Zed, Cline, Goose and others. Use your link as the server URL and choose no authentication.

If an assistant asks for a token separately instead, use these two settings:

URL:     https://www.meridiansignaldesk.com/mcp
Header:  Authorization: Bearer mrd_YOUR_LINK_KEY

Here the key is everything after /mcp/ in your link. An assistant that can only run local programs (servers it starts with npx or python) cannot connect to Meridian directly.

Ask in plain English. A few ideas to start with:

1. You ask the assistant to trade. It sends Meridian a request, not an order.
2. Meridian checks it against the link's limits and your accounts first — an order for a follower, an instrument or size you did not allow, or an account the link may not use is refused straight away.
3. The request arrives in your Telegram chat with Approve and Cancel, as a phone notification, and under Waiting for you on the dashboard. It says which assistant is asking, exactly what, and the reason it gave.
4. Tap Approve and the copier places it — the same way it places a TradingView alert, so your daily limits, drawdown floor, contract caps, trade hours and news protection all still apply, and a leader's followers copy it as usual. Tap Cancel, or do nothing, and nothing happens: a request expires after two minutes.
5. The assistant waits up to about a minute for your answer and then tells you the result — or that it is still waiting. You can ask it later whether the order went through.

Flatten everything always asks, on every link. Accounts you put on a link's no tap needed list trade without asking — meant for simulation accounts while you get used to it.