Cursor

Requires a terminal key that's already bound to a terminal.

Preflight

Before editing MCP config, check:

• You know whether your setup should be project-local (.cursor/mcp.json) or global (~/.cursor/mcp.json).
• Your Cursor version supports your intended transport (HTTP direct or stdio bridge).
• Your key has already been bound by a successful terminal connection.

Configure

Cursor reads MCP servers from .cursor/mcp.json in your project, or ~/.cursor/mcp.json globally. Recent versions support remote HTTP servers directly:

{
  "mcpServers": {
    "mtcontext": {
      "url": "https://mcp.mtcontext.com/mcp/v1",
      "headers": {
        "Authorization": "Bearer MTMCP-YOUR-TERMINAL-KEY"
      }
    }
  }
}

If your Cursor version only supports stdio-based servers, use the mcp-remote connector instead, which works identically across every MCP client:

npm install -g mcp-remote

{
  "mcpServers": {
    "mtcontext": {
      "command": "mcp-remote",
      "args": ["https://mcp.mtcontext.com/mcp/v1"],
      "headers": {
        "Authorization": "Bearer MTMCP-YOUR-TERMINAL-KEY"
      }
    }
  }
}

Replace MTMCP-YOUR-TERMINAL-KEY with your actual terminal key either way.

Verify

Open Cursor's MCP settings panel and confirm mtcontext shows a green/connected status. Then, in a chat, ask something that requires live data — "What's my current account equity?" — and confirm Cursor calls get_account_info and returns real numbers.

Trading tools default to dry_run: true until both conditions in Enabling live trading are met — the same rule applies regardless of which client is calling the tool.

Troubleshooting

• Config ignored: check JSON validity and whether Cursor loaded the correct file (project vs global).
• Connected but no tool calls: reload window and start a fresh chat.
• Auth errors: verify Bearer header format and key state.
• No account/market data: confirm terminal is online and EA is connected.