Finance Toolkit
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Descripción del creador (original en inglés)
AI trading journal: your agent logs trades from chart screenshots and checks your own rules.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
JOURNAL_DATA_DIRNecesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"agent-trading-journal": {
"command": "npx",
"args": [
"-y",
"agent-trading-journal"
],
"env": {
"JOURNAL_DATA_DIR": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add agent-trading-journal --env JOURNAL_DATA_DIR=your-value -- npx -y agent-trading-journalCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"agent-trading-journal": {
"command": "npx",
"args": [
"-y",
"agent-trading-journal"
],
"env": {
"JOURNAL_DATA_DIR": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"agent-trading-journal": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agent-trading-journal"
],
"env": {
"JOURNAL_DATA_DIR": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
JOURNAL_DATA_DIR envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub smizxe, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.0) llegó al registro el mes pasado.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Finance Toolkit, SolidInvoice, Korea Tax Calculator
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Works with: Claude Code · Codex CLI · Claude Desktop · Cursor · Windsurf · any MCP client — Markets: forex, futures, stocks, crypto — Imports: MetaTrader 4/5, TradingView, IBKR, NinjaTrader, Tradovate and more
A trading journal your AI agent writes for you. Paste a chart screenshot into Claude Code, Codex or any MCP client. The agent reads it, fills in *your* strategy's fields, checks the trade against *your* rules, logs it, and attaches the image. A local dashboard shows what's working.
No forms, no LLM API key, no account. Everything stays on your machine in one SQLite file.
Dashboard with generated demo data (npx agent-trading-journal demo). Not a real account.
Most "AI trading journals" are a web form plus a chatbot that reads your numbers afterwards. Two problems follow:
Here the agent is the data-entry clerk, and the journal is shaped by an onboarding interview about how *you* trade:
| Typical AI journal | Agent Trading Journal | |
|---|---|---|
| Who enters trades | You, in a form | Your agent, from screenshots (or a broker statement) |
| How AI connects | The app calls an LLM with your API key | MCP: your agent (Claude Code / Codex / …) *is* the AI |
| What is measured | Fixed fields + free tags | Fields and a rule checklist defined for your strategy |
| Rules | Notes | Each rule is pass/fail per trade → "E[R] when followed vs broken" |
| Skipped setups | Not tracked | Logged and reviewed (was staying out right?) |
| Risk limits | Rarely | Prop-firm style guard: daily loss, max drawdown, trades/day, loss streak |
1. Connect it to your agent. Requires Node.js 22+.
Claude Code:
claude mcp add journal -- npx -y agent-trading-journal
Codex CLI (~/.codex/config.toml):
[mcp_servers.journal]
command = "npx" args = ["-y", "agent-trading-journal"]
Claude Desktop, Cursor, or any other MCP client: add a stdio server with command npx and args ["-y", "agent-trading-journal"]. Run npx agent-trading-journal setup to print all the snippets.
2. Tell your agent: *"Set up my trading journal."*
It interviews you in your language: markets, risk rules, how you find bias, setups, entries, stops and targets, and when you don't trade. From your answers it proposes fields (what to measure on every trade) and rules (your entry checklist). You confirm, and it saves them. See docs/ONBOARDING.md for the full script.
3. Trade or backtest as usual. Paste screenshots and say *"log this"*. Ask for *"weekly review"* or *"pre-session check"*. Say *"open the dashboard"* to see it at http://localhost:3777.
Just looking? npx agent-trading-journal demo fills a separate demo journal and opens the dashboard.
| Area | Tools |
|---|---|
| Setup | get_setup_status, get_onboarding_guide, set_profile, list_presets, import_preset, upsert_strategy, get_strategy, list_strategies, export_strategy |
| Accounts & risk | upsert_account, list_accounts, check_risk |
| Journal | start_session, list_sessions, log_trade, update_trade, delete_trade, query_trades, get_trade, add_screenshot |
| Lessons | add_lesson, update_lesson, delete_lesson, list_lessons |
| Analysis | get_stats, run_sql_readonly, export_review (Markdown, Obsidian-friendly) |
| Import | import_statement: MetaTrader 4/5, TradingView, IBKR, ThinkorSwim, NinjaTrader, Tradovate, TopstepX, Webull, DAS, TradeZella, Tradervue, generic CSV |
| Dashboard | start_dashboard, stop_dashboard, dashboard_status |
MCP prompts (slash commands in clients that support them): onboarding, log_trade_from_screenshot, weekly_review, pre_session_check. The same workflows are available through the get_workflow tool for clients without prompt support.
enum, bool, number, text). Every non-text field gets its own breakdown chart.must or should. Rule adherence compares expectancy when all must-rules were followed against when at least one was broken.presets/ has a *starter* template (for traders without a written strategy), a trend pullback and an opening-range breakout. They're starting points to edit, not recommendations.| Env var | Default | Purpose |
|---|---|---|
JOURNAL_DATA_DIR | ~/.agent-trading-journal | folder with journal.db + screenshots/ |
JOURNAL_DB, JOURNAL_SCREENSHOTS | inside the data dir | override either path |
JOURNAL_PORT | 3777 | dashboard port (binds to 127.0.0.1 only) |
JOURNAL_WEB | unset | 1 = start the dashboard together with the MCP server |
JOURNAL_LOCALES_DIR | /locales | extra dashboard languages as .json (docs/locales.md) |
Back up by copying the data dir. run_sql_readonly and the SQLite file are yours to query.
agent-trading-journal [mcp] MCP server on stdio (what MCP clients run)
agent-trading-journal dashboard dashboard at http://localhost:3777 agent-trading-journal demo demo data in a separate dir + dashboard agent-trading-journal import --account [--strategy ] [--dry-run] agent-trading-journal setup config snippets for Claude Code / Claude Desktop / Codex
This is a journaling and analysis tool. It does not place trades, connect to brokers for execution, or give financial advice. Leveraged trading is high-risk. The agent's chart reading can be wrong: every logged value is visible and editable, and rule checks show which ones failed and why.
No. The journal is an MCP server; the AI is the agent you already use (Claude Code, Codex, Claude Desktop, Cursor…). The journal itself never calls an LLM.
Everything is in one local SQLite file plus a screenshots folder (~/.agent-trading-journal by default). The dashboard binds to 127.0.0.1. Nothing is uploaded anywhere by the journal.
That's the point. The onboarding interview turns *your* plan into custom fields and a rule checklist. Presets are only starting points. SMC/ICT, price action, supply & demand, indicators, options: anything you can describe works.
Yes: import_statement (or agent-trading-journal import --account ) reads MT4/MT5 statements, TradingView paper/strategy exports, IBKR, ThinkorSwim, NinjaTrader, Tradovate, TopstepX, Webull, DAS, TradeZella and Tradervue exports. Your agent can then add screenshots and rule checks to the imported trades.
Yes. Sessions are backtest, forward or live. Accounts can carry prop-firm limits (daily loss, max drawdown, trades per day, loss streak), and check_risk warns before you hit them.
No. It only records and analyses. You make every trading decision.
MIT © 2026 smizxe.
Statement parsing and round-trip reconstruction use @luxalgo/journal-importers and @luxalgo/journal-core (MIT) from LuxAlgo's Trade Journal. The Edge Score is adapted from their open formula. This project is not affiliated with or endorsed by LuxAlgo.