Klang over MCP
Klang runs a hosted Model Context Protocol server so AI assistants can read your meetings, conversations, and notebooks directly. Connect a client once, then ask it about your Klang content in plain language. No copying transcripts around: the client signs in with OAuth, or you hand it an API key.
What you can do
The Model Context Protocol (MCP) is an open standard that lets AI clients call tools on a remote server. Klang's server turns your workspace into a set of read tools the assistant can reach for on its own. Once connected, prompts like these work against your real data:
- forum Summarize what we decided about pricing across last week’s calls.
- forum Which customers brought up SSO this month?
- forum Find the interview where the claimant gave the accident date and quote it.
- forum List the open action items from every meeting in my onboarding folder.
The assistant lists your conversations, opens the relevant ones, and reads their transcripts and summaries to answer. It works the same in a case workflow, where you point it at a specific folder, and across a busy meeting workspace, where you let it find the threads for you.
Server URL
The server speaks Streamable HTTP at a single endpoint. For Klang Cloud that is:
https://app.klang.ai/api/mcp
Self-hosted and dedicated-tenant deployments use a different host. Open Settings → Developers → MCP in your Klang workspace to see and copy your exact URL.
Point any compliant MCP client at that URL and it handles the rest. See connecting clients for per-client setup.
Read-only access
Every Klang MCP tool only reads, and only from the one workspace the connection is bound to. An assistant can browse and quote your content, but it cannot edit, delete, or share anything.