🧠 Memory MCP Server

Created By
Sinhan88a year ago
A MCP (Model Context Protocol) server providing long-term memory for LLMs
Overview

What is Memory MCP Server?

Memory MCP Server is a server that implements the Model Context Protocol (MCP) to provide long-term memory for Large Language Models (LLMs), enabling them to retain information over extended interactions.

How to use Memory MCP Server?

To use the Memory MCP Server, clone the repository, install the dependencies, and run the server. You can then interact with it using API endpoints to store and retrieve memory.

Key features of Memory MCP Server?

  • Long-term memory storage and retrieval for LLMs.
  • Adherence to the Model Context Protocol for seamless integration.
  • User-friendly API for easy integration into applications.
  • Scalability to handle multiple requests.

Use cases of Memory MCP Server?

  1. Enhancing conversational AI by retaining user context.
  2. Improving personalized recommendations in AI applications.
  3. Supporting complex interactions in AI-driven customer service.

FAQ from Memory MCP Server?

  • Can I use Memory MCP Server with any LLM?

Yes! It is designed to work with various LLM architectures that adhere to the MCP standards.

  • Is there a cost to use Memory MCP Server?

No, it is open-source and free to use.

  • How do I contribute to the project?

You can contribute by forking the repository, making changes, and submitting a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Sinhan88
Star
1
Language
-
License
MIT license

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.

31 minutes ago