Modelforge MCP Server

Most developer tooling work still happens through a UI a human drives. Modelforge MCP server moves it into the conversation instead. Bulge-tier financial model factory — live formulas, source-traced cells, 14 templates.

The short version

Bulge-tier Excel financial model factory for credit & structured finance. Every cell live-formulated. Every number traceable back to the source document page it came from.

The tools it exposes

The server publishes 3 tools. What each one is for:

• DCF — WACC band (3-25%), terminal growth ≤ GDP + 1%, EV vs market-cap deviation, terminal-value share, sensitivity-table monotonicity
• Three-statement — balance-sheet integrity, cash reconciliation, retained-earnings link
• NPL — cumulative recovery ≤ 100%, vintage staircase monotone

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: ANTHROPIC_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Modelforge's toolset — DCF, Three-statement, NPL — is a fair guide to whether it matches your workflow. It is maintained by Whatsonyourmind; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Modelforge's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.