Cursor xRocket Exchange MCP xrocket_onboarding_links
How to: Cursor xRocket Exchange MCP xrocket_onboarding_links
Add xRocket Exchange MCP to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"xrocket": {
"url": "https://xrocket-mcp-production.up.railway.app/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something xrocket_onboarding_links does. Cursor lists the server's tools on connect and calls xrocket_onboarding_links itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that xRocket Exchange MCP'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
xRocket Exchange MCP will not start until these are set, so xrocket_onboarding_links never becomes available.
-
XROCKET_PROFILE -
XROCKET_ENVIRONMENT -
XROCKET_API_TOKEN -
XROCKET_ENABLE_TRADING -
XROCKET_TRADING_LIMIT -
XROCKET_ENABLE_TRANSFERS -
XROCKET_ENABLE_WITHDRAWALS -
XROCKET_ALLOW_MAINNET_WRITES -
XROCKET_APPROVAL_TTL_MS
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.