An MCP server that syncs a user's Credit Karma transactions into a local SQLite database and exposes tools to query spending, accounts, merchants, and recent transactions. It also manages Credit Karma authentication from a browser cookie header or a fetchproxy browser extension.
From the registry: Credit Karma transactions for Claude — spending by category, merchant, and account summary
$ git clone https://github.com/chrischall/creditkarma-mcp.git && cd creditkarma-mcp && npm install && npm run buildhttps://github.com/chrischall/creditkarma-mcpPlease install the `creditkarma-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Node.js 18+** — Node.js version 18 or later is required to run and build the MCP server. (https://nodejs.org/)
- **Clone the repository and build the server** — The README only provides a local source install path. Clone the repo, install dependencies, and build the dist output before configuring the MCP client. Run: `git clone https://github.com/chrischall/creditkarma-mcp.git && cd creditkarma-mcp && npm install && npm run build` (https://github.com/chrischall/creditkarma-mcp)
- **Have a Credit Karma account** — You must use your own signed-in Credit Karma account for authentication and data access. (https://www.creditkarma.com)
Optional prerequisites:
- Optional: install the fetchproxy browser extension — If you do not want to set CK_COOKIES manually, install fetchproxy and sign in to creditkarma.com in that browser. The server can then read CKAT and CKTRKID cookies at startup as an auth fallback. (https://github.com/chrischall/fetchproxy)
Canonical MCP server config (stdio transport):
- command: `node`
- args: ["<absolute-path-to-creditkarma-mcp>/dist/index.js"]
- optional environment variables:
- `CK_COOKIES`: Full Cookie header copied from a signed-in creditkarma.com request. If unset, the server falls back to a cached session or the fetchproxy browser extension. (example: `CKTRKID=<your-cookie>; CKAT=<your-cookie>; ...`)
- `CK_DISABLE_FETCHPROXY`: Set to 1 to disable the fetchproxy auth fallback and require explicit credentials. (example: `1`)
- `CK_DB_PATH`: Path to the local SQLite database file used for synced transactions. (example: `<path-to-sqlite-db>`)
Note: Authentication works in priority order: CK_COOKIES env var, cached session saved via the ck_set_session tool, then fetchproxy fallback if available. If using fetchproxy, CK_COOKIES can be left unset. The server stores data in a local SQLite database by default at ~/.creditkarma-mcp/transactions.db.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.CK_COOKIESFull Cookie header from a signed-in creditkarma.com request used for authentication.CK_DISABLE_FETCHPROXYDisables the fetchproxy authentication fallback when set to 1.CK_DB_PATHPath to the SQLite database file.MCP server for interacting with the Supabase platform