GT App MCP is a connector that lets AI agents — Claude, ChatGPT, Cursor, or any tool that speaks the Model Context Protocol — act inside your GT Protocol account. Instead of clicking through a dashboard, you describe what you want in plain language and your agent does it: launches bots, watches deals, pauses risk, runs backtests. Same actions as the app, driven by conversation.
This article walks through what MCP is, what GT App MCP unlocks for traders, and the new workflows it opens up — including the one we used to run five frontier LLMs as portfolio managers in our AI Hedge Fund experiment. No code, no setup minutiae. If you want the integration guide, that lives in our help center.
What is MCP, and why does it matter for trading?
MCP, or Model Context Protocol, is an open standard released by Anthropic in late 2024 for connecting AI assistants to external systems. Before MCP, each AI app had its own way of talking to outside tools — a custom plugin format, a one-off API wrapper, a brittle browser automation. MCP replaces all of that with a single shared language. Any AI agent that speaks MCP can read from and write to any system that exposes an MCP server, with the user staying in control of permissions.
For trading, the implication is direct. A trading platform that ships an MCP server stops being a UI you click through and becomes a set of capabilities your AI can use on your behalf. The agent doesn't need screen-scraping or fragile prompts to operate it. It just asks, you approve, and the action happens on the real account.
What is GT App MCP?
GT App MCP is the GT Protocol implementation of that standard, exposing the trading capabilities of GT App to any compatible AI agent. The current build covers 18 actions, grouped into four areas: bots (create, start, stop, update, paper-clone, archive), deals (open manually, close, list active, view history), accounts (linked exchanges, balances, profile), and research (run a backtest before risking capital). That's roughly everything a user does in the dashboard — now reachable through a chat window.
The connection is permissioned. Your agent signs in with your GT account, the same credentials you use on the web app, and operates inside the same limits. You can revoke access at any time. It's not a black box bot trading on your behalf in some shared infrastructure; it's your assistant, with your keys, doing what you tell it.
Who it's for
Three groups get clear leverage from it:
- Active traders who already work inside Claude or ChatGPT and want to stop tab-switching. "Show me my open positions and PnL today" replaces five clicks.
- Researchers and builders who want to script trading experiments in natural language — backtest a thesis, paper-trade the winners, promote the best to a real bot.
- Power users running multiple portfolios who want their agent to handle the routine: morning check, rebalance suggestion, kill-switch on a losing bot.
What can you actually do with it?
The shortest answer: everything you'd do in the GT App dashboard, you can now do by asking. The longer answer is more interesting, because conversation changes the shape of the task. Clicking is sequential — open the bot list, find the one you want, open its page, scroll to the panel, hit the button. Chat is declarative — "close any bot on Binance that's down more than 5% today" — and the agent figures out the steps. That's a different kind of interface, not just a faster one.
Here are five workflows users have built on top of it:
1. The morning portfolio review
You open Claude, type "give me a summary of my GT positions, flag anything unusual." The agent pulls your active deals, totals the PnL, notices that one bot has been in drawdown for three days, and asks whether to pause it. You say yes. Done in under a minute, with full context, without leaving the chat.
2. Idea-to-bot in one conversation
You describe a strategy — "DCA into ETH on the 4-hour, take profit at 3%, safety orders if it drops 2% twice." Your agent translates the description into the right bot configuration, runs a backtest on recent history, shows you the result, and offers to spin up a paper-trading clone so you can watch it live without risking funds. If you like what you see after a week, you promote it to a real bot in the same chat.
3. The risk kill-switch
Volatility spikes. You write "close every active deal on my account, then stop all bots." The agent executes in sequence and reports back. The same instruction in a panicky moment would take a minute of clicking — long enough for prices to move against you.
4. Research without spreadsheets
You ask your agent to pull deal history for the last 90 days, group by symbol, and tell you which pairs have been profitable and which have been a drag. It reads the data, does the math, and answers. No CSV export, no pivot table.
5. Automated agents that trade autonomously
This is the frontier use case. Builders point an autonomous AI agent at GT App MCP and let it manage a portfolio on its own — making decisions, opening positions, closing losers — on a schedule. We did exactly this with our AI Hedge Fund: five frontier models (Claude, GPT, Gemini, DeepSeek, Grok) given the same MCP toolset, the same budget, and instructions to trade crypto for a quarter. The whole experiment runs on the public MCP server. Read the results here.
How is this different from a Telegram bot or copy-trading?
GT Protocol has shipped AI-driven trading interfaces before — a Telegram assistant that takes natural-language commands, a marketplace for copy-trading other people's strategies. MCP is a different layer. The Telegram bot lives inside Telegram, with its own UI conventions and one specific AI model behind it. Copy-trading is a one-way flow where you follow someone else's decisions. GT App MCP is the underlying capability surface, and it works with any AI agent the user prefers — Claude, ChatGPT, a custom-built one, a local model running on their laptop. The user picks the brain; GT provides the hands.
That matters for two reasons. First, AI models are moving fast and people have preferences. An interface tied to one model ages quickly; an MCP server works with whatever comes next. Second, the agent stays in the user's own AI environment, with all their other tools and context — calendar, notes, browser, code editor. Trading becomes one capability inside a larger workflow, not a separate destination.
What about safety?
Two layers of safety apply, and both are user-controlled. The first is the AI agent itself — Claude and ChatGPT both ask for confirmation before any MCP action with side effects (creating a bot, closing a deal, moving funds). You see what's about to happen and approve it. The second is the GT account layer — exchange API keys connected to GT operate under the same trading-only permissions you set when you linked them, and you can revoke MCP access without touching the rest of the account.
For risk management specifically, the paper-trading clone feature is the safety valve. Any bot you've configured can be cloned to a demo version that runs with simulated money against live prices. Tell your agent to paper-trade an idea for a week before going real, and you've quietly removed most of the downside of letting an AI assist with trading decisions.
Frequently Asked Questions
What is GT App MCP in one sentence?
GT App MCP is a connector that lets AI agents like Claude and ChatGPT operate inside your GT Protocol account — creating bots, opening and closing deals, running backtests — using natural-language instructions instead of dashboard clicks.
Which AI agents does it work with?
Any agent that supports the Model Context Protocol standard. As of 2026 that includes Claude Desktop, Claude Code, ChatGPT (via desktop apps that support MCP), Cursor, and a growing list of independent agent frameworks. The list expands as MCP adoption grows.
Do I need to write code to use it?
No. End users install the connector once through their AI app's settings, sign in with their GT account, and then interact entirely in chat. The setup is a one-time configuration step, similar to enabling any other plugin or extension.
Is it safe to let an AI trade for me?
It's as safe as you make it. The AI confirms every state-changing action before executing. You can restrict it to read-only inquiries, paper-trading, or specific bot operations. Exchange API keys keep their original permissions (typically trading-only, no withdrawals). Most users start with portfolio inquiries and paper-trading before delegating any live decisions.
Does it cost extra?
The MCP connector itself is free. You only pay the standard GT Protocol fees on actual trading activity, plus whatever your AI provider charges (Claude, ChatGPT, etc.) for the conversation itself. There's no MCP-specific subscription.
What's the catch — what can't it do yet?
The current 18 actions cover the full lifecycle of bots and deals plus account inquiries and backtests. Marketplace copy-trading and TradingView webhook setup aren't exposed through MCP yet — those still happen in the web app. We'll add them as the surface stabilizes.
Can I build my own AI trader with it?
Yes — that's one of the things we explicitly designed for. The GT App MCP server is the same one we used to run five frontier LLMs as autonomous portfolio managers in our AI Hedge Fund experiment. If you want to point a custom agent at your account and let it manage a strategy on a schedule, the capability is there.
Try it
The fastest way to see what MCP changes is to use it. Sign in to GT App, set up a paper-trading bot, then connect your AI agent and ask it about that bot's performance. The shift from clicking to conversing takes about thirty seconds to feel natural — and after that it's hard to go back.