Skip to content

Cursor un comtrade mcp server comtrade_get_data_availability

How to: Cursor un comtrade mcp server comtrade_get_data_availability

client:Cursor transport:streamable-http tool:comtrade_get_data_availability

Add un comtrade mcp server to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "un-comtrade-mcp-server": {
      "url": "https://un-comtrade.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that un comtrade mcp server'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

un comtrade mcp server will not start until these are set, so comtrade_get_data_availability never becomes available.

  • COMTRADE_SUBSCRIPTION_KEY
  • MCP_LOG_LEVEL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.