creditkarma-mcp 2.0.3 → 2.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -1
- package/dist/bundle.js +1370 -613
- package/dist/index.js +22 -4
- package/package.json +6 -2
- package/server.json +29 -0
package/README.md
CHANGED
|
@@ -91,7 +91,16 @@ npm run auth -- .env # writes CK_COOKIES=<ckat> to .env
|
|
|
91
91
|
|
|
92
92
|
Launches Chrome with a dedicated profile at `~/.creditkarma-mcp/chrome-profile`, waits for you to sign in at creditkarma.com, then captures the `CKAT` cookie (the URL-encoded bundle of access + refresh JWTs). Either prints it (for pasting into Claude Desktop / MCPB) or writes it to the env file you pass. Requires Google Chrome installed locally; the script installs `puppeteer-core` on first run (~1 MB).
|
|
93
93
|
|
|
94
|
-
#### Option B — manual (
|
|
94
|
+
#### Option B — manual paste (secure prompt)
|
|
95
|
+
|
|
96
|
+
```bash
|
|
97
|
+
npm run auth -- --manual # prompts for the cookie, prints CK_COOKIES
|
|
98
|
+
npm run auth -- --manual .env # prompts for the cookie, writes to .env
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
Use this if the scripted flow hits Intuit/Akamai bot detection (sign-in returns "A technical issue has unexpectedly occurred"). Grab the cookie from your normal Chrome (Option C below), then paste it at the prompt. Input is **not echoed** — paste, press Enter. Accepts the raw CKAT value, `CKAT=<value>`, or a full Cookie header.
|
|
102
|
+
|
|
103
|
+
#### Option C — manual (DevTools)
|
|
95
104
|
|
|
96
105
|
1. Log in to [creditkarma.com](https://www.creditkarma.com) in Chrome
|
|
97
106
|
2. Open DevTools → **Application** → **Cookies** → `https://www.creditkarma.com`
|