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

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와 조합해 10배 효율

도구

이 MCP가 노출하는 것

비용 및 제한

운영 비용

보안

권한, 시크릿, 파급범위

문제 해결

자주 발생하는 오류와 해결

대안

Klavis 다른 것과 비교

더 보기

리소스