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 搭配，撬動十倍槓桿

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.
每次呼叫 Token 數: 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

Klavis

為什麼要用

核心特性

即時演示

實際使用效果

安裝

選擇你的客戶端

使用場景

實戰用法： Klavis

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

前置條件

步驟

注意事項

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

前置條件

步驟

注意事項

組合

與其他 MCP 搭配，撬動十倍槓桿

工具

此 MCP 暴露的能力

成本與限制

運行它的成本

安全

權限、密鑰、影響範圍

故障排查

常見錯誤與修復

替代方案

Klavis 對比其他方案

更多

資源