Memory server for AI Chat with MCP interface

Created By
Gelembjuka year ago
This is the MCP server with memory interface. It can be used with an AI Chat tool as a memory service
Overview

What is CleverChatty Memory?

CleverChatty Memory is a memory server designed for AI chat applications, providing a memory interface that allows chat tools to remember and recall previous conversations.

How to use CleverChatty Memory?

To use CleverChatty Memory, clone the repository from GitHub, install the necessary dependencies, and set up a virtual environment to run the server.

Key features of CleverChatty Memory?

  • Ability to remember chat messages for future context retrieval.
  • Functionality to recall summaries of previous conversations.
  • Supports integration with AI chat tools like CleverChatty.

Use cases of CleverChatty Memory?

  1. Enhancing AI chat interactions by providing context-aware responses.
  2. Storing important information from conversations for later reference.
  3. Improving user experience in chat applications by maintaining conversation history.

FAQ from CleverChatty Memory?

  • Can CleverChatty Memory be used with any AI chat tool?

Yes! It is designed to work with tools that support the MCP interface, such as CleverChatty.

  • Is CleverChatty Memory free to use?

Yes! It is open-source and available under the MIT license.

  • What programming language is CleverChatty Memory written in?

CleverChatty Memory is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Gelembjuk
Star
0
Language
Python
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago