Arcade vs Klavis AI (2026)

More than 8,000 permission aware tools are available, plus custom or third party MCP servers that the customer builds or brings. Authorization is delegated, so the agent acts as its user within that user's scope, and Arcade handles OAuth across dozens of auth providers. Hosted remote MCP servers connect through Arcade to systems such as Salesforce, ServiceNow, GitHub, Atlassian and Snowflake.

Tool Recommendation, added in October 2026, lets an agent describe a task and get back the few tools that fit instead of loading the whole catalog, which Arcade puts at up to 91% fewer input tokens per session, and a Private Registry lets users browse the tools behind a gateway and request missing ones.

Sourcearcade.devread 2026-10-24

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-09-22

Arcade executes the tool calls an agent makes and returns the results. Sequencing, branching and handoffs between agents live in the customer's own framework. Setup guides cover frameworks such as LangChain, CrewAI, OpenAI Agents, Google ADK and Mastra, among others. No workflow runtime of Arcade's own is named, so retries, routing and deterministic workflow steps sit outside the platform.

Sourcearcade.devread 2026-10-24

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-09-22

Tools in Arcade run when an agent or MCP client calls them. No schedule, event, webhook or inbound queue that starts an agent run is named.

Sourcearcade.devread 2026-10-24

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-09-22

Agents get authenticated tools that read from and act in outside systems. Arcade names no index, graph, embeddings layer or other retrieval structure that it maintains over the customer's documents.

Sourcearcade.devread 2026-10-24

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-09-22

Each user's OAuth tokens and authorization grants are kept, so tools can act without asking for consent again. Those stored credentials carry no agent state. Arcade names no memory that keeps an agent's state or a user's context across runs.

Sourcearcade.devread 2026-10-24

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-09-22

Contextual access runs the customer's own policy logic inline. An access hook decides which tools each user can see. A pre execution hook allows, denies or modifies inputs before each tool call, and a post execution hook allows, denies or modifies the output, so sensitive actions can be blocked and personal data redacted.

Users authorize each scope before a tool acts for them, an agent can line up every authorization a job needs before it starts, and rate limits apply. A tool author can ask the user for input during a call through MCP elicitation, but Arcade names no step where a person reviews or approves an action before it commits.

Sourcedocs.arcade.dev/en/operate/governance/contextual-accessread 2026-10-24

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-09-22

Authentication runs against the customer's identity provider, with Okta, Microsoft Entra ID, Auth0 and Stytch as user sources. Authorization is delegated, so an agent acts as its user and never past that user's scope. Contextual access hooks enforce the customer's policies on every tool call. Role based access control has organization admin, project admin and member roles, and SSO and audit logs are included on Enterprise. No security attestation is published.

Sourcearcade.devread 2026-10-24

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-09-22

Every action taken through Arcade leaves one record naming the agent, the user and the system, streamed to the customer's SIEM, and execution tool logs show which tools ran, who they ran for and whether they succeeded. Administrative actions go to a separate audit log that is on by default, with OpenTelemetry export, a filterable dashboard and a REST API for pulling events into the customer's SIEM or compliance tooling.

Sourcedocs.arcade.dev/en/operate/governance/audit-logsread 2026-10-24

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-09-22

Customers choose between Arcade Cloud and their own infrastructure. A turnkey platform that Arcade operates can be deployed into the customer's cloud account, as an Azure Marketplace managed app or through an AWS private offer. A self managed Helm deployment can run on the customer's Kubernetes cluster, for data residency, network isolation or compliance. Enterprise adds VPC and fully air gapped deployment.

Sourcedocs.arcade.dev/en/operate/deployread 2026-10-24

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-09-22

The catalog holds tools and MCP servers that give an agent actions to take. The sample apps are example code. Arcade names no ready made workflows, templates or prebuilt agents of its own.

Sourcearcade.devread 2026-10-24

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-09-22

Any client, model or framework the customer picks can use Arcade's tools. Setup guides cover the customer's own LLM and frameworks such as LangChain, OpenAI Agents, Google ADK, CrewAI, Mastra and Vercel AI SDK, among others. The evaluation command runs against whichever providers and models the customer names.

Sourcearcade.devread 2026-10-24

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-09-22

Developers get an API, described in the Arcade API Reference, and a Contextual Access Webhook API. SDKs appear throughout the framework guides, alongside the Arcade CLI and an open source MCP framework in Python and JavaScript for building MCP servers that Arcade hosts or connects. The Arcade plugin, released in October 2026, installs into Claude Code, Cursor, Codex, VS Code, Copilot CLI and Claude Desktop, and any remote MCP client can connect through one server URL. The REST API behind audit logs is called with an Arcade API key.

Sourcedocs.arcade.dev/llms.txtread 2026-10-24

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-09-22

The arcade evals command runs evaluation suites that the customer writes against its tools. It gives detailed results and critic feedback, a failures only view, multiple runs for stability and comparisons across providers and models in one run. Capture mode records the tool calls a model makes without scoring them, so they can become test expectations, and Arcade describes its evals as catching hallucinated and destructive calls before they run.

Sourcedocs.arcade.dev/en/build/create-tools/evaluate-tools/run-evaluationsread 2026-10-24

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-09-22

Actions go through authenticated APIs and MCP tools. Arcade names no browser, desktop or remote computer session that it runs for an agent. Some toolkits connect to scraping and sandbox services that other vendors run.

Sourcearcade.devread 2026-10-24

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-09-22