AI 트레이딩 어시스턴트로서의 Claude: SharpTrader를 위한 음성 제어, 24시간 모니터링, 컨트롤 센터 11월 9, 2026 – Posted in: Arbitrage Software, Forex trading

# SharpTrader MCP — Automated Monitoring & Interactive Reporting Center

You are already connected to my SharpTrader trading platform running on a VPS through the SharpTrader MCP Server.

I want you to create a comprehensive automated monitoring, risk control, execution analysis, and reporting system using **Claude, the existing MCP connection, and Claude Artifacts**.

## IMPORTANT — Implementation Restrictions

For this initial version:

- Do NOT install any software on the VPS.
- Do NOT create Python monitoring services.
- Do NOT deploy a web dashboard to the VPS.
- Do NOT configure cron, systemd, Windows Task Scheduler, or VPS background processes.
- Do NOT modify the SharpTrader MCP Server.
- Do NOT create additional infrastructure.
- Do NOT open or close trading positions automatically.

Use the existing SharpTrader MCP tools and Claude's native scheduling capabilities, if available.

Your responsibility is to create working recurring tasks wherever supported and organize all results into a single interactive Claude Artifact.

If native scheduling is unavailable, do not claim the tasks are active. Instead, implement the monitoring and reporting workflows that can be run on demand and clearly identify the scheduling limitation.

# 1. Discover SharpTrader MCP Capabilities

First, inspect all available SharpTrader MCP tools.

Identify which tools support:

- Listing strategies and their running/stopped status
- Retrieving strategy settings
- Quote and Trade session monitoring
- Reading active positions and pending orders
- Retrieving historical trades and trading cycles
- Reading strategy logs
- Checking execution latency and slippage
- Retrieving account equity and PnL
- Accessing economic news events
- Starting and stopping strategies
- Retrieving MCP server status and error information

Map each required monitoring function to the actual available MCP tool.

Do not invent MCP commands or unsupported features.

# 2. Recurring Monitoring Tasks

Create the following recurring tasks using Claude's available scheduling functionality.

Use the America/New_York timezone and account for daylight saving time.

## Task 1 — Hourly Health Monitoring

**Schedule:** Every hour during Forex market hours.

Check:

1. SharpTrader MCP connectivity.
2. Quote session connectivity.
3. Trade session connectivity.
4. Running and stopped strategies.
5. Error counters and new errors.
6. Unexpected strategy stops.
7. Stale market data, where detectable.
8. Current open positions.

Assign HEALTHY, WARNING, CRITICAL, or UNKNOWN status.

Record the timestamp and results.

## Task 2 — Orphaned Position Detection

**Schedule:** Every hour during trading hours.

Identify positions or pending orders belonging to stopped strategies.

Display:

- Strategy
- Broker/session
- Instrument
- Order ID
- Direction
- Volume
- Floating PnL
- Protective orders
- Strategy status

Immediately flag detected orphaned positions as CRITICAL.

Never automatically close positions.

## Task 3 — Drawdown Monitoring

**Schedule:** Every 15 minutes during trading hours, if supported.

Default thresholds:

- Warning: 3%
- Critical: 5%

Calculate drawdown using reliable strategy-level equity or an explicitly documented alternative.

Use a consistent baseline and clearly state the calculation method.

At the critical threshold:

- Generate a CRITICAL alert.
- Identify the affected strategy.
- Explain the current risk.
- Recommend suspending new entries.

Do not automatically stop a strategy in this initial version.

## Task 4 — Execution Quality Watchdog

**Schedule:** Every 15 minutes during trading hours.

Analyze new execution logs.

Default thresholds:

- Adverse slippage: more than 50 points
- Execution latency: more than 120 milliseconds
- Repeated bad executions: 3 within 60 minutes

Detect abnormal executions.

For each event, record:

- Strategy
- Broker
- Instrument
- Order ID
- Timestamp
- Expected price
- Actual price
- Slippage
- Execution latency
- Entry or exit

Highlight repeated execution problems and identify brokers with deteriorating performance.

Do not automatically stop strategies.

# 3. Daily Performance Reports

## Task 5 — Daily Trading Digest

**Schedule:** Monday–Friday at 5:10 PM New York time.

Generate a report for every strategy containing:

- Strategy name
- Broker and session
- Instruments
- Trading cycles
- Winning and losing cycles
- Win rate
- Average win
- Average loss
- Gross profit and loss
- Net PnL
- Profit factor
- Maximum drawdown
- Average execution latency
- Worst adverse slippage
- Number of execution errors
- Session uptime
- Open positions and floating PnL

Include consolidated results for all strategies.

Calculate metrics from real MCP data.

Clearly distinguish trading cycles from individual trades and fills.

## Task 6 — Nightly Settings Snapshot

**Schedule:** Daily at 11:55 PM New York time.

Retrieve:

- All strategies
- Strategy parameters
- Instrument assignments
- Broker/session mappings
- Risk settings
- Lot sizes
- Execution parameters

Compare the current configuration with previous snapshots.

Highlight added, removed, and modified parameters.

Use the available Claude persistence features, where supported, to preserve history.

Never include passwords, API keys, or private credentials.

# 4. Weekly Execution Analysis

## Task 7 — Weekly Latency Report

**Schedule:** Monday at 8:00 AM New York time.

Generate:

- Average execution latency
- p95 execution latency
- Maximum execution latency
- Average adverse slippage
- Worst adverse slippage
- Broker-by-broker comparison
- Instrument-level analysis
- Strategy-level execution quality
- Weekly trends
- Execution failures
- Session disconnects

Include charts showing performance deterioration.

# 5. News Calendar Monitoring

## Task 8 — Daily News Calendar Review

**Schedule:** Every day at 7:00 AM New York time.

Use available SharpTrader MCP news calendar tools.

Identify:

- Upcoming high-impact events
- Affected currencies
- Relevant trading instruments
- Strategies potentially affected
- Event timestamps

Default protection recommendation:

- 15 minutes before the event
- 15 minutes after the event

Show which strategies should avoid new entries.

For this initial version, **do not automatically stop strategies or change their settings**.

Generate alerts and recommendations only.

# 6. Weekend Trading Monitoring

## Task 9 — Friday Weekend Review

**Schedule:** Friday at 4:45 PM New York time.

Check:

- Active strategies
- Open positions
- Pending orders
- Floating PnL
- Broker connectivity
- Strategies configured for weekend trading

Generate a weekend risk report.

Identify strategies that should potentially be stopped.

Do not automatically stop them.

## Task 10 — Sunday Market Reopening Review

**Schedule:** Sunday at 5:05 PM New York time.

Check:

- MCP connectivity
- Quote session connectivity
- Trade session connectivity
- Market data freshness
- Existing open positions
- Orphaned orders
- Strategy statuses

Identify which strategies are ready for trading.

Do not automatically start strategies.

# 7. MCP Server Weekly Audit

## Task 11 — MCP Server Health Report

**Schedule:** Monday at 8:15 AM New York time.

Use available MCP diagnostic tools to check:

- Server connectivity
- Response time
- Failed MCP calls
- Reported exceptions
- Available error logs
- TLS certificate expiry, if exposed
- Service restart information, if exposed

If infrastructure-level diagnostics are unavailable through MCP, clearly mark them as unavailable.

Do not attempt to access the VPS operating system through unapproved methods.

# 8. Create One Unified Claude Artifact

Create an interactive Claude Artifact named:

**SharpTrader — Monitoring & Analytics Control Center**

The Artifact must contain the following tabs.

## Tab 1 — Overview

Display the current overall state:

- MCP server status
- Connected sessions
- Active strategies
- Stopped strategies
- Open positions
- Net PnL
- Drawdown
- Active alerts
- Upcoming news

Use color-coded indicators.

## Tab 2 — Monitoring

Display:

- Quote and Trade session statuses
- Strategy health
- Error counters
- Orphaned positions
- Drawdown monitoring
- Historical monitoring results

## Tab 3 — Execution Quality

Display:

- Execution latency
- Slippage analysis
- Worst fills
- Bad execution events
- Broker comparisons
- Historical execution trends

Use interactive charts.

## Tab 4 — Performance

Display:

- Daily strategy reports
- Portfolio-level performance
- Win rates
- Trading cycles
- Profit factor
- Daily PnL charts
- Historical performance comparisons

## Tab 5 — Settings History

Display:

- Current strategy settings
- Previous settings snapshots
- Configuration changes
- Instrument changes
- Broker/session changes

Show old versus new parameter values.

## Tab 6 — News & Calendar

Display:

- Upcoming high-impact events
- Affected instruments
- Affected strategies
- Recommended trading blackout periods
- Weekend monitoring results
- Next scheduled reviews

## Tab 7 — MCP Health

Display:

- MCP connection status
- Response time
- Error history
- Available infrastructure diagnostics
- Certificate expiration information when available

## Tab 8 — Alerts

Display:

- Active critical alerts
- Warning alerts
- Historical incidents
- Affected strategies
- Alert timestamps
- Alert descriptions
- Recommended actions

## Tab 9 — Scheduled Tasks

Display a complete automation control panel containing:

- Task name
- Schedule
- Status
- Last execution
- Next scheduled execution
- Last result
- Error information
- Whether the task is actually registered with a scheduler

Clearly distinguish ACTIVE, MANUAL ONLY, FAILED, and UNSUPPORTED tasks.

# 9. Artifact UI Requirements

Create a professional dark-themed trading dashboard.

Requirements:

- Responsive layout
- Interactive navigation tabs
- Sortable tables
- Strategy filters
- Broker filters
- Instrument filters
- Date-range selection
- Interactive charts
- Historical comparisons
- Clear alert severity indicators
- Last updated timestamps
- Data freshness indicators

Use real SharpTrader MCP data only.

Do not generate fictional performance metrics or sample trading results.

If a required metric is unavailable, display N/A and explain why.

The Artifact must never falsely indicate that monitoring is live or continuously updating when it is only displaying the latest available snapshot.

# 10. Scheduling and Persistence

Use Claude's native recurring task functionality if it is available in this environment.

Verify:

1. Whether scheduled tasks can call SharpTrader MCP tools.
2. Whether they can execute when the Claude chat is closed.
3. Whether task execution history persists.
4. Whether monitoring results can be saved between executions.
5. Whether scheduled task outputs can be used to refresh the Artifact.

If any of these capabilities are unavailable, clearly explain the limitation.

Do not substitute temporary chat reminders for actual recurring monitoring.

Do not claim that an Artifact itself performs background monitoring.

# 11. Initial Execution

After discovering the MCP tools:

1. Retrieve all SharpTrader strategies.
2. Retrieve all current trading sessions.
3. Check current connectivity.
4. Retrieve open positions.
5. Analyze available execution logs.
6. Identify current warnings.
7. Generate the first performance summary using available data.
8. Build the interactive Artifact.
9. Create and register recurring tasks wherever supported.
10. Verify actual scheduling status.

# 12. Final Result

At completion, provide:

**A. SharpTrader Monitoring & Analytics Artifact**

A complete interactive dashboard with all nine tabs.

**B. Recurring Tasks Status**

A table showing which tasks are successfully scheduled, which can only run manually, and which are unsupported.

**C. Current SharpTrader Status**

A summary based on actual MCP data.

**D. Limitations**

Explain which functions require capabilities that Claude or the existing SharpTrader MCP connection does not currently provide.

**Important: Do not stop after writing an implementation plan. Perform all supported actions now. Build the Artifact, retrieve real SharpTrader data, and register the available recurring tasks. Do not make any trading changes or deploy anything to the VPS.**