Kaminari Click MCP Server

Official Model Context Protocol server for Kaminari Click — connect Claude, Cursor, ChatGPT, or any MCP-capable agent to your traffic-quality statistics.

• Statistics — slice traffic by time, sub IDs, geo, device; compare periods; filter by any dimension.

• Reports — list, save, and delete saved reports; create public share links.

• Databases — check access to and download slices of the IP risk-score, VPN IP, and bot User-Agent databases.

Quick start

1. Generate an API token in the Kaminari Click account settings (API section).

2. Add the server to your client.

Cursor / Claude Code / any stdio client

{
  "mcpServers": {
    "kaminari-click": {
      "command": "npx",
      "args": ["-y", "@kaminari-click/mcp"],
      "env": {
        "KAMINARI_CLICK_API_KEY": "<your-api-token>"
      }
    }
  }
}

Claude Desktop

Download kaminari-click-mcp.mcpb from the latest release and double-click to install. Claude Desktop asks for your API token during setup.

ChatGPT / hosted agents (HTTP)

Point the connector at https://mcp.kaminari.click/mcp. The server implements OAuth 2.0 (authorization code + PKCE + dynamic client registration): during authorization you paste your API token once, and the client receives it as its access token. Self-hosting:

KAMINARI_CLICK_TRANSPORT=http KAMINARI_CLICK_HTTP_PORT=8080 npx -y @kaminari-click/mcp

In HTTP mode every request must carry Authorization: Bearer <api-token>; the KAMINARI_CLICK_API_KEY env var is rejected so one tenant's token can never leak to another.

Related MCP server: supos MCP Server

Tools

Configuration

All variables are prefixed KAMINARI_CLICK_ — see .env.example. Key ones:

Development

npm install
npm run lint && npm run typecheck   # static gates
npm run test:cov                    # tests + coverage gate (100% lines)
npm run build                       # npm package -> dist/
npm run build:mcpb-bundle           # Claude Desktop bundle -> dist-mcpb/
npx @anthropic-ai/mcpb pack . kaminari-click-mcp.mcpb   # .mcpb archive

Architecture: clean layering (domain → application → infrastructure / presentation), all dependencies flow through a per-request ToolContext, expected errors travel as Result<T, E> (neverthrow). The HTTP transport is stateless — any replica can serve any request — and API tokens never appear in logs.

Security

• Bearer tokens are wrapped in a self-redacting value object and never logged.

• HTTP mode builds a fresh API gateway per request; there is no cross-tenant state.

• The OAuth authorization server stores nothing beyond a 5-minute one-time code window.

Report vulnerabilities to security@kaminari.click.

License

MIT