Klavis MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

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

Demo en vivo

Cómo se ve en la práctica

klavis.replay ▶ listo

0/0

Instalar

Elige tu cliente

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

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.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 usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

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

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "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"
      ]
    }
  }
}

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

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

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

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

Añádelo a context_servers. Zed recarga en caliente al guardar.

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

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: Klavis

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

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

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

Requisitos previos

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

Flujo

Wire the gateway

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

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

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

→ All three APIs hit in one flow with audit trail

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

Errores comunes

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

Combinar con: gmail · slack

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

👤 Internal tools teams ⏱ ~30 min intermediate

Cuándo usarlo: You want one Claude chat that can "do the paperwork" across your SaaS stack.

Requisitos previos

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

Flujo

Connect stack

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

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

→ Case + bug created; Slack reply links them

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

Errores comunes

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

Combinar con: slack · linear

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

klavis + gmail

Local Gmail MCP for personal, Klavis for multi-user

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

klavis + slack

Post status updates from ops flows

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

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar	Coste
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

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: Free tier: 1k calls/mo. Pro: 100k/mo.
Tokens por llamada: 100–2000 depending on app
Monetario: Freemium + usage-based
Consejo: Audit which apps drive the bulk of calls and set per-app quotas in the dashboard

Seguridad

Permisos, secretos, alcance

Ámbitos mínimos: read (per app) write-scoped (per app)

Almacenamiento de credenciales: Klavis holds OAuth tokens; encrypted at rest

Salida de datos: api.klavis.ai + each downstream SaaS

No conceder nunca: admin scopes unless truly needed

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

Resolución de problemas

Errores comunes y soluciones

401 from proxy_tool_call

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

Verificar: 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

Alternativas

Klavis vs otros

Alternativa	Cuándo usarla	Contrapartida
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

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills