Finstracker
Log in Get started
Documentation

Build on Finstracker.

Pull your card data over REST, or hand it to an LLM through MCP. Same JWT works for both, so there's nothing new to learn on the auth side.

New here?

Getting started

A visual walk-through of the app. Add a card, check off perks, save offers, and watch the dashboard chart fill in. No code required.

Take the 5-minute tour →

For developers & tinkerers

For LLM agents

MCP server

Connect Claude Desktop, agent SDKs, or any Model Context Protocol client to read your wallet, recommend cards, and log activity through natural language.

 For Claude users

Claude Skill

Drop two files into ~/.claude/skills/ and Claude can list your perks, mark credits as used, and log transactions in plain English. Doubles as a bash CLI.

 For Chrome users

Chrome extension

Install Fins Sync in five minutes. One click on a card opens your issuer portal, scrapes the points balance, and posts the delta back to your tracker.

 For developers

REST API

Full JSON API behind the Finstracker web app: cards, perks, offers, transactions, billing, and waitlist endpoints with a single uniform envelope.

What can I build?

  • "What card should I use at Target right now?" Hook MCP into Claude and ask. Finstracker checks your active Chase/Amex/BoA offers and ranks your wallet.
  • Monthly perk reminders in your own tools. Poll /api/perks?status=open from a cron job and pipe results to Slack, email, or a custom dashboard.
  • Bring-your-own analytics. Export every transaction via /api/transactions and run your own charts. No paywall on read endpoints during trial.
  • Custom card-onboarding flows. POST a card with cardKey and let the catalog auto-seed perks and offers, so your user never sees an empty state.

Authentication

Both surfaces use the same JWT bearer token. POST to /api/auth/login with { username, password }, read data.token, then send Authorization: Bearer <token> on every request. Tokens are valid for 7 days. One token, both APIs.

Status

The REST API powers the production web app and is considered stable. The MCP server is in beta, so tool input schemas and response shapes may still change as I learn how people actually use it. Anything that breaks will be noted in the changelog.