Any MCP server—Notion, Zendesk, your own

Connect your knowledge base

Connect any remote MCP server—Zendesk, Notion, Confluence, GitHub, or your own internal one. If it speaks the Model Context Protocol, the assistant can use it. An admin authorizes it once from the dashboard and every chat and voice session for that app can use its tools. No code, no per-provider integration to maintain.

Read the docs

Works withChat & voicePer-app connectionOAuth, bearer or no-authAdmin-gatedKMS-encrypted at rest

Connected providers (examples)

Zendesk

Connected

Notion

Connected

Confluence

Connected

Any MCP-compatible server

+ Connect

Tokens encrypted · never sent to the browser

Auto-refreshed · powers chat & voice

What you get

Admin connects once from the dashboard—OAuth, a static bearer token, or a public no-auth server, no engineering work
Same connection powers both chat and voice
Tool allowlist: pick exactly which tools the model can call (none until you enable them)
Provider tokens are envelope-encrypted at rest with AWS KMS and never sent to the browser
Tokens auto-refresh; one-click reconnect if a provider revokes access

How it works

Admin connects a server once

An org admin opens an application's Integrations tab, pastes the MCP server URL, and clicks Connect—Yak runs the provider's OAuth flow (or accepts a static bearer token, or connects public no-auth servers in one step).

Pick the tools the model may call

Yak discovers the server's tools and the admin checks the ones to expose—tools stay off until explicitly enabled, so you can surface read-only lookups while hiding write or destructive actions.

Every session uses them, server-side

On your site, each end-user chat and voice session calls the allowed tools through Yak's backend against the provider—the browser only ever sees the tool name, arguments, and result, never the credentials or server URL.