Skip to content

Cline MERX - TRON Resource Exchange execute_intent

How to: Cline MERX - TRON Resource Exchange execute_intent

client:Cline transport:streamable-http tool:execute_intent

Add MERX - TRON Resource Exchange to Cline

  1. 01

    Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp": {
      "url": "https://merx.exchange/mcp/sse"
    }
  }
}
  1. 02

    Save the file and restart Cline.

  2. 03

    Ask for something execute_intent does. Cline lists the server's tools on connect and calls execute_intent itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that MERX - TRON Resource Exchange's identifier in your config matches the one above exactly.

Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs

Set these first

MERX - TRON Resource Exchange will not start until these are set, so execute_intent never becomes available.

  • MERX_API_KEY
  • TRON_PRIVATE_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.