Sayli as an MCP server

Sayli can be a source your own AI tools read from. Connect it as an MCP server and your meetings become something Claude, ChatGPT, or Cursor can ask about, without copying anything out of Sayli. It speaks JSON-RPC, signs you in through Sayli, and is strictly read-only.

The tools

prepare_call

Gather what past calls with a company or person established, each line with its call.

show_call_prep

Show a preparation view built from those lines.

show_open_commitments

Show the action items that are still on you, grouped by call.

ask_meetings

Ask a question across your meetings and get a grounded answer.

search_meetings

Search for moments across every call you can see.

list_meetings

List recent meetings, or find them by a name or a date.

get_brief

Pull the brief for one meeting, including the follow-up Sayli drafted.

list_my_actions

List the action items that are on you.

list_folders

List your folders.

get_profile

Tell the client which person and workspace it is connected as.

Connect it

Copy your link

In Sayli, open Connections and copy the link under "Let your AI ask about your own meetings". It is https://api.sayli.ai/api/v1/mcp.

Paste it into your tool

Claude and ChatGPT take the link on its own. They open a Sayli page where you sign in, pick a workspace, and approve.

Or use a token

A tool with no sign-in step, like Cursor or a script, takes a config with a token instead. Create one in the same place in Sayli:

json

{
  "mcpServers": {
    "sayli": {
      "url": "https://api.sayli.ai/api/v1/mcp",
      "headers": { "Authorization": "Bearer sayli_pat_your_token_here" }
    }
  }
}

Read-only and audited

The server can read your meetings. It cannot change anything. Every call is written to your audit log and fires an mcp.tool_called webhook, so you always know what was asked and when.

A workspace in HIPAA mode cannot be connected: its meeting content stays inside Sayli.

Sayli in ChatGPT

What to ask, what it reads, and how to get help.

Personal access tokens

Create the token your client uses to connect.

The same memory, searched from inside the app.