Skip to content

Cursor MERX - TRON Resource Exchange execute_intent

How to: Cursor MERX - TRON Resource Exchange execute_intent

client:Cursor transport:streamable-http tool:execute_intent

Add MERX - TRON Resource Exchange to Cursor

  1. 01

    Open ~/.cursor/mcp.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 Cursor.

  2. 03

    Ask for something execute_intent does. Cursor 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.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor 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.