Back to Browse

Weckr Sdks MCP Server

Developer ToolsModerate6.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

6.2
Moderate6.2Moderate Risk

The MCP server code demonstrates solid security practices with proper authentication via API keys, no malicious patterns, and appropriate permission scoping for its purpose as a cost/margin tracking tool. Minor code quality issues around error handling and input validation prevent a higher score, but findings are low-severity. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

6 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Your Weckr project API key (starts with wk_), from the dashboard sidebar at useweckr.com/dashboard.Required

Environment variable: WECKR_API_KEY

Optional. Pins the server to one project id; otherwise it is resolved from the API key.Optional

Environment variable: WECKR_PROJECT_ID

Optional. Overrides the API base URL, for self-hosted or staging deployments.Optional

Environment variable: WECKR_BASE_URL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "com-useweckr-weckr": {
      "env": {
        "WECKR_API_KEY": "your-weckr-api-key-here",
        "WECKR_BASE_URL": "your-weckr-base-url-here",
        "WECKR_PROJECT_ID": "your-weckr-project-id-here"
      },
      "args": [
        "-y",
        "@weckr/mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Weckr SDKs

OpenSSF Best Practices CI OpenSSF Scorecard

AI cost and margin intelligence for SaaS founders. See exactly which users cost you more than they pay, per LLM call, zero added latency.

Drop the SDK into your app, get a dashboard that shows cost per user / feature / model and recommends cheaper swaps. Set per-plan spending caps the SDK enforces before the LLM call.

Pick your language

PackageInstallSource
TypeScript / Node@weckr/sdknpm install @weckr/sdktypescript/
Pythonweckr-sdkpip install weckr-sdkpython/
Claude / Cursor (MCP)@weckr/mcpnpx -y @weckr/mcpmcp/
Claude Code (Skills)weckr plugin/plugin install weckr@weckrskills/

Each subfolder has full setup docs, examples, and supported-model lists.

Claude Skills

This repo is also an installable Claude Code plugin that bundles four skills, so your AI assistant knows real model prices and the exact Weckr syntax instead of inventing code:

/plugin marketplace add Ghiles3232/weckr-sdks
/plugin install weckr@weckr
SkillWhat Claude learns
weckr-integrationWire the SDK in with the correct two line pattern, errors, and provider notes
weckr-model-pricingCurrent per token prices for OpenAI, Anthropic, Gemini, and Kimi
weckr-cost-estimatorProject what an AI feature costs per call, per user, per month before shipping
weckr-margin-auditFlag which pricing plans go underwater once LLM cost is counted

The pricing skills read the live feed at useweckr.com/pricing.json first (generated from the same table Weckr bills with), and a weekly pricing watcher opens a reviewed PR whenever a provider changes rates, so the numbers track reality instead of drifting. Full explainer at useweckr.com/skills.

Try it without signing up

Live demo dashboard →

Click around with seeded data for a fictional SaaS. No signup required.

Starter templates

Clone a full AI SaaS with Weckr already wired in and deploy in minutes. Both are MIT licensed.

  • weckr-nextjs-starter: Next.js 14, Supabase auth, Stripe billing, an OpenAI endpoint, and Weckr tracking cost and margin per user.
  • weckr-fastapi-starter: FastAPI, a Claude endpoint, SQLite, and Weckr tracking cost and margin per user.

Framework guides

Step by step integrations for the stacks people actually ship on, each with the exact code and where the wrap goes:

  • Next.js: route handler pattern, flush() for serverless, streaming notes.
  • FastAPI: endpoint pattern with the authenticated user, zero added dependencies.
  • LangChain: wrap the client at the boundary, not the callbacks.
  • CrewAI: price every agent turn, catch the stuck crew.

How it works

  1. You wrap your LLM calls with wk.chat(client, opts).
  2. The SDK forwards the call to OpenAI / Anthropic / Gemini and returns the original result, with no added latency on the request path.
  3. After it resolves, the SDK fire-and-forgets a log to the Weckr API with (userId, feature, model, tokens, latency, plan).
  4. The backend computes cost server-side from public per-token pricing (clients can't forge cost) and stores (cost, revenue, margin) per request.
  5. The dashboard rolls it up, per user, per feature, per model, and surfaces unprofitable users + cheaper-model recommendations.

What gets sent

Only the call metadata above: model name, token counts, latency, plan, and your userId string. No prompt text or completion text is ever sent.

Get an API key

app.useweckr.com. Free tier, no credit card.

Questions and Support

Have a question about integration or a feature request? Open a discussion: https://github.com/Ghiles3232/weckr-sdks/discussions

We respond to every question.

License

MIT. See LICENSE.

Reviews

No reviews yet

Be the first to review this server!

Weckr Sdks MCP Server - Ask which of your customers cost more in LLM calls than | MCP Marketplace