Log inSubmit server
Kansei MCP Server logo

Kansei MCP Server

by kansei-link

Local-first SaaS integration intelligence with service search, connection guidance, workflow recipes, and local usage reporting.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Kansei MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "kansei-link-kansei-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@kansei-link/mcp-server"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

kansei-link/kansei-mcp-server helps agents research SaaS integrations through a local catalogue of 11,000+ services, API guides, and workflow recipes. Its MCP tools search for relevant services, retrieve authentication details and known pitfalls, and record post-use outcomes in a local database. Use it before connecting to services such as Slack, Notion, freee, SmartHR, or kintone, especially when avoiding web research and trial-and-error matters. It can run locally with no network calls or connect to a hosted HTTP endpoint with current data.

Use cases

  • Search for a SaaS service before attempting an API integration
  • Retrieve authentication steps and known workarounds for an external service
  • Find multi-service recipes for a described workflow
  • Record integration outcomes for local recovery hints
  • Measure token usage and retry chains in agent sessions

Key features

  • Local SQLite catalogue of 11,000+ services
  • Service search by name or integration intent
  • Connection guides, pitfalls, and workarounds
  • Multi-service workflow recipes
  • Local outcome reporting with PII masking
  • Optional token-usage and session reports

Tools3

What Kansei MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~2.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

19/19 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @kansei-link/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads466Package downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Kansei MCP Server works

What kansei-link/kansei-mcp-server does

KanseiLink provides structured integration research for AI agents working with SaaS APIs and MCP services. The catalogue covers more than 11,000 services across many categories, along with roughly 200 multi-service workflow recipes and API guidance covering authentication, endpoints, rate limits, pitfalls, and workarounds.

The local npm package includes a public copy of the catalogue and builds a SQLite database on the user's machine. Searching and looking up services can therefore work without an account, a hosted-server dependency, or API calls. A hosted HTTP option provides access to the service through a URL and keeps the catalogue current.

How it works

The intended sequence is:

  1. Search for a service or integration goal with search_services.
  2. Use lookup to retrieve setup guidance, pitfalls, workarounds, or a multi-service recipe.
  3. Execute the integration with the relevant external tool or API.
  4. Call report with the outcome and any useful feedback.

report stores results in the installation's local database. PII is masked before storage. Local usage measurement is also available through installed hooks, which parse session transcripts and write token and call statistics under ~/.kansei-link/usage/.

Setup and configuration

For a hosted connection, add https://mcp.kansei-link.com/mcp as an MCP server URL. Claude Code can add it with:

Terminal
claude mcp add --transport http kansei-link https://mcp.kansei-link.com/mcp

The local package can be run through npm and configured as a standard stdio MCP server:

Terminal
claude mcp add -s user kansei-link -- npx -y @kansei-link/mcp-server

The corresponding client configuration uses npx as the command and -y, @kansei-link/mcp-server as its arguments. The local mode uses the bundled public catalogue and sends no data. The hosted endpoint requires no key or sign-up.

Optional utilities install session-measurement hooks, generate a monthly Wrapped report, install a Claude Code skill for automatic invocation, and manage the optional reporting hook. Central reporting is off by default; enabling it permits limited pseudonymous event or aggregate transmission, while local measurement remains on the machine. Measurement can be disabled with KANSEI_USAGE_HOOK=off.

Tools and capabilities

  • search_services finds services by name or intent and returns structured integration evaluations, connection methods, guides, and agent-readiness signals.
  • lookup returns service tips by default, with optional full connection details, usage insights, or workflow recipes selected through its parameters.
  • report records success or failure, feedback, API changes, and qualitative integration results for local recovery hints and statistics.
  • The catalogue includes service cards, recipes, API guides, and a changelog copy for local lookup.
  • Optional Wrapped reports distinguish measured token and call data from estimated avoided research costs and identify failed calls, retry chains, and time spent stuck.

Limitations and notes

The local catalogue is a public copy rather than the complete hosted dataset. Internal scores, probe results, agent voices, and raw registry data remain hosted; a missed lookup points to the service site and an ask path. Local data also does not automatically provide the credentials or execution tools needed to call a third-party API.

The optional sharing features have separate consent controls. The reporting hook sends only a fixed set of pseudonymous fields when enabled, such as service slug, tool name, outcome, and error category; prompts, tool arguments and results, customer or record names, API keys, file paths, and free text are excluded.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Kansei MCP Server

kansei-link/kansei-mcp-server is an MCP server that connects AI agents to a catalogue of SaaS services and MCP integrations. Its main tools search_services, lookup, and report help agents find services, retrieve connection guidance and workflow recipes, then record integration outcomes in a local database.

Install it locally with `npx -y @kansei-link/mcp-server` as the MCP command, or add the hosted endpoint `https://mcp.kansei-link.com/mcp` as an HTTP MCP server. The package also provides example commands for Claude Code and JSON configuration for URL-based clients.

Yes, the npm package works offline using a bundled public catalogue and local SQLite database. Local searches and lookups do not require API calls, a hosted-server dependency, an account, or sign-up.

The lookup tool returns service-specific tips by default, including authentication setup, pitfalls, and workarounds. Optional parameters can request a full connection guide, usage insights, or recipes matching a workflow description.

No, local mode sends nothing, and the optional reporting hook excludes prompts, tool inputs and outputs, API keys, file paths, customer or record names, and free text. When central reporting is explicitly enabled, it sends limited pseudonymous fields such as the service, tool, outcome, and error category.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewKansei MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/kansei-link-kansei-mcp-server?style=directory)](https://allmcps.com/mcp/kansei-link-kansei-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/kansei-link-kansei-mcp-server"><img src="https://allmcps.com/api/badge/kansei-link-kansei-mcp-server?style=directory" alt="Kansei MCP Server on AllMCPs" /></a>