In this post, I’ll walk through how to integrate the Mem0 memory model with CleverChatty-CLI, a command-line framework for building AI assistants.

Spoiler: It turned out to be a lot easier than I expected.

Quick Overview of the Projects

Before we dive into the integration, here’s a quick recap of the two key components involved:

• Mem0 “Mem0” (pronounced mem-zero) adds an intelligent memory layer to AI assistants and agents. It enables personalized experiences by remembering user preferences, adapting to their needs, and continuously learning over time. It’s particularly useful for customer support bots, personal assistants, and autonomous agents.

• CleverChatty-CLI A command-line interface for interacting with LLM-based chat systems. It supports MCP (Model Context Protocol), RAG (Retrieval-Augmented Generation), and I plan to add support for A2A (Agent-to-Agent) communication soon. The CLI is built for experimentation, testing, and prototyping AI interactions.

CleverChatty, a lightweight AI Chat tool supporting multiple LLM providers, now includes support for Streamable HTTP with MCP servers. This update enables more flexible and efficient communication with AI models, making integration with custom tools and services even smoother.

🌐 What is CleverChatty?

CleverChatty is a minimalist AI chat interface that works with various large language model (LLM) providers — including OpenAI, Anthropic, Google, and local models like Ollama. It’s designed for users and developers who want a simple, extensible tool that supports MCP-based tool usage.

Until now, CleverChatty only supported STDIO and SSE (Server-Sent Events) as transport protocols for connecting with MCP servers. With the latest update, it now supports Streamable HTTP, expanding compatibility and flexibility.

Over the past couple of months, I’ve been experimenting with the Model Context Protocol (MCP) — building AI agents and tools around it. While the experience has been promising, I’ve noticed a few areas where MCP could be expanded or improved.

These aren’t critical issues, but adding them would make MCP more complete and developer-friendly.

Here’s my current wishlist:

1. A Standard MCP Server Interface
2. Bidirectional Notifications
3. Built-in or Native Transport Layer

Let’s walk through each of these in more detail.

This is the third part of the novella "The End of the Holocene". The second part

"He who fights with monsters should see to it that he does not become a monster himself" — Friedrich Nietzsche, "Beyond Good and Evil"

In May 2030, a strange event occurred.

At dawn, a rocket was launched from a desert area in Mexico into space. The incident caused a stir among military forces and politicians around the world—most of all, in the United States. The rocket was large, and based on its trajectory, it was heading into space, not toward any target on Earth.

Immediately after the launch, the U.S. military activated defensive protocols and went into full alert. Several other countries did the same. Within minutes, it became clear that the rocket wasn’t aimed at any earthly location—it was continuing on, further into space. Calculations confirmed it was headed toward Mars.

Emergency meetings were convened between governments and military leaders to determine what was going on. The Mexican government and armed forces also issued statements saying they had no knowledge of the launch and were just as confused as everyone else. They agreed to full cooperation in the investigation.