How to connect an AI agent to TraderBuddy over MCP
Connect Claude Code, Cursor or any MCP client to TraderBuddy in three steps: a personal access token, one command, a check. What the agent can do, and what it never can.
Engineering notes, the homelab and the tools I build.
Connect Claude Code, Cursor or any MCP client to TraderBuddy in three steps: a personal access token, one command, a check. What the agent can do, and what it never can.
How the site is served from a homelab: R2 releases, two pointers, what happens when things fail, and the failover Worker that is designed but not built yet.
What TraderBuddy is made of, and the constraints that shaped it: one WebSocket, thirty symbols, SIP versus IEX, and alerts that need previous state.
A self-hosted terminal for the US market: a watchlist home, server-side indicators, after-close alerts, a screener, SEC financials, news with an AI read, an AI research assistant and a manual portfolio. It never trades.
A thirty-second animated tour of TraderBuddy: chart, after-close alert, scanner, SEC financials and portfolio. It tracks and alerts. It never trades.
A headless CMS, a static Astro build, and nginx pods that keep serving even when the CMS is down. The reasoning and the trade-offs.