Klavis MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

Live-Demo

In der Praxis

klavis.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/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"
      ]
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.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 nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "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"
      ]
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: Klavis

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

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

Wann einsetzen: Your users want Claude to read Gmail, update HubSpot, comment on Jira — and you don't want to write OAuth glue for each.

Voraussetzungen

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

Ablauf

Wire the gateway

Add Klavis as an MCP server with my token. List which tools are now available.✓ Kopiert

→ 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.✓ Kopiert

→ 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.✓ Kopiert

→ All three APIs hit in one flow with audit trail

Ergebnis: A working multi-SaaS agent with user-scoped auth and one config URL.

Fallstricke

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

Kombinieren mit: gmail · slack

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

👤 Internal tools teams ⏱ ~30 min intermediate

Wann einsetzen: You want one Claude chat that can "do the paperwork" across your SaaS stack.

Voraussetzungen

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

Ablauf

Connect stack

Add Klavis. Confirm Salesforce, Jira, Slack are all connected.✓ Kopiert

→ 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.✓ Kopiert

→ Case + bug created; Slack reply links them

Ergebnis: Cross-tool action completed in one chat with receipts in each system.

Fallstricke

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

Kombinieren mit: slack · linear

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

klavis + gmail

Local Gmail MCP for personal, Klavis for multi-user

Use my local Gmail MCP for me, Klavis for customer data.✓ Kopiert

klavis + slack

Post status updates from ops flows

After creating the Salesforce case, post a summary in #customers via Klavis.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: Free tier: 1k calls/mo. Pro: 100k/mo.
Tokens pro Aufruf: 100–2000 depending on app
Kosten in €: Freemium + usage-based
Tipp: Audit which apps drive the bulk of calls and set per-app quotas in the dashboard

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: read (per app) write-scoped (per app)

Credential-Speicherung: Klavis holds OAuth tokens; encrypted at rest

Datenabfluss: api.klavis.ai + each downstream SaaS

Niemals gewähren: admin scopes unless truly needed

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

Fehlerbehebung

Häufige Fehler und Lösungen

401 from proxy_tool_call

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

Prüfen: 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

Alternativen

Klavis vs. andere

Alternative	Wann stattdessen	Kompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen