Creditkarma MCP

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.

[!WARNING]

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"*

Requirements

• Claude Desktop or Claude Code
• 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](https://www.creditkarma.com/about/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 build

2. Configure

cp .env.example .env

See "Authentication" below to get your CK_COOKIES value

3. 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.

1. `CK_COOKIES` env var (legacy). Set the full Cookie header in your Claude Desktop config or .env. This is the path shown in the config above.
2. Saved session from `ck_set_session`. The tool saves the Cookie header to ~/.creditkarma-mcp/session (mode 0600; override the path with CK_SESSION_PATH), which the server reads back directly on every start — including from the .mcpb bundle. Paths 1 and 2 are both local: whichever holds the fresher refresh token wins.
3. 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 + CKTRKID cookies from your already-signed-in creditkarma.com tab 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)

1. 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 .sha256 file published beside it before loading it:

   shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256

1. Sign into creditkarma.com in that browser.
2. Leave CK_COOKIES unset 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)

1. Log in to creditkarma.com in Chrome
2. Open DevTools → Network → click any request to creditkarma.com → Request Headers
3. Right-click the cookie header → 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 call ck_set_session).

Available tools

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=equifax to 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, s