MCP Server Overview
The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. TradeStaq's MCP server exposes your entire trading platform to AI clients like Claude Desktop, Cursor, and Claude Code — so you can manage portfolios, deploy bots, run backtests, and execute trades through natural language.
What is MCP?
MCP defines a standard way for AI models to discover and call external tools. Instead of copying data between your browser and an AI chat, MCP lets the AI interact with TradeStaq directly. You describe what you want in plain English, and the AI translates that into the right API calls.
What TradeStaq's MCP Server Provides
| Resource Type | Count | Description |
|---|---|---|
| Tools | 31 | Executable actions — deploy bots, fetch prices, run backtests, manage portfolios |
| Prompts | 3 | Pre-built prompt templates for common workflows |
| Resources | 3 | Read-only data sources the AI can reference |
Tool Categories
| Category | Tools | Examples |
|---|---|---|
| Authentication | 4 | Login, OAuth, token management |
| Market Data | 3 | Prices, exchange listing, trading pairs |
| Portfolio | 2 | Balances, positions across exchanges |
| Strategies | 6 | List, search, get details, FORGE AI generation |
| Backtesting | 3 | Run backtests, check status, get results |
| Bot Management | 5 | Deploy, stop, configure, list bots |
| Trade History | 2 | Recent trades, trade details |
| Copy Trading | 3 | Leaderboard, follow/unfollow masters |
| Advisor | 3 | AI trading advice, portfolio analysis |
Prompts
- portfolio-review — Analyze your current portfolio and suggest improvements
- strategy-backtest — Walk through backtesting a strategy step by step
- bot-deployment — Guide you through deploying a new trading bot
Resources
- exchanges — List of supported exchanges and their capabilities
- strategies — Available trading strategies in the marketplace
- account — Your account status and subscription details
Scoped Access for Remote Agents
Remote OAuth tokens carry a scope that limits what the agent can do. Pick the narrowest scope that unlocks the workflow you want:
| Scope | What the agent can do |
|---|---|
mcp:read | Browse strategies, read market data and portfolios |
mcp:paper | Everything in mcp:read plus create paper exchanges and deploy paper bots |
mcp:live | Everything in mcp:paper plus live-money deploys and wallet-charging tools (e.g. generate_strategy) |
See the Authentication guide for the full scope model and how check_auth surfaces tier capabilities, wallet balance, and token scope.
Installation
The MCP server is available as an npm package and as a remote HTTP endpoint:
# npm package
@the-staq/tradestaq-mcp
# Remote URL (no install needed)
https://mcp.tradestaq.com/mcp
See the Setup Guide for full configuration instructions for your AI client.
For Third-Party MCP Clients
If you're building an MCP client and want to connect to TradeStaq on behalf of your users, TradeStaq runs a standards-compliant OAuth 2.1 authorization server with Dynamic Client Registration (RFC 7591). No contact with TradeStaq needed — clients self-register, authorize via PKCE, and receive a short-lived scoped access JWT (60 min) plus a rotating refresh token (30 days) for silent renewal. See Discovery & .well-known endpoints for the full first-contact flow.
Next Steps
- Setup Guide — Configure Claude Desktop, Cursor, or Claude Code
- Tools Reference — All 31 tools with parameters and descriptions
- Authentication — In-chat auth + OAuth 2.1 + Dynamic Client Registration
- Discovery & .well-known — Programmatic first-contact endpoints for MCP clients
- HTTP Transport — Remote server and self-hosting options
- Troubleshooting — Common errors and fixes