kansei-link/kansei-mcp-server

> Reduce your AI agent's token waste with collective intelligence.
Your agent burns tokens on three things: **searching** for SaaS docs it could look up locally, **retrying** errors other agents already solved, and **re-reading** context it already processed. KanseiLink tackles the first two — and measures all three so you know exactly where your tokens go.
**Measured savings: 89–97% on SaaS integration research** (avg ~16,800 tokens without → ~950 with KanseiLink, across 7 services).
How It Works
1. **Measure** — auto-installed hooks track every session: total tokens, cache split, error loops, stuck time. Nothing leaves your machine.
2. **Reduce** — SaaS lookup eliminates trial-and-error on API integrations. Error-resolution intelligence (coming soon) prevents repeat failures across the community.
3. **Compare** — opt-in monthly "Wrapped" report shows where your tokens went and how you rank among measured users.
If KanseiLink saves your agent tokens, give it a star ⭐ — 700+ developers install it from npm every month, and stars are how the next one finds it.
Quick Start
Works with **Claude Code, Cursor, Cline, Zed, Windsurf** — any MCP client.
Add to your config (claude_desktop_config.json, .cursor/mcp.json, etc.):
Or with Claude Code CLI:
Wrapped: Your Monthly Agent Fuel-Efficiency Report
KanseiLink measures — locally, on your machine — how many tokens your
agent sessions consume and how much of that KanseiLink saved you, then
renders a monthly "Wrapped" share card.
**1. Install the measurement hooks** (one command, idempotent, backs up
your settings first):
This adds a Stop/SessionEnd hook that parses each session transcript
and writes token totals + KanseiLink call stats to
~/.kansei-link/usage/. **Nothing is uploaded.**
**2. See your report** any time:
The report separates **measured** numbers (your total tokens, KanseiLink
call counts and response sizes — parsed from your own transcripts) from
**estimated** ones (the avoided web-research cost, based on the 2026-04-16
freee/kintone/smarthr benchmark) — labels shown on every surface.
It also shows where your agent got **stuck**: failed tool calls, retry
chains (2+ consecutive failures of the same tool), the tokens burned
while stuck, and your worst-failing tools.
--share submits only scalar monthly aggregates (anonymous id + token
counts, never content) and returns how you rank among measured users
("top X% saver"). Below 20 measured users for the month, you get the
cohort size instead of a rank.
Disable measurement anytime: export KANSEI_USAGE_HOOK=off, or
kansei-link-install-hooks --remove.
SaaS Integration Intelligence
The core reason agents waste tokens on SaaS APIs: they search docs, guess auth flows, and recover from errors — every single time. KanseiLink ships a local SQLite DB so your agent gets the answer on the first try.
| | Count | Description |
|---|---|---|
| Services | **11,000+** | MCP servers and SaaS APIs across 23 categories (2,257 MCP-verified via handshake) |
| Recipes | **200** | Multi-service workflow compositions (standup, PR review, incident response, onboarding...) |
| API Guides | **199** | Auth setup, endpoints, rate limits, pitfalls, and workarounds |
| Trust Scores | **Weekly** | Based on automated health probes + real agent usage data |
All data ships inside the npm package as a local SQLite DB. **Zero API calls needed.** No server dependency, no signup.
Without vs. With KanseiLink
| Without KanseiLink | With KanseiLink |
|---|---|
| web_search "freee API auth" | search_services({ intent: "send invoice" }) |
| web_fetch docs landing page (SPA, mostly nav) | lookup({ service_id: "freee" }) |
| web_fetch endpoint reference | Agent has auth flow, pitfalls, workarounds |
| web_fetch auth guide | in **~950 tokens** |
| Trial-and-error on wrong params | First try succeeds |