
CoinruleVerifiedFeatured
@Coinrule Inc
About Coinrule
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
Connection details
https://cloud.coinrule.com/mcpSetup
claude mcp add coinrule-mcp --transport http https://cloud.coinrule.com/mcpTools
17Use 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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
Overview
Last updated July 21, 2026
Coinrule MCP lets you connect a compatible AI model like ChatGPT, Claude, Gemini, Grok, etc. to your Coinrule account so you can inspect your portfolio, monitor strategies, run backtests, create trading strategies, and manage trading automation through a conversation. To find information or configure a strategy, you can describe what you want in plain language.
This article explains what Coinrule MCP is, how the connection works, what your AI assistant can do, and how to get started safely.
For a shorter product overview, see the Coinrule MCP overview. You can also explore the full Coinrule MCP documentation for individual setup guides and technical references.
What is Coinrule MCP?
MCP stands for Model Context Protocol. It is an open standard that allows AI assistants to connect to external software and use authorised tools.
Coinrule operates an official remote MCP server for Coinrule Cloud accounts. When you connect a compatible AI assistant, such as ChatGPT, Claude, Grok, or another client that supports remote MCP connections, the assistant can use the Coinrule functions you have authorised. You continue talking to the AI assistant in natural language, while Coinrule remains the underlying execution, validation, portfolio, and market-connectivity layer.
The problem MCP solves is the gap between describing a trading idea and working through the software needed to inspect, test, or automate it.
For example, instead of manually opening several pages to review your strategies and portfolio, you could ask your connected assistant to summarise your holdings and recent strategy activity. If you have granted the appropriate permissions, you can also describe a strategy, ask for it to be validated and backtested, and then create or launch it.
You do not need to know Coinrule's internal tool names or API structure. The assistant selects the relevant Coinrule tools based on your request. Strategies created through chat remain part of your regular Coinrule account and appear in the standard Agents dashboard alongside strategies created through the web interface.
Coinrule MCP is therefore an additional way to interact with Coinrule, rather than a separate trading account or standalone product. For broader information about using artificial intelligence with trading automation, you can also explore Coinrule's AI trading resources.
How Coinrule MCP works
At a high level, the connection involves three parts:
- You provide the instruction in normal conversational language.
- Your AI assistant interprets the request and decides which authorised Coinrule tool is needed.
- Coinrule MCP provides the controlled connection between the assistant and your Coinrule account.
The MCP server acts through the Coinrule API on your behalf. According to the Coinrule documentation, it does not provide the AI assistant with direct access to Coinrule databases, exchange keys, or your Coinrule password. Authentication is handled through OAuth 2.1, and you approve the level of access when you connect the assistant.
A request might follow a workflow like this:
- You ask your AI assistant to show your active strategies.
- The assistant identifies the appropriate Coinrule MCP tool.
- Coinrule returns the information allowed by your permissions.
- The assistant presents the result conversationally.
- With Read + Write access, the same model can be used for actions such as creating, updating, starting, or stopping strategies.
The Coinrule Agentic Trading MCP listing in the MCP Servers directory describes the official server as supporting the creation, backtesting, execution, and management of trading agents through natural language across crypto, stocks, and ETFs.
What can you do with Coinrule MCP?
The available MCP tools cover several parts of the Coinrule workflow.
Review your portfolio and connected accounts
With read access, your assistant can retrieve information about balances, holdings, portfolio allocation, recent signals, and connected exchange or broker accounts.
This can be useful when you want a conversational overview of your account without opening each individual strategy or account page.
Review your trading strategies
You can ask the assistant to list your strategies and inspect details such as their configuration, status, open positions, PnL, activity, trades, and recent signals.
Coinrule MCP also provides access to a combined activity feed across strategies, allowing your assistant to help summarise what your trading automation has been doing.
Create and manage strategies
With Read + Write access, your assistant can use Coinrule's strategy creation and management tools.
The documented tools support validating a proposed strategy, creating a strategy after validation, or turning a plain-language request into a validated, tested, and launched strategy in a more direct workflow. Existing strategies can also be updated, started, stopped, or paused. A stop action can optionally close open positions, so it is important to make your intention explicit when giving instructions.
Browse strategy templates
Your assistant can browse Coinrule's Script Library through MCP. Available templates can be filtered and used as the starting point for a new strategy.
This can be useful when you have a general objective, such as exploring DCA or RSI-based approaches, but would like to review existing templates before creating something from scratch.
Compare backtests
Coinrule MCP includes tools for reviewing saved backtests and running new historical simulations. With the appropriate permission, your assistant can also compare multiple parameter scenarios.
Backtesting can help you study how a strategy would have behaved on historical data before considering live execution. However, historical simulations and past performance do not guarantee future results.
Build and launch baskets
The MCP supports browsing curated baskets and creating custom multi-asset baskets. Coinrule's tools reference states that a custom basket can contain between two and 20 assets with defined target weights.
Baskets can be launched on a single venue or, where appropriate accounts are connected, across multiple venues.
Resources:
- Coinrule MCP: https://coinrule.com/mcp/
- MCP Server: https://cloud.coinrule.com/mcp
- Documentation: https://cloud.coinrule.com/docs/mcp
- AI Trading Agent: https://coinrule.com/ai-trading-agent/
- Coinrule Homepage: https://coinrule.com
Who is Coinrule MCP for?
Coinrule MCP can be useful whenever you prefer to interact with your trading automation conversationally rather than starting every task from a dashboard.
For example, you may use it to:
- Get a quick summary of balances, holdings, active strategies, or recent activity.
- Investigate what a running strategy has been doing.
- Turn a clearly defined trading idea into a strategy for validation and testing.
- Compare backtest scenarios.
- Explore Coinrule templates through your AI assistant.
- Manage existing strategies after reviewing their current status.
- Build or manage multi-asset baskets.
You can use Read only access when your main goal is account visibility and analysis. Read + Write is intended for workflows where you want your assistant to create or manage trading automation.
The broader idea behind Coinrule MCP is covered in more detail in Coinrule's article on MCP and AI trading agents.
How to set up Coinrule MCP
The exact location of connector settings depends on the AI assistant you use, but the general connection process is the same.
Before you start
You need:
- A Coinrule Cloud account. If you do not already have one, you can create a Coinrule account.
- An AI client that supports remote MCP connectors using OAuth.
- A connected exchange or broker account if you intend to execute live strategies.
- You can use paper trading without connecting a live exchange.
1. Open your AI assistant's integrations or connectors
Find the area where your AI client allows you to add apps, integrations, connectors, or custom remote MCP servers.
Coinrule provides specific connection guidance for supported clients in the Coinrule MCP documentation.
2. Add the Coinrule MCP server
Add the official Coinrule MCP server endpoint as a custom or remote MCP server.
Use the exact MCP endpoint without adding extra paths or query parameters.
3. Sign in to Coinrule
Your AI client will open the Coinrule sign-in flow.
Log in using your normal Coinrule account. Authentication takes place on Coinrule's side through OAuth 2.1; the AI assistant does not receive your Coinrule password or exchange API keys.
4. Choose your permission level
You can grant one of two access levels.
- Read only grants the
coinrule:readscope. The assistant can inspect information including strategies, balances, holdings, trades, signals, PnL, and backtests, but cannot place or change trades. - Read + Write grants both
coinrule:readandcoinrule:write. In addition to reading account information, the assistant can create, launch, update, start, and stop strategies, launch baskets, and run backtests.
5. Test your connection
Start with a simple read request.
For example, ask the assistant to show your balances or list your Coinrule strategies. This confirms that the assistant can reach your account with the permissions you selected.
Security, permissions, and best practices
Connecting an AI assistant to a trading account deserves the same care as any other automation that can affect real funds.
Start with the minimum access you need
If you only want to review your account or explore how MCP works, start with Read only access.
Write tools are not available to an assistant on a read-only connection. You can change your level later by revoking the connection and reconnecting with different permissions.
Remember that Read + Write can affect real funds
When Read + Write access is connected to a live exchange or broker account, your assistant can launch strategies that trade real funds.
Review consequential instructions carefully and make sure the strategy being created matches what you intended.
Consider paper trading while learning the workflow
Coinrule's guidance recommends considering paper trading while you build confidence in AI-assisted workflows.
A sensible process is to define your objective clearly, specify the asset, venue, timeframe, capital allocation, entry and exit conditions, position sizing, and risk limits, and then ask the assistant to explain the resulting strategy. You can validate the structure, run backtests, observe it with paper trading, and only consider live execution after your own review.
Be precise in your prompts
Ambiguous instructions can lead to unintended interpretations.
When relevant, specify whether you want paper or live trading, which asset and venue you mean, how much capital should be used, the timeframe, entry and exit conditions, and your risk parameters.
For management actions, be particularly clear about open positions. For example, stopping a strategy and stopping a strategy while closing its open position are not necessarily the same request.
Review and revoke connections when necessary
Connected assistants can be reviewed in Settings → Integrations in Coinrule.
The documentation states that each connection displays its access level and can be revoked immediately. Revoking access prevents that assistant from continuing to reach your account.
Coinrule also uses scoped OAuth permissions, expiring access tokens, rotating refresh tokens, and per-user rate limits. The MCP operates through the Coinrule API rather than receiving direct access to your exchange API keys.
Risk notice: Trading automation, AI-generated strategies, and analysis can contain errors. Trading involves risk, and backtests or simulations do not guarantee future performance. You should independently review strategies and decisions before using real capital.
Frequently asked questions
Can I use Coinrule MCP without allowing an AI assistant to trade?
Yes. Choose Read only access when connecting. This allows the assistant to inspect supported account and strategy information but does not give it access to write tools that can create or change trades.
Can I use Coinrule MCP without connecting a live exchange?
Yes. Coinrule's documentation states that paper trading can be used without a live exchange connection. A connected exchange or broker is required when you want to execute on a live account.
Does my AI assistant receive my Coinrule password or exchange API keys?
No. Coinrule MCP uses OAuth 2.1 for authentication. According to the Coinrule documentation, your assistant receives scoped access rather than your Coinrule password or exchange API keys.
Where can I see strategies created through my AI assistant?
Strategies created through the MCP appear in your regular Coinrule Agents dashboard, where they can be reviewed and managed alongside strategies created through the web app.
What should I do if my assistant can read my account but cannot create or manage strategies?
Check the permission level of your connection. Write tools are intentionally unavailable when the assistant has Read only access.
To enable supported write actions, reconnect the assistant and choose Read + Write access. Remember that on a connected live account, this permission can allow strategies to trade real funds.
For full setup information, troubleshooting, permissions, and individual client guides, visit the Coinrule MCP documentation. You can also read the Coinrule MCP product overview or view the official Coinrule Agentic Trading MCP directory listing.
Frequently asked questions
What is the Coinrule remote MCP server?
The Coinrule remote MCP server is a hosted Model Context Protocol endpoint at https://cloud.coinrule.com/mcp, so AI assistants can connect to it without installing or running anything locally.
How do I connect to the Coinrule MCP server?
Add the endpoint https://cloud.coinrule.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Does the Coinrule MCP server require authentication?
Yes. Coinrule uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Which transport does the Coinrule MCP server use?
Coinrule exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
Basic information
Transport
Streamable HTTP
Authentication
OAuth
Category
Finance & Commerce
Author
Coinrule Inc
Submitted by
Coinrule
Comments