• TidioReply faster to tickets across all channels
  • LyroHire AI to handle customer servicecheck
  • Hubi AIRun on-brand marketing with an AI coworker
  • LabsTidio LabsGet a custom AI solution built by experts
  • Master AgentOrchestrates every channel
  • AI Voice AgentResolves calls on its own
  • Lyro for Zendesk
  • Lyro for Freshdesk
  • Lyro for Salesforce
  • Lyro for HubSpot
Browse all integrationsarrow_forward
  • Borrowell83% resolved
  • GameBoost86% automated
  • Cove Smart70% self-service
  • Secureframe59% automated
See all customer storiesarrow_forward
  • AI in E-Commerce in 2026Free report on the new shopping funnel
  • Shadow AIFree report on the hidden AI habit
  • AI in Insurance in 2026Free report on AI in insurance
See all reportsarrow_forward
  • Features
  • Pricing
Talk to salesGet started
Lyro wordmark

Product

  • Features
  • Master Agent
  • AI Voice Agent
  • Integrations
  • Pricing
  • Copilot

Resources

  • Blog
  • Customer Stories
  • Reports
  • AI in Ecommerce Report
  • Docs

Company

  • Contact
  • Book a Demo

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement

4.7/5on G2G2 logo

SOC 2 Type II · GDPR · CCPA

© 2026 Lyro by Tidio. All rights reserved.

Zep

Zep MCP integration

Writes thread messages into a user graph, retrieves the context relevant to the conversation, searches it semantically, and deletes data on request.

Connect ZepSee all integrations

43actions available

  1. Home/
  2. Integrations/
  3. Zep

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Add thread messages

    Lyro stores every customer message in Zep's conversation graph to build a complete memory. Your team gives Lyro full context of the entire customer relationship.

  • Get thread user context

    Lyro retrieves the most relevant facts about a customer from their knowledge graph. Your team personalizes responses by pulling in what Lyro already knows about them.

  • Create thread

    Lyro starts a new conversation thread for each customer to organize their history. Your team keeps conversations tidy and retrieves past interactions instantly.

See all 43 actions

How businesses use Zep + Lyro

Each card is one request a support team gets, and the Zep actions Lyro runs to close it.

  • hub

    Retrieve the context this conversation actually needs

    Lyro pulls the most relevant context from a user's graph based on the thread in progress, together with the facts and entities held on the session and the summary stored on that user's node.

    Get Thread User ContextGet Session MemoryGet User Node
  • database

    Store what a conversation established

    Lyro adds chat messages to a thread and ingests them into the user's knowledge graph, and records an explicit subject-predicate-object fact when something should be stated outright rather than inferred.

    Add Thread MessagesAdd Session MemoryAdd Fact Triple
  • group

    Set up the users, threads, and shared graphs behind it

    Lyro creates the user record a thread has to hang off, opens the thread itself, and sets up a group namespace when several users need to draw on one shared body of context.

    Create UserCreate ThreadCreate Group
  • search

    Search the graph and follow what connects

    Lyro runs a hybrid search combining semantic similarity with BM25 full-text matching across the knowledge graph, then walks the entity edges around a matched node to see how those facts relate.

    Graph SearchGet Node Entity EdgesGet Edge by UUID

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Zep actions it has and picks the ones a request needs.

  1. 01

    Connect Zep

    Authorize the Zep account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Zep actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free

Zep · Lyro

What can you do in Zep without me setting anything up?

These, right away:

  • Add fact triple
  • Get edge by uuid
  • Delete graph

Great, let's start with the first one.

Ask Lyro anything...

FAQ

Everything else about Zep

Setup, permissions, and the limits of what Lyro can do inside Zep.

  • Get Task Status checks the state of Zep's asynchronous operations - batch adds, graph clones, and fact triple additions among them - so Lyro can confirm the write landed before relying on it, rather than reading a graph that is still ingesting.

  • Delete User removes the user along with all associated threads and artifacts, and Delete Graph permanently removes a graph and all of its data. Delete Thread is the narrower option: it removes one thread and its messages, which is the right call when a single conversation should be forgotten but the user's graph should stay.

  • The one behind the API key on the connection. Get Project Info returns that project's UUID, name, and details, so you can confirm which environment memory is going into before Lyro starts writing - worth checking when staging and production projects sit side by side.

  • Yes. Clone Graph duplicates a user or group graph under new identifiers, which Zep documents for test copies and user migrations, so a change can be tried against real-shaped data before it reaches the graph a live conversation reads from.

Every action available in Zep

All 43 actions your agent can call on Zep, straight from the live MCP connection.

  • Add fact triple

    Add a manually specified fact triple (subject-predicate-object) to the Zep knowledge graph.

  • Add session memory

    Add memory messages to a specified Zep session.

  • Add thread messages

    Add chat messages to a thread in Zep and ingest them into the user knowledge graph.

  • Clone graph

    Clone a user or group graph with new identifiers in Zep.

  • Create graph

    Create a new graph by adding data to Zep.

  • Create group

    Create a new group in Zep for multi-user graph management.

  • Create session

    Create a new session in Zep for storing conversation memory.

  • Create thread

    Create a new thread in Zep for a specific user.

  • Create user

    Create a new user in Zep with properties like user_id, email, and metadata.

  • Delete graph

    Delete a graph from Zep.

  • Delete group

    Delete a group from Zep.

  • Delete session memory

    Delete a session and its memory from Zep.

  • Delete thread

    Delete a thread and its messages from Zep.

  • Delete user

    Delete a user and all associated threads and artifacts from Zep.

  • Get edge by uuid

    Retrieve a specific edge by its UUID from the Zep knowledge graph.

  • Get graph by ID

    Retrieve a graph by its unique identifier from Zep.

  • Get group by ID

    Retrieve a group by ID from Zep.

  • Get node entity edges

    Retrieve all entity edges for a specific node in the Zep knowledge graph.

  • Get project info

    Retrieve project information based on the provided API key.

  • Get session by ID

    Retrieve a session by its unique identifier from Zep.

  • Get session memory

    Retrieve memory for a given session including relevant facts and entities.

  • Get session message by uuid

    Retrieve a specific message by UUID from a Zep session.

  • Get session messages

    Retrieve messages for a given session from Zep.

  • Get task status

    Check the status of asynchronous operations in Zep.

  • Get thread messages

    Retrieve conversation history for a specific thread from Zep.

  • Get thread user context

    Retrieve the most relevant user context from the user graph based on thread messages.

  • Get user by ID

    Retrieve a user by their user ID from Zep.

  • Get user node

    Retrieve a user's graph node and summary from Zep.

  • Get user nodes

    Retrieve all nodes for a specific user from their graph in Zep.

  • Get user sessions

    Retrieve all sessions for a user from Zep.

The tools Zep sits next to

Same connection, same setup. Pick the next one your team already uses.

  • Botpressarrow_outward

    Botpress

    Attributes workspace usage to individual bots, provisions workspaces and integrations, updates workflows, and drives runtime conversations.

  • Entelligencearrow_outward

    Entelligence

    Registers a GitHub repository for analysis and answers plain-language questions about its architecture, functionality, and dependencies.

  • Kagglearrow_outward

    Kaggle

    Searches datasets, models, and competitions, publishes and versions datasets, pulls notebook code and output, and files competition entries.

  • Ollamaarrow_outward

    Ollama

    Route a request to a self-hosted model, reuse OpenAI-format endpoints against it, and report which models the host currently has installed.

  • Scale.aiarrow_outward

    Scale.ai

    Creates image, video, LiDAR, and text annotation tasks, batches and finalizes them, reports completion counts, and reassigns Studio projects.

  • Winston.aiarrow_outward

    Winston.ai

    Scores a submitted passage for AI authorship, checks it for plagiarism against online sources, and measures how closely two texts match.

Browse every integration
Support agent working at a laptop next to the Lyro mascot

Ready to connect Zep?

Authorize the account and your agent has all 43 actions from the first conversation.

Connect ZepTalk to sales
Connect ZepTalk to sales
Support agent working at a laptop next to the Lyro mascot