Coinrule
About
The Coinrule MCP is an official Model Context Protocol server that connects AI assistants, Claude, ChatGPT, Grok, and others, directly to your Coinrule Cloud account https://cloud.coinrule.com/mcp
Details
- Author
- Coinrule Inc
- Downloads
- 1,600
- Transport
- SSE
- Categories
- Finance
Jump to
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
CoinruleCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
{
"mcpServers": {
"coinrule-mcp": {
"type": "http",
"url": "https://cloud.coinrule.com/mcp"
}
}
}
list_strategies
Use this when the user asks to see their Coinrule trading bots, agents, or strategies. Returns name, status, venue, and strategy_url dashboard links. Do not use for live PnL (get_strategy_status), trade history (get_strategy_trades), or browsing templates before creating a bot (list_strategy_templates).
get_strategy
Use this when the user wants full configuration and metadata for one existing strategy. Response includes strategy_url — share that link when they ask where to open it. Do not use for live positions/PnL (get_strategy_status), recent events (get_strategy_activity), or creating a new bot (create_strategy_from_prompt).
get_strategy_status
Use this when the user asks how a running strategy is performing right now: open positions, live PnL, paper balance, or proximity to triggers. Do not use for historical trades (get_strategy_trades), event logs (get_strategy_activity), or listing all bots (list_strategies).
get_strategy_activity
Use this when the user asks for the event log of one strategy: signals fired, lifecycle changes, evaluation notes. Do not use for executed trade rows (get_strategy_trades), cross-bot feed (get_strategy_feed), or live PnL snapshot (get_strategy_status).
get_strategy_trades
Use this when the user asks for filled trade history or closed positions for one strategy. Do not use for trigger/signal events (get_strategy_activity), PnL time series (get_strategy_pnl), or portfolio-wide holdings (get_portfolio_holdings).
get_strategy_pnl
Use this when the user asks for profit/loss over time for one strategy (chart/history). Do not use for current live PnL (get_strategy_status) or individual trade rows (get_strategy_trades).
get_strategy_feed
Use this when the user asks what happened recently across all of their strategies (dashboard-style activity feed). Do not use for one strategy's log (get_strategy_activity) or buy/sell signal focus (get_recent_signals).
list_backtests
Use this when the user asks to see saved historical backtest runs. Do not use to start a new backtest (run_backtest) or export trades from a run (get_backtest_export).
get_backtest
Use this when the user asks for results summary of one saved backtest run by id. Do not use to list all runs (list_backtests) or download raw trade export (get_backtest_export).
get_backtest_export
Use this when the user wants raw backtest trades or export data for analysis. Do not use for high-level metrics only (get_backtest) or running a new simulation (run_backtest).
get_portfolio_balances
Use this when the user asks about cash or quote balances on connected exchanges and open strategy allocations. Do not use for total portfolio value / holdings breakdown (get_portfolio_holdings) or bot performance (get_strategy_status).
get_portfolio_holdings
Use this when the user asks what assets they hold, portfolio value, or allocation across coins/stocks. Do not use for free cash on exchanges (get_portfolio_balances) or a single bot's trades (get_strategy_trades).
get_recent_signals
Use this when the user asks about recent buy/sell signals or trigger events across bots. Omit strategy_id to search all strategies. Do not use for full trade history (get_strategy_trades), one strategy's event log (get_strategy_activity), or the cross-strategy feed (get_strategy_feed).
list_exchange_accounts
Use this when the user wants connected exchange accounts or needs venue_id and account_id before launching live trading. Call before create_strategy, create_strategy_from_prompt, or launch_basket on live venues. Do not use for portfolio balances (get_portfolio_balances) or listing bots (list_strategies).
list_baskets
Use this when the user wants to browse multi-asset Coinrule baskets (curated themes or their custom baskets) before launching. Curated entries use basket_slug; custom entries use custom_basket_id. Do not use for single-strategy Script Library templates (list_strategy_templates) or searching tickers (list_basket_assets).
list_basket_assets
Use this when the user is building a custom basket and needs to validate tickers or search the asset universe. Call before create_basket. Do not use to browse ready-made baskets (list_baskets) or launch a basket (launch_basket).
list_strategy_templates
Use this when the user wants to browse pre-built Coinrule strategy scripts (RSI, DCA, TradingView, etc.) before launching. Each entry includes full script text for validate_strategy or create_strategy_from_prompt. Do not use for multi-asset baskets (list_baskets) or the user's already-running bots (list_strategies).
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"coinrule": {
"coinrule-mcp": {
"type": "http",
"url": "https://cloud.coinrule.com/mcp"
}
}
}
}McpServers
{
"coinrule-mcp": {
"type": "http",
"url": "https://cloud.coinrule.com/mcp"
}
}Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
