Back to vendors
K

Klavis AI

Also known as: Klavis, Strata

Visit site
Entry priceFree (open source servers and a hosted free plan); Pro and Enterprise unpriced; sandboxes by quoteFull pricing detail

Hosted MCP servers with per-user OAuth across more than a hundred apps, the open source Strata server, and sandboxed real-app environments for training and evaluating agents.

Klavis AI builds MCP integration infrastructure and live environments for training and evaluating AI agents. Its hosted MCP servers connect agents to more than a hundred applications, from GitHub, Gmail and Slack to Salesforce, HubSpot, Notion and Jira, with OAuth 2.0 handled per end user so an agent acts in each user's own accounts. Strata puts every connected server behind a single MCP server that lets the agent discover categories and actions progressively instead of loading every tool at once.

The servers and Strata are open source, with Docker images for running them in the customer's own infrastructure, and a REST API with Python and TypeScript SDKs manages servers, users, authentication and white-labeled OAuth, with US and EU production endpoints. Klavis Guardrails sits as a proxy between MCP clients and servers, checking tool calls against allowlists and enforcing least privilege access.

The same API provides sandboxes of real applications for training and evaluation. A sandbox is seeded with a deterministic state, the agent works against it through MCP, the final state can be exported and checked against ground truth, and the sandbox resets for the next run. Benchmark environments and a task verification endpoint report whether an agent completed a task.

Klavis's homepage and products page now present the company as a supplier of RL environments, training datasets and evaluations for AI labs, and the MCP platform appears only in the documentation and a homepage link to it. The MCP platform has a free plan with paid Pro and Enterprise tiers, and Klavis does not publish their prices; sandbox environments are sold by quote.

Vendor details

Canonical URL

https://www.klavis.ai

Category

Agent infrastructure

Subcategory

Tools and MCP

Funding status

Independent and backed by Y Combinator. The MCP servers and Strata are open source on GitHub.

Company status

independent

Use cases & customers

Primary use cases

hosted MCP serversper-user OAuth for agent tool accessprogressive tool discovery with Stratasandboxed environments for agent training and evaluation

Target customers

developersAI application teamsAI labs

Deployment options

SaaSself-hosted

Integrations

Hosted MCP servers for more than a hundred applications, including GitHub, Gmail, Slack, Salesforce, HubSpot, Notion, Jira, Google Workspace and Microsoft 365, with per-user OAuth 2.0 or API-key authentication, reached by MCP URL, through Strata or through the Call Tool API. REST API with an OpenAPI specification and Python and TypeScript SDKs; guides for LangChain, LlamaIndex, CrewAI, Agno, Mastra, Google ADK and the major model APIs; open source servers with Docker images for self-hosting.

In practice

Your agent needs to act in each user's GitHub, Gmail and Notion, and you do not want to build OAuth for each. Klavis runs hosted MCP servers with per-user OAuth and returns a server URL the agent connects to.

Your agent loses accuracy as its tool list grows. Strata puts every connected server behind one MCP server the agent explores by category and action before executing one.

You need to test an agent's tool use against realistic data before production. Klavis sandboxes are seeded with a deterministic state, exported for checking against ground truth, and reset between runs.

Agentic Index coverage score

7.0 / 14 capabilities · 50%

Integrations & Tool Calling Full

Hosted MCP servers from Klavis cover more than a hundred applications, from Affinity and Airtable to Zendesk and Zoho Mail. Each one connects per end user through OAuth 2.0 or an API key, so an agent reads and writes in that user's own accounts. Tools are reached through each server's MCP URL, through Strata or through the Call Tool API for plain function calling. Strata is one MCP server that lets the agent discover categories and actions across every connected server before executing one.

Sourceklavis.ai/docs/mcp-server/overviewread 2026-11-03

Workflow Orchestration Not documented

The product executes the tool calls an agent makes and returns the results. Sequencing, branching and handoff live in the customer's own framework, and Klavis publishes guides for LangChain and LangGraph, LlamaIndex, CrewAI, Agno, Mastra, Google ADK and the major model APIs. Strata's discover, browse and execute tools help the agent pick an action. Klavis has no workflow runtime of its own to sequence, branch, retry or route work, or to combine deterministic workflow nodes with autonomous agent steps.

Sourceklavis.ai/docs/ai-platform-integration/overviewread 2026-11-03

Knowledge Grounding & RAG Not documented

MCP servers for Notion, Google Drive, Confluence and similar tools let an agent query those systems live, but Klavis builds no retrieval layer over the customer's own content. Strata finds tools, not documents, by browsing categories and actions instead of semantic search. Klavis names no ingestion, indexing, retrieval or RAG layer of its own, so there are no retrieved passages or sources to show.

Sourceklavis.ai/docs/concepts/strataread 2026-11-03

Human Oversight & Guardrails Partial

Each end user authorizes an integration through OAuth consent before its tools act, and a server connection can be set read only through the API. Klavis Guardrails sits as a proxy between MCP clients and servers. It detects tool poisoning and prompt injection, enforces least privilege access and checks tool invocations against allowlists. Klavis names no approval step a person acts on before an action commits, whether at a node, workflow or policy layer.

Sourceklavis.ai/docs/enterprise-security/klavis-securityread 2026-11-03

Security, Identity & Governance Partial

The API enforces HTTPS with API key authentication. Each end user's credentials are scoped per integration and returned only to the key owner that controls the instance, and customers can run OAuth through their own white label OAuth apps. Connections can be set read only, and Klavis Guardrails enforces least privilege tool access. No attestation or certification is published. On security, Klavis points only to its built in OAuth, and it publishes terms, privacy and cookie policies but no trust center. Klavis names no SSO, roles or audit trail.

Sourceklavis.ai/docs/api-reference/overviewread 2026-11-03

Observability & Auditability Not documented

The API returns server instances, tools, users and authentication status, and users check authentication in the dashboard. Klavis names no log, trace, execution history or audit event of the tool calls an agent makes through it, and no export to a SIEM. Guardrails' real time threat detection acts on calls as they happen, and Klavis does not say whether it keeps a record the customer can inspect.

Sourceklavis.ai/docs/api-reference/overviewread 2026-11-03

Memory & State Persistence Not documented

Each end user's credentials and integration status are stored so tools act without asking for consent again. A sandbox holds application state for one training or evaluation run. Klavis names no memory layer that keeps an agent's context across runs. Its Mem0 server connects an agent to another vendor's memory product.

Sourceklavis.ai/docs/api-reference/user/get-user-integrationsread 2026-11-03

Deployment & Data Residency Full

Hosted servers run on Klavis's infrastructure with a stated 99.9% uptime SLA. There are two production servers, api.klavis.ai for the US and api.eu.klavis.ai for the EU. For on premises or custom deployments, every MCP server ships as a Docker image to run in the customer's own infrastructure, and Strata is open source. Customers can pick the US or EU region, or run the servers in their own environment.

Sourceklavis.ai/docs/concepts/mcpread 2026-11-03

Prebuilt Agents, Templates & Packs Not documented

The catalog holds MCP servers and tools. They give an agent actions to take and do no work on their own when selected. The framework guides build example agents as tutorial code. Klavis names no ready made workflow, template or role specific agent of its own for a customer to adopt.

Sourceklavis.ai/docs/mcp-server/overviewread 2026-11-03

Triggers & Channel Coverage Partial

Slack and Discord clients come alongside the hosted servers, so a person can put MCP tools to work from those chat channels. Klavis gives no setup guide for either client. It names no schedule, webhook, event subscription or inbound queue that starts work without a person asking.

Sourceklavis.ai/faqread 2026-11-03

Model Flexibility & Routing Full

Tools are served to whatever model the customer runs. The List Tools API returns a server's tools in several model formats, and integration guides cover OpenAI, Anthropic's Claude, Gemini, Mistral, Cohere, Together AI and Fireworks AI, each using the customer's own provider key. Klavis names no model of its own, so the model, the provider and the key are the customer's throughout.

Sourceklavis.ai/docs/ai-platform-integration/overviewread 2026-11-03

APIs, SDKs & MCP Extensibility Full

Outside callers reach Klavis through a REST API at api.klavis.ai with a published OpenAPI specification. Python and TypeScript SDKs cover servers, Strata, users, OAuth, white labeling and sandboxes. Klavis serves MCP as an addressed service, with each hosted server and each Strata instance at its own URL. The servers and Strata are open source for self hosting.

Sourceklavis.ai/docs/installationread 2026-11-03

Testing, Debugging & Optimization Full

Isolated sandboxes of real applications let the customer test and train its agent. A Klavis Sandbox is loaded with a deterministic world state, and the agent works against it through MCP. The full state can be exported to compare against ground truth, and the sandbox resets for the next run. The Universe API acquires benchmark task environments, and its verify endpoint runs the task's check and returns whether the task passed, with the failure reason. Sandboxes can also be configured for the MCP-Atlas, Toolathlon and MCP-Mark benchmarks.

Sourceklavis.ai/docs/api-reference/universe/verify-taskread 2026-11-03

Browser & Computer Use Partial

The Local Sandbox API starts a virtual machine hosting interconnected MCP servers, among them Playwright for a browser plus a terminal and Desktop Commander for the machine. It serves filesystem, terminal, browser and document workflows during agent training and evaluation. Klavis restricts it to use outside production and says nothing more about driving a browser through the hosted Playwright server. The hosted MCP servers and Strata work through application APIs, not interfaces.

Sourceklavis.ai/docs/api-reference/local-sandbox/acquireread 2026-11-03

The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded

Pricing

Free (open source servers and a hosted free plan); Pro and Enterprise unpriced; sandboxes by quote

not published (plan tiers named in the FAQ; sandbox environments by quote)

Free tierTrial available

Included quota

Free plan: hosted API at a default rate limit of two requests per second. Open source servers and Strata: no vendor limit when self hosted. Pro, Enterprise and sandbox quotas are not published.

What is public

The free paths are public: open source servers and Strata, and a hosted free plan at a stated rate limit. No paid plan price is published, and the pricing page quotes sandbox environments on request.

Billing mechanics

Self host the open source servers for free, or use the hosted platform on a free plan with a rate limit and move to Pro or Enterprise on terms that are not published; sandbox environments for training and evaluation are quoted by sales.

Cost watchouts

No paid plan price is published, so hosted use beyond the free plan's two requests per second needs a quote. Sandbox capacity for training and evaluation is priced on request. Self hosting moves the cost to your own infrastructure and operations.

Variable cost rationale

The free plan's rate limit is the only published usage term and paid usage terms are unpublished; self hosting the open source servers lets heavy users take the vendor cost to zero.

Overage / add-ons

Not published. The free plan is rate limited at two requests per second and paying users have no rate limit; self hosting has no vendor metering.

Sales call required

Mixed (some tiers require a call)

Free / trial

Open source servers and Strata free to self host, plus a hosted free plan

Lowest paid plan

None published; Pro and Enterprise plans are named in the FAQ without a price

Commercial notes

Independent and backed by Y Combinator. The homepage and pricing page now lead with training environments and agentic data for frontier AI labs; the MCP integration platform runs on the same account and API.

Key ambiguities

The pricing page no longer covers the MCP platform: klavis.ai/pricing redirects to sandbox environment pricing, while the FAQ still names free, Pro and Enterprise plans and no self-serve purchase path for a paid plan is published. Scope plan limits and prices with the vendor.

Agentic Index verified 2026-11-03

Alternatives to Klavis AI

The closest documented capability profiles to Klavis AI among agent infrastructure platforms tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.

  • Arcade7.5 / 14Adds documented Observability & AuditabilityKlavis AI vs Arcade →
  • Inworld AI8.5 / 14Adds documented Workflow Orchestration and Observability & Auditability, among others
  • Maxim AI8.5 / 14Adds documented Workflow Orchestration and Observability & Auditability
  • Portkey7.5 / 14Adds documented Observability & Auditability
  • Freeplay8.0 / 14Adds documented Observability & Auditability
  • Guardrails AI7.0 / 14Adds documented Observability & Auditability and Prebuilt Agents, Templates & Packs

Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded

Contact us

Found a vendor we missed? Have feedback on the index? We'd love to hear from you.