Documentation / Strategies
Strategies + MCP
Create an account, choose a paid plan, then create an API key. Put the key in the assistant’s settings, never in the chat. Paper works with a read key on a paid plan. LIVE places real orders through the same engine as Terminal. Pause is the kill switch.
Full Hyperliquid tape is ready
Hosted paper (strategy_paper) uses the Hyperliquid tape we already keep for the desk — the same fills Terminal charts from. Not a 30-day sample, not another exchange. Call it after the key is on a paid plan.
Hosted MCP (any internet LLM)
Put the key in client config, never in the chat. Header X-Api-Key or Authorization: Bearer mtdp_….
Always-on REST: GET/POST https://app.mrtrades.com/v1/mcp/tools|/call
Short path + JSON-RPC: https://app.mrtrades.com/mcp
Cursor / Claude Desktop
Paste this into Settings → Tools & MCP or ~/.cursor/mcp.json. Do not clone the repo.
Optional: run a local copy
Grok / Claude.ai / ChatGPT
Click-by-click, including the Grok CLI command and a paste-ready system prompt: Connect an assistant.
Publishing alerts for followers? That is a published webhook strategy, not this MCP YAML path.
YAML
Alert, entry, exit, risk only. The assistant does not submit orders; the engine does. Paper can see same-size print runs, the cloud on a higher timeframe (and a 1-minute reclaim), and the book when we have history. A trail can arm at the band, not only after a fixed bounce. Paper returns the actual fills so you can plot them. If the assistant needs a feature we do not have yet, it can file a request on your account — you will see it under Portal Support. The legal name list is for assistants: llms-strategies.txt. After paper, call strategy_paper with save: true or strategy_save in the same session so the run is stored. Default risk is fixed_notional — the YAML notional_usd is the size, then capped by available buying power. Hyperliquid requires a minimum order value of $10. If sizing would land under that, the engine raises to $10 when buying power allows; otherwise it blocks (below_exchange_min_notional) instead of submitting dust that the exchange rejects. The runtime blotter is entries and includes reject reasons; use hosted paper for closed-trade stats. Portal Strategies shows those stats and a copyable follow link. Author share stays on the MrTrades account. This page is the contract — not Nexus scanner docs or HyperTape credits.
Optional peak pullback trail: the engine can arm when price reaches the cloud band (or after a profit threshold you set), then track the best price and close if it pulls back. You can still keep a fixed take-profit and a hard stop from entry. Put trail under exit or as an item in exit.any. Hosted paper and live use the same rule.
Use a longer hold / wider take-profit if you want the trail to run instead of a short scalp timer.
Optional daily profit goal (live): when open profit on the account hits risk.daily_goal_usd, remaining trades close, working orders cancel, and new automated entries stop until the next UTC day. Turn on daily_goal_keep_runners to leave strong winners with a trailing stop that stays above the locked goal. Manual Terminal orders are not blocked. A daily loss limit (0 = off) only blocks new automated entries; it does not close open trades.