OpenCoffer

OpenCoffer

Enables querying personal finance data including accounts, transactions, spending, holdings, net worth, and budgets from your self-hosted OpenCoffer instance. Supports natural language queries through any MCP-compatible client.

Category
Visit Server

README

<div align="center">

<img src="public/logo.png" alt="OpenCoffer" width="96" height="96" />

OpenCoffer

Self-hosted personal finance with bank sync, dashboards, and a BYO-LLM chat that actually reads your numbers.

License: MIT Next.js Postgres Docker MCP

Quick start · Features · MCP · Configuration · Security

</div>

<p align="center"> <img src="public/demo.gif" alt="OpenCoffer demo" width="720" /> </p>

OpenCoffer is read-only against your financial accounts. It syncs through SimpleFIN, stores everything in a Postgres database you own, encrypts sensitive tokens and model keys at rest, and lets you ask finance questions through the in-app chat or any MCP-compatible client. Bring any model you want — OpenAI, Anthropic, OpenRouter, Groq, Together, Ollama, Hermes, ChatGPT subscription auth, or any OpenAI-compatible endpoint.


Features

  • Bank & brokerage sync via SimpleFIN — one-token setup, encrypted access URLs.
  • Net worth, cash flow, spending, subscriptions, holdings, budgets, alerts, saved charts — all deterministic, all generated from your database.
  • Bring your own LLM — OpenAI, Anthropic, any OpenAI-compatible provider, ChatGPT subscription auth, local Ollama, or a self-hosted endpoint.
  • Persistent chat with finance tools — model picker, conversation history, category fixes, deterministic chart tools the LLM can call.
  • Background worker — automatic sync, categorization, insight refresh, and net-worth snapshots on a cron you control.
  • MCP server at /api/mcp exposing the same finance tools used by chat, so any MCP client (Claude Desktop, Hermes, custom agents) can query your data with a bearer token.
  • Docker Compose deployment with Postgres, web, worker, and optional Ollama.

Screenshots

<table> <tr> <td align="center"><img src="public/screenshots/overview.png" alt="Overview" width="320" /><br/><sub><b>Overview</b> — net worth, cash flow, intelligence</sub></td> <td align="center"><img src="public/screenshots/charts.png" alt="Charts" width="320" /><br/><sub><b>Charts</b> — deterministic, regenerated on sync</sub></td> <td align="center"><img src="public/screenshots/chat.png" alt="Chat" width="320" /><br/><sub><b>Chat</b> — BYO model, persistent history</sub></td> </tr> </table>

Quick start (Docker)

The fastest path — Postgres, web, and worker running in three commands.

# 1. Generate secrets
cp .env.example .env
echo "NEXTAUTH_SECRET=$(openssl rand -base64 32)" >> .env
echo "APP_ENCRYPTION_KEY=$(openssl rand -base64 32)" >> .env

# 2. Start Postgres, run migrations, then bring up the full stack
docker compose up -d postgres
docker compose run --rm web pnpm db:migrate
docker compose up -d --build

Open http://localhost:3000, create an account, then add a SimpleFIN setup token in Settings → Connections.

[!IMPORTANT] APP_ENCRYPTION_KEY encrypts your SimpleFIN access URLs and LLM API keys at rest. Back it up. Rotating it makes existing encrypted secrets unreadable.

Local development

Requirements: Node.js 22, pnpm (via Corepack), Postgres 16+.

corepack enable
pnpm install
cp .env.example .env.local

# Point DATABASE_URL at your local Postgres, then:
pnpm db:migrate
pnpm dev          # web on :3000
pnpm worker       # background sync + categorization (second terminal)

For production-mode testing (recommended for mobile / LAN testing — next dev compiles on demand and is slow over the network):

pnpm build
pnpm start
pnpm worker

Architecture

┌──────────────┐     ┌──────────────┐     ┌──────────────┐
│   Next.js    │     │  Postgres 16 │     │   Worker     │
│   (web)      │◄───►│  (drizzle)   │◄───►│   (cron)     │
│              │     │              │     │              │
│  /dashboard  │     │  accounts    │     │  • sync      │
│  /chat       │     │  txns        │     │  • categorize│
│  /settings   │     │  insights    │     │  • insights  │
│  /api/mcp ───┼──┐  │  snapshots   │     │  • snapshots │
└──────────────┘  │  │  budgets     │     └──────┬───────┘
                  │  │  chat_msgs   │            │
                  │  │  llm_creds*  │            │
                  │  │  mcp_tokens* │            ▼
                  │  └──────────────┘     ┌──────────────┐
                  │                       │  SimpleFIN   │
                  ▼                       │   bridge     │
         ┌─────────────────┐              └──────────────┘
         │   MCP client    │
         │  (Claude /      │     * encrypted with
         │   Hermes / etc) │       APP_ENCRYPTION_KEY
         └─────────────────┘

The worker is part of the release runtime, not optional dev tooling. It syncs SimpleFIN connections, categorizes new transactions with your chosen analysis model, refreshes AI insights, writes net-worth snapshots, and purges disconnected connections after their retention window.

Configuration

All configuration lives in .env (Docker) or .env.local (dev). See .env.example for the full list.

Variable Required Description
DATABASE_URL Yes Postgres connection string
NEXTAUTH_SECRET Yes Auth.js session secret — openssl rand -base64 32
NEXTAUTH_URL Yes Public URL of the web app
APP_ENCRYPTION_KEY Yes 32-byte base64 key for at-rest encryption of secrets
APP_URL Yes Used in MCP setup snippets shown in the UI
OPENCOFFER_SYNC_CRON No Worker sync cadence (default */30 * * * *)
OLLAMA_BASE_URL No Pre-seeded base URL when using the bundled Ollama profile

LLM setup

  1. Open Settings → Models.
  2. Add at least one credential. Any OpenAI-compatible endpoint works — provider, base URL, API key, model name.
  3. Mark one model as the analysis model. It's used for background categorization and generated insights. Chat lets you pick per-message.

To run Ollama inside the compose network:

docker compose --profile ollama up -d ollama

Then point the app at http://ollama:11434/v1 (inside Docker) or http://host.docker.internal:11434/v1 (host Ollama from a container).

Use your ChatGPT Plus/Pro subscription instead of an API key

OpenCoffer can talk to the same backend the official codex CLI uses, so a ChatGPT Plus/Pro/Business subscription works as a model credential — no extra OpenAI API spend.

  1. Install the official Codex CLI and sign in with your ChatGPT account:

    npm install -g @openai/codex
    codex login
    

    This opens a browser, completes the OAuth flow, and writes a token bundle to ~/.codex/auth.json.

  2. In OpenCoffer, go to Settings → Models → Add credential and pick ChatGPT Plus/Pro subscription as the provider.

  3. Paste the entire contents of ~/.codex/auth.json into the credential field and pick a model (e.g. one of the GPT-5.x options exposed via the codex backend). Leave the base URL blank — OpenCoffer defaults to https://chatgpt.com/backend-api/codex.

  4. Save. OpenCoffer encrypts the token bundle with APP_ENCRYPTION_KEY and automatically refreshes the access token against auth.openai.com when it's within 60 seconds of expiry. If a refresh ever fails (you signed out elsewhere, the refresh token rotated, etc.), re-run codex login and paste the new auth.json.

This works for both the in-app chat and the background analysis model (categorization, insights, snapshots). Same auth, same provider config.

SimpleFIN

OpenCoffer uses SimpleFIN for read-only bank and brokerage data. There are no app-wide credentials — each user pastes their own setup token in Settings → Connections. The token is claimed once; the resulting access URL is encrypted with APP_ENCRYPTION_KEY.

Disconnecting a connection marks it for purge after 30 days. Hard-delete removes it immediately.

MCP

OpenCoffer exposes its finance tools to MCP-compatible clients at /api/mcp.

# 1. Create a token in Settings → MCP
# 2. Wire it into your MCP client (Hermes example):

hermes mcp add opencoffer \
  --transport http \
  --url http://localhost:3000/api/mcp \
  --header "Authorization: Bearer oc_<your-token>"

Tool families available over MCP:

accounts            recent_transactions    transaction_search
spending_by_category  holdings             recurring_streams
upcoming_payments   net_worth              budgets
alerts              chart_data             category_fixes

The LLM writes the commentary; finance totals come from deterministic database-backed tools. No hallucinated balances.

Security

  • SimpleFIN access URLs and LLM API keys are encrypted at rest with APP_ENCRYPTION_KEY.
  • MCP bearer tokens are stored as hashes — you see them once at creation.
  • Dashboard and settings routes require Auth.js sessions; /api/mcp uses bearer auth instead of session cookies.
  • Keep NEXTAUTH_SECRET, APP_ENCRYPTION_KEY, .env, database backups, and SimpleFIN setup/access URLs private.

See SECURITY.md for the full policy and disclosure channel.

Operations

docker compose logs -f web
docker compose logs -f worker
docker compose run --rm web pnpm db:migrate    # apply new migrations
docker compose pull && docker compose up --build -d

Back up Postgres before upgrades:

docker compose exec postgres pg_dump -U opencoffer opencoffer > opencoffer.sql
docker compose exec -T postgres psql -U opencoffer opencoffer < opencoffer.sql

Demo GIF

The hero GIF lives at public/demo.gif. It's rendered from real app screenshots captured with fake demo data — never real account data.

# Remotion source (preferred — produces the higher-res GIF)
cd demo/remotion
pnpm install
pnpm run render:gif      # writes ../../public/demo.gif

# Deterministic Python fallback (no Remotion / Chromium required)
python3 scripts/generate-demo-gif.py

Contributing

PRs welcome. See CONTRIBUTING.md for the local setup and the checks that should pass before opening a PR:

npx --no-install tsc --noEmit
pnpm lint
pnpm build

License

MIT © OpenCoffer contributors.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured