claude_prophet vs OpenProphet

By Jake Nesler. Both repos are open source.

claude_prophet and OpenProphet are both by Jake Nesler. They are not competitors — OpenProphet is the evolution of claude_prophet into a complete autonomous trading system.

Short Version

claude_prophet = the MCP server. The toolbox. 40+ trading tools for any MCP-compatible LLM to interact with markets via Alpaca.

OpenProphet = the full system. Integrates claude_prophet's MCP server with a web dashboard, autonomous heartbeat loop, multi-account sandboxes, agent personas, strategy templates, and Go trading backend.

Comparison

Feature                  claude_prophet              OpenProphet
─────────────────────────────────────────────────────────────────
MCP trading tools        40+ tools                   45+ tools (extended)
Go trading backend       Yes                         Yes (same codebase)
Autonomous heartbeat     No — manual use only        Yes — phased 6-interval loop
Web dashboard            No                          Yes — real-time SSE streaming
Multi-account            Single .env config          Multi-account sandboxes, hot-swap
Agent personas           4 Claude agents             Unlimited, configurable via dashboard
Strategy management      Single TRADING_RULES.md     Multiple strategies, assignable
Permission system        Basic                       Full enforcement layer
AI memory                Vector search (sqlite-vec)  Vector search (sqlite-vec)
LLM support              Claude Code only            Any LLM via OpenCode (294+ models)
License                  MIT                         CC BY-NC 4.0
Status                   Deprecated                  Active development

Why claude_prophet Was Deprecated

claude_prophet was an MCP server for interactive Claude Code sessions. You'd open Claude Code, the AI could call trading tools — but only while you were chatting. Nobody can sit in Claude Code 24/7.

OpenProphet wraps the MCP server in an autonomous agent loop. The heartbeat system wakes the AI on intervals that vary by market phase. The web dashboard streams everything. No human in the loop required.

The claude_prophet repo now redirects to OpenProphet. The MCP server code lives inside OpenProphet and receives all updates there.

What Stayed the Same

Same Go backend (Gin, port 4534)
Same Alpaca API integration for stocks and options
Same news aggregation (Google News, MarketWatch)
Same technical analysis (RSI, MACD, momentum)
Same AI news cleaning via Gemini
Same vector similarity search for trade memory
Same MCP tool interface (Node.js stdio server)

What OpenProphet Added

Autonomous heartbeat loop — six market phases, agent-adjustable intervals
Web dashboard — 8 tabs, real-time SSE streaming, mobile-first
Multi-account sandboxes — isolated Go backend + DB per Alpaca account
Agent orchestration — unlimited agents with different models, strategies, permissions
Permission enforcement — asset class gates, order value limits, daily loss circuit breakers, 0DTE blocking
Plugin system — Slack notifications for trades, errors, daily summaries
Session persistence — context maintained across heartbeats, saves ~2,000 tokens/beat
Any LLM — switched from Claude Code to OpenCode (294+ models)

Which Should You Use?

OpenProphet if you want an autonomous trading agent with a dashboard. This is the active project.

claude_prophet only if you want a minimal MCP server for interactive Claude Code sessions. It is deprecated and no longer updated.