Lyro MCP Server

Lyro runs its own MCP (Model Context Protocol) server, so you can connect an AI client - like Cursor, Claude, or any MCP-compatible tool - directly to your workspace. Once connected, the client can read and change your Lyro setup the same way you would in the dashboard: create agents, add knowledge, configure channels, review conversations, and more.

Not to be confused with Tools and integrations, which is about connecting external MCP servers into Lyro as agent tools. This page is the other direction - connecting a client to Lyro's own MCP server.

Connect

Point your MCP client at the Lyro MCP endpoint and authenticate with a workspace API key.

• Endpoint: https://api.getkronos.ai/api/mcp
• Transport: Streamable HTTP
• Auth header: Authorization: Bearer krns_sk_...

Create the key in Settings → API Keys (see API & Developers). The key is scoped to the workspace that created it, so the client only ever sees that workspace.

A typical client config looks like this:

{
  "mcpServers": {
    "lyro": {
      "url": "https://api.getkronos.ai/api/mcp",
      "headers": { "Authorization": "Bearer krns_sk_..." }
    }
  }
}

Most MCP clients handle the connection handshake for you - paste the URL and token and you are done.

What you can do

The tools the client sees depend on your API key's scopes. With a fully scoped key, an MCP client can manage:

• Agents - create and configure agents, roles, and skills (see Agents)
• Knowledge - create knowledge bases and articles (see Knowledge)
• Channels - set up the chat widget, email, phone, and other channels
• Conversations & contacts - read conversations and look up people
• Escalation - manage escalation procedures and destinations
• Integrations, custom tools, and MCP servers - wire up the tools your agents can call
• Evals & datasets - build and run evaluations
• Analytics & findings - pull metrics and quality findings
• Workspaces - read and manage workspace settings

A key with limited scopes only exposes the matching tools. Give a key the narrowest scopes it needs.

How it works

Under the hood the endpoint speaks JSON-RPC over the MCP Streamable HTTP transport:

• The first request is an initialize call. Lyro replies with a session id in the mcp-session-id response header.
• The client sends that mcp-session-id header on every following request, uses GET for the server message stream, and DELETE to close the session.

You normally never deal with this directly - the MCP client library does it. You only need the endpoint URL and your API key.

Clients

Lyro works with any MCP client, including Cursor, Claude, and the pydantic-ai SDK. Add the endpoint and bearer token using whatever "add MCP server" flow your client provides.