Price alerts and Pine Script signals for AI agents

Three ways in, same alerts underneath

Read prices and alerts from your agent, manage alerts from your terminal or backend.

How it works

Four integration paths, same alerting engine underneath.

# mkt-alerts ships its OWN stdio MCP server — READ/WRITE.
# Add to your MCP client config (Claude Desktop, Claude Code, Cursor):
{
  "mcpServers": {
    "mkt-alerts": {
      "command": "npx",
      "args": ["-y", "github:dzianisv/mkt-alerts", "mcp"]
    }
  }
}

# Tools (manage alerts, not just read):
#   list_alerts()
#   add_alert(...)
#   remove_alert(id)

# ── Optional companion (third-party, read-only) ──────────────
# The 'mkt' Go binary (github.com/stxkxs/mkt) exposes a separate
# READ-ONLY MCP with market-data tools. Install it on PATH first:
#   get_quote  query_history  get_alerts  get_portfolio
# {
#   "mcpServers": { "mkt": { "command": "mkt", "args": ["mcp"] } }
# }

Pine Script v5 alerts

Write real ta.sma/ta.rsi/custom Pine Script v5 logic. It runs on your own checker via an isolated PineTS subprocess — not on TradingView's servers, and not against your alert plan's quota. Evaluated every ~15 minutes.

# golden-cross.pine — plot a "signal" series
//@version=5
indicator("golden cross")
plot(ta.sma(close, 20) - ta.sma(close, 50), "signal")

# Arm it — runs SERVER-SIDE in an isolated PineTS subprocess,
# evaluated every ~15 minutes. Never on TradingView's servers,
# never against your alert plan's quota.
npx -y github:dzianisv/mkt-alerts add \
  --symbol BTC-USD \
  --pine golden-cross.pine \
  --signal signal \
  --fire-on cross_up \
  --reason "SMA20 crossing above SMA50 confirms trend flip" \
  --channel email:you@example.com

--signal signal names which plot() series to read (default "signal"). --fire-on cross_up is edge-triggered — fires when the signal crosses 0 upward. truthyis state-based — fires on every check while the signal is currently positive (e.g. "while oversold").

Schedule alerts with Hermes (or any cron)

Hermes is a scheduled-prompt agent — not a separate mkt-alerts plugin. It just runs the same CLI or HTTP call a human would, on a schedule. Two patterns work today.

# Pattern A — shell the CLI on a schedule.
# Requires ~/.config/mkt-watch/auth.json present on the runner.
npx -y github:dzianisv/mkt-alerts add \
  --symbol BTC-USD --condition below --value 90000 \
  --reason "reclaim entry" \
  --data-source "200wMA $62,640 from TradingView 210 weekly bars" \
  --channel ntfy:my-topic

# Pattern B — POST the HTTP API directly with a bearer token.
curl -sS -X POST "$MKT_API_URL/alerts" \
  -H "Authorization: Bearer $MKT_TOKEN" -H "Content-Type: application/json" \
  -d '{"symbol":"BTC-USD","desk":"crypto","reasoning":"reclaim entry [data: 200wMA $62,640, 210w TradingView]","conditions":[{"condition":"below","value":90000}]}'

Auth is read from ~/.config/mkt-watch/auth.json (apiUrl + token). There is no env-var override for the CLI's auth today, so a Hermes runner needs that file present — or use Pattern B with an explicit bearer token.

Ready to give your agents market alerts?