Credit Karma MCP
Connect Claude to your Credit Karma account to sync and analyze transactions, spending, account balances, and run read-only SQL locally.
Verify credentials and upstream Credit Karma reachability with a healthcheck.
Store or forget a Credit Karma session for automatic token refresh.
Sync transactions into local SQLite, incrementally or as a resumable full backfill.
List and filter transactions by date, account, category, merchant, amount, or status.
Fetch recent transactions and spending summaries by category, merchant, or account.
View current account balances, including available credit, limits, as-of times, and stale flags; optionally refresh live.
Run read-only SQL SELECT queries against the local transactions database with row limits.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Credit Karma MCP What did I spend on food last month?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Credit Karma MCP
A Model Context Protocol server that connects Claude to Credit Karma, giving you natural-language access to your transactions, spending patterns, and account summaries.
AI-developed project. This codebase was entirely built and is actively maintained by Claude Code. No human has audited the implementation. Review all code and tool permissions before use.
What you can do
Ask Claude things like:
"Sync my latest transactions"
"What did I spend on food last month?"
"Show me my top merchants this year"
"How much did I spend in March compared to February?"
"Which accounts have the most activity?"
"What are my account balances?"
"Run a SQL query against my transactions"
Related MCP server: Yodlee MCP Server
Requirements
Node.js 18 or later
A Credit Karma account
For the no-env-var path: the ContextMint Bridge browser extension (the renamed fetchproxy extension, same maintainer — see Option A below for how to verify it)
Acknowledgement of Terms
By using this MCP server, you acknowledge and agree to the following:
1. This server accesses your own Credit Karma account. Every request is dispatched through your own signed-in browser tab via the ContextMint Bridge extension. You are the one logged in. It does not — and cannot — access anyone else's account.
2. Credit Karma's Terms govern your use of this server, just as they govern your direct use of creditkarma.com. The clauses most relevant here:
You must not sell, transfer, or assign your account to anyone else… you may not allow anyone else to log into our Services as you.
CK does contemplate third-party data retrieval at the user's direction (Section 3.7). There is no explicit anti-scraping clause in the membership agreement; Section 4.1 restricts copying or distributing CK content without express prior written consent.
You are agreeing to those terms — read by the maintainer 2026-05-23 — every time you invoke a tool in this server. Critically: this server runs as you, not as a third party logging in on your behalf. You direct the tool.
3. Personal, non-commercial use only. This project is not affiliated with, endorsed by, sponsored by, or in partnership with Intuit, Credit Karma, or any financial institution. It is a personal automation tool that reads your transaction history, spending categories, and account snapshots — the same data Credit Karma already shows you in their app. Do not use it on someone else's account, do not redistribute their content, and do not use it to make trading or lending decisions on behalf of others.
4. This server may break. Credit Karma rotates its internal endpoints; what works today may 404 tomorrow. This is the nature of unofficial integrations.
5. You accept full responsibility for any consequences of using this server in connection with your Credit Karma account — rate limiting, account warnings, suspension, or any enforcement action Intuit takes. If Credit Karma objects to your use, stop using this server. Do not commit your .env to git — your CK session/auth artifacts are credentials, and the Membership Agreement holds you responsible for their confidentiality.
This section is the maintainer's good-faith summary of the terms — it is not legal advice and does not modify or supersede Credit Karma's actual Membership Agreement.
Installation
1. Clone and build
git clone https://github.com/chrischall/creditkarma-mcp.git
cd creditkarma-mcp
npm install
npm run build2. Configure
cp .env.example .env
# See "Authentication" below to get your CK_COOKIES value3. Add to Claude
Claude Code — add to .mcp.json in your project:
{
"mcpServers": {
"creditkarma": {
"command": "node",
"args": ["/absolute/path/to/creditkarma-mcp/dist/index.js"]
}
}
}Claude Desktop — edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"creditkarma": {
"command": "node",
"args": ["/absolute/path/to/creditkarma-mcp/dist/index.js"],
"env": {
"CK_COOKIES": "CKTRKID=...; CKAT=eyJ...%3BeyJ...; ..."
}
}
}
}4. Restart Claude
Fully quit and relaunch. Then ask: "Sync my Credit Karma transactions".
Authentication
Credit Karma uses short-lived JWTs. This server handles automatic token refresh — you only need to set up credentials once (or when your session expires).
creditkarma-mcp tries three auth paths in priority order; whichever succeeds first is used. Existing setups keep working unchanged.
CK_COOKIESenv var (legacy). Set the full Cookie header in your Claude Desktop config or.env. This is the path shown in the config above.Saved session from
ck_set_session. The tool saves the Cookie header to~/.creditkarma-mcp/session(mode 0600; override the path withCK_SESSION_PATH), which the server reads back directly on every start — including from the.mcpbbundle. Paths 1 and 2 are both local: whichever holds the fresher refresh token wins.Browser fallback via ContextMint Bridge (no env vars needed — easiest onboarding). Used when neither is configured, or when the local session has expired or Credit Karma has rejected its refresh token: the server reads
CKAT+CKTRKIDcookies from your already-signed-increditkarma.comtab via the ContextMint Bridge browser extension. After that read, all CK API calls go directly from Node — the extension is not in the request hot path. Install ContextMint Bridge (see Option A below), sign into creditkarma.com, and the MCP just works.
Set CK_DISABLE_FETCHPROXY=1 to opt out of the fallback (turns missing credentials into a hard error — useful in headless CI).
Getting your credentials (env-var path)
Option A — ContextMint Bridge extension (recommended)
Install ContextMint Bridge from its releases page. Chrome: download the chrome zip, unzip it, and load it unpacked at
chrome://extensions(Developer mode → Load unpacked). Safari: it ships inside the ContextMint app, which has no public download link yet — use Chrome, or Option B, for now.ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README (Extension) points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself (
npm run build), or check a release zip against the.sha256file published beside it before loading it:shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256Sign into creditkarma.com in that browser.
Leave
CK_COOKIESunset in your Claude config.
The MCP reads the HttpOnly CKAT + CKTRKID cookies via chrome.cookies.get on the first tool call, then operates direct-to-API from Node. To re-auth (e.g. after Credit Karma signs you out), just sign back in to creditkarma.com. If the bridge in your browser can't read cookies, the MCP says so — use Chrome, or Option B.
Option B — manual (DevTools)
Log in to creditkarma.com in Chrome
Open DevTools → Network → click any request to creditkarma.com → Request Headers
Right-click the
cookieheader → Copy value
Then either paste into CK_COOKIES in your Claude config / .env, or call ck_set_session from within Claude with the Cookie header value.
The server extracts the access and refresh JWTs from the CKAT cookie inside the header and refreshes the access token automatically as needed.
Session expiry
Access token: ~15 minutes (auto-refreshed transparently)
Refresh token: ~8 hours
When the refresh token expires:
fetchproxy path: sign back into creditkarma.com — the MCP re-reads fresh cookies on the next tool call.
env-var path: grab a fresh Cookie header from DevTools and update
CK_COOKIES(or callck_set_session).
Available tools
Tool | What it does |
| Store credentials from your browser Cookie header (auto-extracts JWTs from the CKAT cookie) |
| Delete the saved-session file and clear in-memory credentials (local only; synced transactions are kept) |
| Sync transactions into the local SQLite database, then refresh account balances |
| Balance of every account: institution, type, last 4, current balance, available credit and credit limit (cards), as-of time and a |
| List transactions with filters (date, account, category, merchant, amount); |
| Fetch the N most recent transactions |
| Spending totals grouped by category |
| Spending totals grouped by merchant |
| Transaction counts and totals by account |
| Run a read-only SQL query against the local database (returns at most |
How it works
Transactions are synced from Credit Karma's GraphQL API into a local SQLite database (default: ~/.creditkarma-mcp/transactions.db). All query tools run against this local database — fast, offline-capable, and queryable with SQL.
Sync strategy: incremental by default (fetches since last sync date with a 30-day overlap for updates). Use force_full: true to walk the whole history with no date cutoff — it starts from the beginning, except that a repeated force_full continues a backfill that paused on max_pages. After a sync that failed or stopped on a stuck cursor, force_full restarts from page 1 (a plain call retries from the saved cursor).
Account balances: each sync also refreshes balances once, from two sources (a failure in either is reported in the result's balances, never thrown, and the transactions still sync):
Linked accounts — every type, including credit cards and loans — come from the account aggregator behind Credit Karma's Manage accounts page (Intuit's account vault, reached with a token Credit Karma issues). Each account is matched to your transaction account by its account id, and its as-of time is that account's own last refresh. Card rows include the credit limit; available credit is calculated as limit minus balance.
Credit cards and loans also come from your credit report (TransUnion by default; set
CK_CREDIT_BUREAU=equifaxto switch). These are as of the bureau's last report, usually 2–5 weeks old, with credit limits but no last 4. Closed accounts are dropped. When a credit-report account is clearly the same as a linked one (same lender, same credit limit, similar balance, the linked balance is at least as recent — and no other account fits), it is hidden as a duplicate; passinclude_matched: trueto see it. Doubtful pairs are never hidden.
Balances follow the transaction sign convention: assets are positive, money owed (card balances, loans) is negative; credit_limit and available_balance are positive. stale is true when balance_as_of is more than 7 days old for linked accounts, or 35 days for credit-report accounts.
Auto-refresh: if the access token has expired, the server automatically refreshes it before syncing. If the refresh token has also expired, it throws an error asking you to re-authenticate.
Database schema
transactions (id, date, description, status, amount, account_id, category_id, merchant_id, raw_json)
accounts (id, name, type, provider_name, display, last4, account_urn,
current_balance, available_balance, credit_limit,
balance_as_of, balances_synced_at, balance_source, matched_account_id)
account_aliases (alias, account_id)
categories (id, name, type)
merchants (id, name)
sync_state (key, value)Configuration
Env var | Description | Default |
| Full Cookie header from a signed-in creditkarma.com request | (unset — falls back to fetchproxy) |
| Set to | (unset) |
| Path to SQLite database file |
|
| Credit report used for card and loan balances: |
|
| Set to | (unset) |
Troubleshooting
"CK auth: set CK_COOKIES, or call the ck_set_session MCP tool, or install the ContextMint Bridge extension…" — neither auth path is configured. Either fill in CK_COOKIES in your Claude config, or install ContextMint Bridge and sign into creditkarma.com in your browser.
"TOKEN_EXPIRED" — your refresh token has expired. Sign back into creditkarma.com (ContextMint Bridge path) or grab a fresh Cookie header from DevTools and update CK_COOKIES / call ck_set_session.
ck_healthcheck fails with a fresh sign-in — read its steps / failed_step: they report credential lookup, token validity, refresh and probe separately. A refresh failure reported as blocked at its CDN/WAF (Akamai) means the request never reached Credit Karma, and signing in won't help. A session rejected refresh means Credit Karma ended the session, even when the token looks new: an idle tab gets signed out. Sign in again. If a sign-in made moments ago fails the same way, restart with CK_DEBUG=1 and compare against docs/refresh-ground-truth.md.
"fetchproxy fallback failed" — the env-var path wasn't configured and the extension couldn't be reached. Confirm ContextMint Bridge is installed, you're signed into Credit Karma, and that it's running (open the extension popup). To disable the fallback, set CK_DISABLE_FETCHPROXY=1.
Sync returns 0 transactions — check that your auth is fresh. The refresh token inside the CKAT cookie expires after ~8 hours.
Tools not appearing — fully quit and relaunch Claude Desktop. In Claude Code, run /mcp to check server status.
"No such file or directory: dist/bundle.js" — run npm run build (not just tsc).
Security
Credentials are stored only in your saved-session file (
~/.creditkarma-mcp/session, orCK_SESSION_PATH), Claude config /.env, or your browser's cookie jar (ContextMint Bridge path)The saved-session file is written at mode 0600 (owner read/write only), in a 0700 directory, by
ck_set_sessionand by every token-refresh rotationck_set_sessionrefuses to save a refresh token whose JWTexpis already in the past — prevents stale credentials from polluting the saved sessionThe fetchproxy path reads cookies directly from the user's browser via
chrome.cookies.get, but it is not memory-only: every token refresh rotates the session, and the rotatedCKAT/CKTRKIDCookie header is saved to the saved-session file (~/.creditkarma-mcp/session, orCK_SESSION_PATH) at mode 0600 in a 0700 directory — fetchproxy-only users included — so a restart can recover without re-reading the browser. Callck_forget_session(or delete that file) to remove itThe server never logs credentials (including under
CK_DEBUG=1, which logs names, timings and redacted bodies only); warnings go to stderr only (stdout is reserved for the MCP JSON-RPC stream)Only
SELECTqueries are permitted viack_query_sql— no writes to Credit Karma. The query runs against a read-only connection, andnode:sqlite'sprepare()compiles only the FIRST statement of multi-statement input: anything after the first;is silently ignored, never executed
Uninstall / Reset
The server keeps two things on disk. Neither is removed when you uninstall the extension or stop using it:
What | Default path | How to remove |
Saved session — your full creditkarma.com Cookie header (working access + refresh tokens) |
| Call |
Synced transaction history (accounts, merchants, amounts, descriptions) |
| Quit the server, then delete the files (or the whole |
ck_forget_session is local only: Credit Karma is not contacted, so sign out at creditkarma.com to invalidate the tokens themselves. If CK_COOKIES is set in your Claude config, remove it there too, and sign out of creditkarma.com in the browser if ContextMint Bridge is installed — otherwise the next call picks the session straight back up.
Development
npm test # run the test suite (vitest)
npm run build # compile TypeScript → dist/, bundle for MCPB
npm run test:watch # watch mode
npm run test:coverage # coverage report (CI enforces 100% on src/**)Versions are bumped automatically by the Tag & Bump GitHub Action (.github/workflows/tag-and-bump.yml). Do not bump manually.
Pull requests
Changes land via PR, including for solo work — release notes are generated from merged PRs only (config in .github/release.yml). Apply one of these labels to every PR: enhancement, bug, security, refactor, documentation, test, dependencies, ci, or ignore-for-release (excludes from notes). The PR title becomes the changelog bullet, so write it like a user-facing entry.
Project structure
src/
auth.ts resolveAuth() — three-path priority (CK_COOKIES env / ck_set_session cache / fetchproxy), plus loadAuthIntoClient()
client.ts Credit Karma GraphQL client (auto-refresh, JWT helpers, cookie parser, balance operations)
index.ts MCP server entry point; bootstraps tokens from the saved session / CK_COOKIES
db.ts SQLite schema, migrations, and upsert helpers
vault.ts Linked-account balances from Intuit's account vault
creditReport.ts Credit-report balances (cards and loans, weeks old)
matching.ts Pairs credit-report accounts with the linked accounts they duplicate
json.ts Small helpers for reading untyped API JSON
transaction.graphql Documents the transaction fields we read (sent as a persisted-query hash, not this text)
tools/
auth.ts ck_set_session — refuses stale refresh tokens, saves ~/.creditkarma-mcp/session at 0600;
ck_forget_session — deletes it and clears in-memory credentials
sync.ts ck_sync_transactions — incremental sync with resume-on-failure
query.ts ck_list_transactions, ck_get_recent_transactions,
ck_get_spending_by_category, ck_get_spending_by_merchant,
ck_get_account_summary
balances.ts ck_get_account_balances + the balance refresh run by every sync
sql.ts ck_query_sql — SELECT-only escape hatch
tests/
helpers.ts Shared test helpers (fakeServer, makeJwt)
auth.test.ts resolveAuth + loadAuthIntoClient (mocks @fetchproxy/bootstrap)
client.test.ts
db.test.ts
tools/
auth.test.ts
sync.test.ts
query.test.ts
sql.test.tsLicense
MIT
Available Tools
11 toolsck_forget_sessionADestructiveIdempotent
Forget the Credit Karma session on this machine: delete the saved-session file (~/.creditkarma-mcp/session, or CK_SESSION_PATH) that ck_set_session and token refreshes write, and clear the credentials held in memory. Use when the user stops using this server or wants their stored login removed. Local only — Credit Karma is not contacted, synced transactions are kept, and a CK_COOKIES value set in the host config is not changed.
Inputs: no named parameters.
ck_get_account_balancesAIdempotent
Current balance of every account: institution, type, last 4, current balance, available credit and credit limit (cards), and the as-of time. Reads the local database (filled by ck_sync_transactions); pass refresh:true to fetch live first. source "linked" = a linked bank, card, loan or investment account, live from the account aggregator (refreshed about daily). source "credit_report" = a card or loan from the credit report (2–5 weeks old, no last 4); one that duplicates a linked account is hidden unless include_matched:true. Liabilities are negative, matching transactions; available credit is limit minus balance. stale is true past 7 days (linked) or 35 days (credit report).
Inputs: refresh, include_matched.
ck_get_account_summaryBRead-only
Return per-account debit, credit, and net totals.
Inputs: end_date, start_date.
ck_get_recent_transactionsBRead-only
Return the N most recent transactions. Convenience shortcut for ck_list_transactions.
Inputs: limit.
ck_get_spending_by_categoryBRead-only
Group debit transactions by category and return totals.
Inputs: account, end_date, start_date.
ck_get_spending_by_merchantBRead-only
Return top merchants by total debit spend.
Inputs: limit, category, end_date, start_date.
ck_healthcheckVerify credentials and upstream reachabilityARead-onlyIdempotent
Resolves the credential the way real tools do, then makes one authenticated request to creditkarma.com. Reports which source supplied the credential, whether creditkarma.com accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a creditkarma.com-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke — steps reports credential lookup, token validity, refresh and probe separately, and failed_step names the first that failed.
Inputs: no named parameters.
ck_list_transactionsARead-only
List transactions with optional filters, newest first. Paginated. Reads the local database (filled by ck_sync_transactions). view "brief" answers one line per transaction instead of JSON.
Inputs: view, limit, offset, status, +7 more.
ck_query_sqlARead-only
Execute a raw SQL SELECT query (CTEs via WITH ... SELECT are supported) against the transactions database. Non-SELECT statements (INSERT, UPDATE, DELETE, DROP, etc.) are rejected. Returns at most max_rows rows (default 500, max 5000); a larger result comes back with truncated: true, so prefer aggregates or LIMIT/OFFSET paging. A query running longer than 10 s is stopped. Only the first statement runs. Tables: transactions, accounts, categories, merchants, sync_state.
Inputs: sql (required), max_rows.
ck_set_sessionAIdempotent
Store a Credit Karma session to enable automatic token refresh. Pass the full Cookie header from a signed-in creditkarma.com request (Chrome DevTools → Network → any creditkarma.com request → Request Headers → right-click the cookie header → Copy value). For most users the easier onboarding path is to install the ContextMint Bridge extension and sign into creditkarma.com — the MCP reads the cookies automatically.
Inputs: cookies (required).
ck_sync_transactionsAIdempotent
Sync Credit Karma transactions into the local SQLite database, then refresh account balances once (see ck_get_account_balances; a balance failure is reported in balances, never thrown; a call that pauses with more to fetch leaves balances to the call that finishes). Incremental by default (fetches since last sync + 30-day overlap for updates). There is no login flow: credentials are re-read from the saved session (ck_set_session), CK_COOKIES, or a signed-in creditkarma.com tab via the ContextMint Bridge extension; if none is usable it fails with an error saying how to sign back in. Bounded and resumable: when it pauses with more to fetch it returns another_run_needed:true and a note — run it again and it continues from where it stopped.
Inputs: max_pages, force_full.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Most tools are cleanly separable by resource and action (sync vs list vs query vs aggregate reports). The main wrinkle is ck_get_recent_transactions, which is explicitly a shortcut for ck_list_transactions, plus mild overlap between ck_get_account_summary, ck_get_account_balances, and ck_query_sql. The descriptions flag these relationships well, so an agent can still choose correctly.
All tools share a ck_ prefix and snake_case verb_noun form (sync_transactions, list_transactions, get_spending_by_category, set_session, query_sql). The one deviation is ck_healthcheck, a bare noun rather than a verb_noun name. Readability and predictability are otherwise strong.
Eleven tools sit comfortably in the well-scoped range. Each tool covers a distinct capability (sync, query, report, session lifecycle, diagnostics) with no filler. The set includes a sensible escape hatch (ck_query_sql) instead of proliferating narrow query tools.
The surface covers the full lifecycle for the stated domain: credential setup/removal, sync, transaction retrieval, aggregation reports, balances, raw SQL, and a diagnostic path when auth breaks. Minor gaps exist (no single-transaction fetch or category mutation), but ck_query_sql provides a workaround for most of them.
Maintenance
Related MCP Connectors
Ask Claude about your income and spending, and import bank statements. No bank login.
Read-only access to your own bank, card and brokerage accounts for Claude, ChatGPT and other AI agents: balances, transactions, spending, subscriptions, cashflow and investment holdings. It can never move money.
Personal finance, bank account, and shared memory connector for Claude, ChatGPT, Gemini Spark & more
Connect AI agents to bank accounts, transactions, balances, and investments.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables integration with Monarch Money to query financial data, analyze spending patterns, track budgets, and get personalized financial insights through conversational AI with Claude Desktop.113ISC
- AlicenseNot gradedqualityDmaintenanceConnects Claude Desktop to Yodlee financial data, enabling account management, transaction queries, spending summaries, and audio narrations.1MIT
- FlicenseAqualityDmaintenanceEnables Claude to query Empower/Personal Capital financial accounts, net worth, transactions, and asset allocation via natural language.5-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to analyze personal finances by reading bank CSVs or connecting to Plaid for live transactions, categorizing spending, flagging overspending against benchmarks, and generating actionable reports and savings tips.MIT