Klavis MCP — ユースケース, インストール & ライブデモ

なぜ使うのか

主な機能

Hosted MCPs for Slack, Salesforce, Notion, Jira, Gmail, Drive, Calendar, HubSpot, Asana, etc.
OAuth 2.0 handled end-to-end — no per-user token juggling
Single MCP endpoint regardless of how many apps you enable
Audit log of every tool call per tenant
Self-host option via Docker for compliance-heavy envs

ライブデモ

実際の動作

klavis.replay ▶ 準備完了

0/0

インストール

クライアントを選択

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "klavis": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.klavis.ai/mcp/{server}?auth_token=YOUR_TOKEN"
      ]
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "klavis": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.klavis.ai/mcp/{server}?auth_token=YOUR_TOKEN"
      ]
    }
  }
}

Cursor は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "klavis": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.klavis.ai/mcp/{server}?auth_token=YOUR_TOKEN"
      ]
    }
  }
}

Cline サイドバーの MCP Servers アイコンをクリックし、"Edit Configuration" を選択。

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "klavis": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.klavis.ai/mcp/{server}?auth_token=YOUR_TOKEN"
      ]
    }
  }
}

Claude Desktop と同じ形式。Windsurf を再起動して反映。

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "klavis",
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.klavis.ai/mcp/{server}?auth_token=YOUR_TOKEN"
      ]
    }
  ]
}

Continue はマップではなくサーバーオブジェクトの配列を使用。

~/.config/zed/settings.json

{
  "context_servers": {
    "klavis": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-remote",
          "https://api.klavis.ai/mcp/{server}?auth_token=YOUR_TOKEN"
        ]
      }
    }
  }
}

context_servers に追加。保存時に Zed がホットリロード。

claude mcp add klavis -- npx -y mcp-remote https://api.klavis.ai/mcp/{server}?auth_token=YOUR_TOKEN

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方： Klavis

Ship an agent that touches 5 SaaS tools without 5 auth flows

👤 Product builders embedding Claude into their app ⏱ ~45 min intermediate

使うタイミング： Your users want Claude to read Gmail, update HubSpot, comment on Jira — and you don't want to write OAuth glue for each.

前提条件

Klavis account + API key — Sign up at klavis.ai and grab the key from dashboard
Selected servers enabled — Toggle Gmail, HubSpot, Jira on in the Klavis UI

フロー

Wire the gateway

Add Klavis as an MCP server with my token. List which tools are now available.✓ コピーしました

→ Tool list mentions Gmail, HubSpot, Jira endpoints
End-user connect

Generate the Connect-Gmail URL for user_id=xyz. When they return, confirm auth succeeded.✓ コピーしました

→ OAuth URL returned; post-callback shows connected:true
Cross-app action

For the latest Gmail from acme.com, create a HubSpot contact and a Jira ticket summarizing the thread.✓ コピーしました

→ All three APIs hit in one flow with audit trail

結果： A working multi-SaaS agent with user-scoped auth and one config URL.

注意点

User tokens expire silently — Subscribe to the auth_expired webhook and prompt the user to reconnect

組み合わせ： gmail · slack

Internal ops bot — file tickets, update CRM, post to Slack from one chat

👤 Internal tools teams ⏱ ~30 min intermediate

使うタイミング： You want one Claude chat that can "do the paperwork" across your SaaS stack.

前提条件

Admin OAuths all apps once — Connect each app from the team account, not per-user

フロー

Connect stack

Add Klavis. Confirm Salesforce, Jira, Slack are all connected.✓ コピーしました

→ All three show connected status
Triage email

For the customer complaint in the last Slack #support message: create a Salesforce case, a Jira bug, and reply-in-thread with the ticket links.✓ コピーしました

→ Case + bug created; Slack reply links them

結果： Cross-tool action completed in one chat with receipts in each system.

注意点

Rate limits on Slack — Klavis dashboard shows per-app quota; batch operations when possible

組み合わせ： slack · linear

組み合わせ

他のMCPと組み合わせて10倍の力を

klavis + gmail

Local Gmail MCP for personal, Klavis for multi-user

Use my local Gmail MCP for me, Klavis for customer data.✓ コピーしました

klavis + slack

Post status updates from ops flows

After creating the Salesforce case, post a summary in #customers via Klavis.✓ コピーしました

ツール

このMCPが提供する機能

ツール	入力	呼び出すタイミング	コスト
list_connected_apps	user_id?: str	Check which apps a given user has connected	free
get_auth_url	app: str, user_id: str	Kick off user OAuth flow	free
proxy_tool_call	app, tool, args, user_id	Any downstream tool call — Klavis routes it	varies by app

コストと制限

運用コスト

APIクォータ: Free tier: 1k calls/mo. Pro: 100k/mo.
呼び出しあたりのトークン: 100–2000 depending on app
金額: Freemium + usage-based
ヒント: Audit which apps drive the bulk of calls and set per-app quotas in the dashboard

セキュリティ

権限、シークレット、影響範囲

最小スコープ： read (per app) write-scoped (per app)

認証情報の保管： Klavis holds OAuth tokens; encrypted at rest

データ送信先： api.klavis.ai + each downstream SaaS

絶対に付与しない： admin scopes unless truly needed

Self-host Docker build for SOC2 scopes — the hosted plane sees all traffic

トラブルシューティング

よくあるエラーと対処法

401 from proxy_tool_call

User's OAuth expired — call get_auth_url again and have them reconnect

確認： Call list_connected_apps, check status==connected

Server "notion" not in gateway

Enable it in the Klavis dashboard first, then restart the MCP client to pick up new tools

Rate limit on a single app

Klavis returns 429 with retry_after; back off or batch

代替案

Klavis 他との比較

代替案	代わりに使う場面	トレードオフ
Composio MCP	You want a similar hosted-integration platform with different pricing	Different app coverage; similar auth model
Self-hosted individual MCPs	Single user, few apps, compliance-sensitive	You own the OAuth glue for every app

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る