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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago