Weckr

Name: Weckr
Author: Ghiles3232

by Ghiles3232version 0.1.2i★ –iRuns on your computer

Registry namecom.useweckr/weckr

Install

Overview

Description from the maker (original English)

Ask which of your customers cost more in LLM calls than they pay, per user and per feature.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi0 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: WECKR_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 0 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: WECKR_API_KEY, WECKR_PROJECT_ID, WECKR_BASE_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "weckr": {
      "command": "npx",
      "args": [
        "-y",
        "@weckr/mcp"
      ],
      "env": {
        "WECKR_API_KEY": "your-value",
        "WECKR_PROJECT_ID": "your-value",
        "WECKR_BASE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add weckr --env WECKR_API_KEY=your-value --env WECKR_PROJECT_ID=your-value --env WECKR_BASE_URL=your-value -- npx -y @weckr/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "weckr": {
      "command": "npx",
      "args": [
        "-y",
        "@weckr/mcp"
      ],
      "env": {
        "WECKR_API_KEY": "your-value",
        "WECKR_PROJECT_ID": "your-value",
        "WECKR_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "weckr": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@weckr/mcp"
      ],
      "env": {
        "WECKR_API_KEY": "your-value",
        "WECKR_PROJECT_ID": "your-value",
        "WECKR_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

WECKR_API_KEY secret required env
Your Weckr project API key (starts with wk_), from the dashboard sidebar at useweckr.com/dashboard.
WECKR_PROJECT_ID env
Optional. Pins the server to one project id; otherwise it is resolved from the API key.
WECKR_BASE_URL env
Optional. Overrides the API base URL, for self-hosted or staging deployments.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

! Caution
Maker matches the repo
The publisher (useweckr.com) is not the repo owner (Ghiles3232); someone else may have listed it
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7275 servers in this category
Published to the registry more recently than 32% of the other 7275 servers in this category
Basic checks equal to or better than 30% of the other 7275 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Weckr safe?

It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: WECKR_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@weckr/mcp

Query your Weckr AI cost and margin data directly from Claude, Cursor, or any other MCP-compatible AI assistant.

Try it live

See what Weckr looks like before connecting your own data. 👉 https://app.useweckr.com/demo

What you can ask

Ask things like:

*"Which of my users are losing me money this month?"*
*"What's my AI margin right now?"*
*"Which feature should I switch to a cheaper model?"*
*"Is my pricing sustainable given my actual AI costs?"*
*"Show me the feature cost breakdown."*

Claude calls the Weckr API and gives you the real numbers from your dashboard, in the conversation.

Get an api key

Sign up at app.useweckr.com. Your wk_ key is shown once when you create a project. Copy it. If you missed it, mint a new project at app.useweckr.com/dashboard/projects/new.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

"mcpServers": { "weckr": { "command": "npx", "args": ["-y", "@weckr/mcp"], "env": { "WECKR_API_KEY": "wk_your_key_here" } } } }

Restart Claude Desktop. Try: *"Use the Weckr tools to show me my AI costs this month."*

Why `npx` and not `npm install -g`? Claude Desktop runs under launchd on

macOS, which doesn't inherit your interactive shell's PATH. If you installed

Node via nvm / asdf / volta, a globally-installed weckr-mcp binary

usually isn't on Claude Desktop's PATH and the server fails to start with no

diagnostic. npx -y @weckr/mcp sidesteps the PATH problem entirely.

Cursor

Add to .cursor/mcp.json at your project root (or ~/.cursor/mcp.json for global):

"mcpServers": { "weckr": { "command": "npx", "args": ["-y", "@weckr/mcp"], "env": { "WECKR_API_KEY": "wk_your_key_here" } } } }

Tools exposed

Tool	Use it to ask
`get_overview`	"How am I doing this month?" Total cost, revenue, margin, requests, unprofitable user count
`get_users`	"Which users are unprofitable?" / "Show me my top-cost users." Per-user margin (filterable)
`get_feature_breakdown`	"Which features cost me the most?" Per-feature cost share
`get_model_recommendations`	"Where can I cut AI cost?" Same-provider cheaper-model swaps with $-saving estimate
`get_pricing_recommendations`	"Is my pricing sustainable?" Per-plan margin health + recommended price
`get_spending_cap_url`	Returns the dashboard URL where caps are edited (does NOT mutate state)

Configuration

Env var	Required	Default	Notes
`WECKR_API_KEY`	yes	none	Your `wk_` key from app.useweckr.com
`WECKR_PROJECT_ID`	no	resolved from `/api/v1/me`	Optional: pre-set the project UUID to skip one round-trip on startup
`WECKR_BASE_URL`	no	`https://app.useweckr.com`	Override for self-hosted Weckr. Your wk_ key is sent here on every request, so do not set this to a host you do not control. Only `https://` is accepted (loopback `http://` allowed for dev).

How it works

The MCP server is a tiny stdio process spawned by your AI client. It calls the Weckr HTTP API using your wk_ key (server-to-server, no JWT needed). The api key authoritatively identifies one project. The server uses it to resolve projectId once at startup, then scopes every subsequent call to that project. The dashboard endpoints (/api/v1/stats, /users, /recommendations/*) verify the URL project id matches the api key's project and return 404 on mismatch, so a leaked api key cannot be used to read another project's data.

No prompt text or completion text is sent anywhere by this package. The tools only read aggregated stats. The api key never leaves your local process *except* to the URL configured via WECKR_BASE_URL (default app.useweckr.com). If you change WECKR_BASE_URL, the SDK prints a stderr warning so you can spot a copy-paste config that points at the wrong host.

Troubleshooting

Claude Desktop shows the weckr server as disconnected, with no error. Likely a PATH issue. Switch to the npx -y @weckr/mcp form above. To see the actual error from the spawn, run the server manually in a terminal: WECKR_API_KEY=wk_... npx -y @weckr/mcp. Anything wrong (missing api key, 401 from Weckr, network issue) prints to stderr.

`Weckr API 401 on /api/v1/me`. Your WECKR_API_KEY is empty, malformed, revoked, or pasted with a trailing space. Confirm a working key by visiting app.useweckr.com/dashboard/projects/new and creating a fresh project.

Tools show "Project not found or forbidden" (404). You set WECKR_PROJECT_ID to a UUID that doesn't belong to the project the api key owns. Remove WECKR_PROJECT_ID so the server resolves the right project id from the api key.

Local development

git clone https://github.com/Ghiles3232/weckr-sdks

cd weckr-sdks/mcp npm install npm run build

Smoke-test against production:

WECKR_API_KEY=wk_... node dist/index.js

(prints "weckr-mcp running on stdio" to stderr, then waits for JSON-RPC on stdin)

To point at a local Weckr backend:

WECKR_API_KEY=wk_... WECKR_BASE_URL=http://localhost:3000 node dist/index.js

Source

Open source at github.com/Ghiles3232/weckr-sdks.

License

MIT

Weckr

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

@weckr/mcp

Try it live

What you can ask

Get an api key

Claude Desktop

Cursor

Tools exposed

Configuration

How it works

Troubleshooting

Local development

Smoke-test against production:

(prints "weckr-mcp running on stdio" to stderr, then waits for JSON-RPC on stdin)

Source

License