Connect Sentimentrader to MCP Clients
Enable your AI agents to access backtesting, market data, and analysis tools through our MCP server.
Help me connect to Sentimentrader MCP. Use OAuth sign-in first:
1. Open https://st-tools.sentimentrader.com/skills/mcp-server/CONNECT.md and follow the setup instructions.
2. Use OAuth sign-in first in my MCP client; do not ask me for credentials or a header.
3. If OAuth is unavailable, explain the Basic Auth fallback without asking me to expose credentials.
4. Let me know when the connection is complete, and suggest the most relevant next steps.
→ Configures MCP server at https://st-tools.sentimentrader.com/mcp-server/mcp
→ Uses OAuth sign-in first; only then considers the Basic Auth fallback
→ Verifies connection & available tools
https://sentimentrader.com/pricing#
# 2. After completing OAuth sign-in locally, tell your agent:
"Please verify my SentimenTrader MCP connection."
What is MCP?
Model Context Protocol (MCP) allows AI agents to connect to external tools and data sources. Once connected, your agent can access our full suite of backtesting and market analysis capabilities.
Supported clients
OAuth-first, same endpoint, no client secret:
- Z-Code —
~/.zcode/cli/config.json,type: http - DeepSeek — TUI, DSH preset, or MCP Center
- Kimi —
~/.kimi-code/mcp.json+/mcp-config login - Claude Code / Desktop
- ChatGPT connectors, Cursor, VS Code
Available Tools
25 canonical tools across 6 domains:
- Backtest execution & validation
- Market data & indicators
- Pattern matching & analysis
- Seasonality analysis
- Scanner picks & signals
- Reports & research
My Data API Dashboard
Browse the indicators your connected MCP account is permitted to read in a read-only dashboard.
Open it in one line: Open my SentimenTrader Data API Dashboard. MCP Apps hosts render the dashboard inline; every MCP tool works without it. The earlier phrase Open the SentimenTrader Indicator Workbench remains supported.
Open the Data API Dashboard guide →
Standalone local build: if it is already running on its default port and http://127.0.0.1:4174/_health identifies it, open the local dashboard →. Otherwise the guide covers the verified private runtime, installation, and recovery.
OAuth remains browser-based: the agent never handles credentials or logs in for you. Read the dashboard setup and safety rules →