Credit Karma MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CK_COOKIES | No | Full Cookie header from a signed-in creditkarma.com request | |
| CK_DB_PATH | No | Path to SQLite database file | ~/.creditkarma-mcp/transactions.db |
| CK_DISABLE_FETCHPROXY | No | Set to '1' to skip the fetchproxy fallback (headless / CI) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ck_healthcheckA | 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 — |
| ck_set_sessionA | 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 |
| ck_forget_sessionA | 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. |
| ck_sync_transactionsA | 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 |
| ck_list_transactionsA | 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. |
| ck_get_recent_transactionsB | Return the N most recent transactions. Convenience shortcut for ck_list_transactions. |
| ck_get_spending_by_categoryB | Group debit transactions by category and return totals. |
| ck_get_spending_by_merchantB | Return top merchants by total debit spend. |
| ck_get_account_summaryB | Return per-account debit, credit, and net totals. |
| ck_get_account_balancesA | 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. |
| ck_query_sqlA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.