Klavis AI

by Klavis-AI

Community Collaboration Tools 6k likes

Klavis AI is an open-source platform bundling 100+ prebuilt MCP integrations (Gmail, Slack, GitHub, Discord) behind managed OAuth and one aggregated endpoint.

Install the Strata CLI

pipx install strata-mcp && strata add --type stdio playwright npx @playwright/mcp@latest

Source: https://github.com/Klavis-AI/klavis

About

Klavis AI packages more than 100 ready-made MCP integrations, including Gmail, Slack, GitHub, Discord, YouTube, and dozens more, so you don't have to write a connector for every service your agent touches. Its Strata layer aggregates several of those integrations behind a single endpoint and only surfaces the tools relevant to the current task, which keeps an agent's context window from filling up with hundreds of unused tool definitions.

OAuth and API-key handling for each service is built in: you call create_strata_server with the list of integrations you want, complete the OAuth prompt it returns, and the resulting MCP endpoint is ready for any client that speaks the protocol. Klavis also ships a hosted MCP Sandbox for running agent training workloads, plus Python and TypeScript SDKs for wiring servers up programmatically instead of by hand.

Key features

  • 100+ prebuilt MCP integrations spanning email, chat, dev tools, and CRM
  • Strata aggregation layer combines multiple servers behind one endpoint
  • Progressive tool discovery limits what an agent sees to its current task
  • Built-in OAuth and API-key management per integration
  • Python and TypeScript SDKs plus a REST API
  • Hosted MCP Sandbox for scaled agent-training environments

Use cases

  • Wiring one agent up to Gmail, Slack, and GitHub without building three separate connectors
  • Keeping tool-choice context small by aggregating several integrations behind Strata instead of loading every tool at once
  • Standing up OAuth-authenticated MCP servers for a multi-tenant product via the SDK
  • Running scaled agent-training workloads inside the hosted MCP Sandbox

Available tools

strata add

CLI command that registers an existing MCP server (Playwright, GitHub, etc.) into your local Strata aggregator so its tools show up behind one connection.

create_strata_server

SDK/API call that provisions a hosted MCP server bundling the integrations you list for a given user, returning an OAuth URL if authentication is required.

get_tools

Returns the live tool list for a running server instance. Klavis exposes tools progressively rather than dumping the full catalog into context.

Frequently asked questions

Do I need to build a separate MCP server for each service Klavis supports?

No. Klavis already ships the connector. You either pull a prebuilt Docker image for a single integration or call create_strata_server to bundle several at once.

How does Klavis stop an agent's context from filling up with unused tools?

Its Strata layer uses progressive discovery: instead of registering every tool from every bundled integration up front, it exposes only the tools relevant to what the agent is currently doing, fetched via get_tools.